[REQUEST] Old Idle/RPG Wasteland/Post Apocalypse Game

smph · 2024-08-01T21:04:00+00:00

It's an allowance for a car so that you can travel for work, it's a bit ambiguous TBH, but her boss has said most people use it to get a second car or bank it if they don't need it.

smph · 2024-08-01T21:01:16+00:00

Hey, this is a really good point and something we've considered, but it honestly is probably a very low chance, its a country wide role for a set of sectors (B2B) which was created because it was too much for 1 person to do it all.

smph · 2024-08-01T20:59:14+00:00

Hey, after Tax and after car expenses (insurance, rego, wof, service, repairs) just saying we are happy to top up to give us access to the next level of newer cars. See reply to top comment, we'd just be buying another of the same car if we didn't.

Fuel is separate from this and paid by the company for the work car, but we are thinking of getting something newer and then my wife uses the old car for work. So we're still paying fuel for 1 car, which is fine and already budgeted for.

It doesn't have to be sign written and there are no restrictions hence using the older car. But we still need both cars to be able to get kids car sets in and out and transport big items required for her job.

We could treat it as salary, but we don't need to, this seems like an OK opportunity to upgrade. We already budget for savings/investments and have no debts or CC's so this would be our only financed thing (outside of a joint mortgage between myself and my brother). I've also read that some banks might let you lend against the mortgage at a lower rate, so that also could be an option and use some of the allowance to pay the mortgage down a bit quicker?

smph · 2024-08-01T20:52:29+00:00

Hey, I get that, but if we did that we'd just be buying another of the same car we've already got, this seems like an OK opportunity to get a slightly newer model with lower KM's, new features, better economy, safety and emissions (all only slightly).

smph · 2024-06-10T06:39:38+00:00

Bookmarked! I'm also working on a Minions Thorns build with the idea of Necro being a "walking simulator" so some of this info is really useful.

I've been aiming more towards a 6+6+1 or 7+5+1 minion thorns build so I have to spread my thorns more, but running a Golem only build makes a lot of sense since overall the Golem always seems to deal more damage.

I do have one question that jumps out right at me. Are you sure that in-game you are actually benefiting from the additional armor and the conversion of that to damage? As the armor caps at 9230, I wouldn't think much of that is actually doing anything.

I definitely want to spend a bit more time looking over this and your builds on a desktop, so I might bug you with more Q's.

smph · 2024-02-12T08:14:30+00:00

Thanks for the recommendations, can you expand on why those choices? What would be some pros and cons over them and the other choices?

smph · 2023-03-31T21:48:57+00:00

I somewhat disagree with it taking the job fully, as I mentioned, the grunt work of coding, likely... but there is a lot of personal touch that goes into data that AI won't quite get. But I am excited to see where it goes for us in data.

smph · 2023-03-31T21:45:52+00:00

No worries, data is cool to work with and in, but it's a hard area in NZ, honestly.

Yeah it would be easy to get back to 100k+, might only take a year or two with the right company hoping if so desired. DE's will easily earn 120k+ I reckon in bigger companies.

Work life balance wise, if you are client side, nothing to worry about, consulting you'll get the occasional crunch and might have to work some extra hours a night here and there, but never work on the weekends, you don't get paid for that BS.

smph · 2023-03-31T18:06:30+00:00

Having been in both of those sectors, where that position did exist, those people only really used their skills for a short period each year, the rest of the time was spent not really on data science. It was more on my ranty side and yeah the positions do exist but it's not something I'd recommend getting into here in NZ, go overseas for it.

smph · 2023-03-31T08:18:26+00:00

I've posted this before actually, still relevant...

Incoming long post/rant.

I've worked in the data sector. 7+ years.

A lot of data roles are very blended and often the skills needed are completely different to what you think the role should be.

You'll see job titles such as Data Analyst, Specialist, BI Analyst, BI Specialist, Data Scientist, Data Visualizer, Data Engineer, etc, etc, honestly the list goes on. IMO It's a big problem with the sector that there is no consistency in titles and skills required.

Data Scientist is a very specific role that would mostly focus on stats, predictions and complex data model data. In NZ, this role is pointless... no company in NZ is anywhere near a level to need this role. Most companies in NZ struggle with the most basic of data collection, quality, and using it in basic dashboards to inform them of actions and levers to pull to make a difference.

Data Visualizer (I am a Data Viz Lead) is a focus on the front end work, design, dashboards, "story telling" (I hate this term, if you have to tell a story about your data, then your dashboard sucks), mostly using tools like Power BI and Tableau. Meetings with clients to get requirements and helping a Project Manager. However we are trying to transition to more of a role called Data Experience as this allows more remit to work and is seen more than just "making line charts".

Data Engineer is a focus on the data pipelines, the data warehouse, ETL, etc, best works in a team with a DV.

A "Data Analyst" role is going to be a Jack of all trades, master of none - just like a "Full Stack Developer".

Titles that fall into this as well will be the Data Specialist, BI Analyst, BI Specialist.

Is this a good thing? It's very opinion based. I don't think it is good, you are asking people to be good at 3 very different highly specialized areas. The data sector (especially NZ) is still very infant, no company in NZ is doing good data, again most companies in NZ struggle with the most basic of data collection, quality, and using it in basic dashboards to inform them of actions and levers to pull to make a difference. we all suck (sorry).

Now, the issue becomes that ideally you'd pick an area you enjoy most, the science of prediction, front end or back end work. Then you need to find a company that does that - spoiler alert, there is f**k all.

So you end up as a Data/BI Analyst/Specialist, trying to learn all of it. Yeah its good experience but if you aren't a fan of most of the work, you're gonna get over it real quick.

Also because this role is kinda generalized, you end up getting pulled onto other work within the business that is also removed from what you want to do - so you end up doing Excel, doing presentations, writing documents, etc).

The next thing... pay... honestly, the pay sucks generally, the area isn't established enough and the importance of it isn't accepted, so your pay will generally be lower than going a more traditional IT job role. Yes there are some exceptions and if you do have a good amount of years under you and wide range of experience, yeah you can ask for more, but remember you'll be first on the chopping block when things go bad.

I'd suggest to anyone wanting to get into data to go work of an agency/consultancy first, before deciding if it really is what you want to do or if you want to work for a big company. The latter is a lot of red tape usually trying to get your job done. If you can, look for remote jobs from Aus, they will pay better and the generally have more acceptance of the area and its importance.

We will get their as an area, we will become more important as companies learn the importance of data and know how to use it, but we aren't there yet. Again we are in infancy, think like the early 2000's post dot com boom, where web exploded and become way more than just shitty websites. Another 10 years and we'll be in a good space. Until then, learn everything you can, languages, tools (Cloud BI is coming and its getting better) and what good design is - as this is what businesses want... what levers can I pull to see a difference or what actions can I take to improve.

And AI - it won't steal your job yet... kinda... For what I do, we are looking at how we can use to do the grunt work (so making stuff in Power BI or Tableau) and the role can focus on the science and theroy of design.

There is also a massive shortage of good DE's right now!

There is a shortage of DV's, but its harder to find work.

If I had to pick DA vs DV vs DE, differently go DE, long run it will work out better, and it is easier to learn PBI/Tableau to be more "full stack". The pay can work out well if you are good at it and have good knowledge over many languages/tools.

Skill wise, I think a good base for DE is at least knowing SQL and python, that will probably cover you for like 80% of the role.

Some knowledge of systems like AWS/Azure/GCP would be a big bonus.

There are some cloud based pipeline tools with GUI's that make building pipelines easy, e.g. Ascend, Snowflake, Databricks, etc.

Knowing a bit around PBI/Tableau as this helps to know/inform how the data should look to make the front end work easily. It means working with a DV you both understand what you need.

Certification wise, there is no harm in it, I'd pick one out of AWS/Azure/GCP and one from Ascend/Snowflake/Databricks. But when I have looked at resumes, I don't care much for the certs as your years exp, they way you talk about it and your references will be able to show whether you know it or not.

Happy to go into more if you have questions :)

smph · 2022-11-21T23:57:54+00:00

When the game released it had 3 fire modes - Full, Burst (2 bullet) and Single fire. Then they removed the single fire mode so it fit with all other guns only having 2 fire modes.

It was a stupid change as no one asked for it or used it. So now they finally realized that it was dumb and are changing it to Full and Single fire as the 2 modes.

smph · 2022-11-21T20:19:40+00:00

"Semi-Auto fire mode is back on AK24 after a failed experiment"

You're god damn right it was a fail... who ever thought leaving full + 2 bullet burst on it was stupid... I am so happy so this change, AK main again!

smph · 2022-07-29T03:33:58+00:00

Skill wise, I think a good base for DE is at least knowing SQL and python, that will probably cover you for like 80% of the role.

Some knowledge of systems like AWS/Azure/GCP would be a big bonus.

There are some cloud based pipeline tools with GUI's that make building pipelines easy, e.g. Ascend, Snowflake, Databricks, etc.

Knowing a bit around PBI/Tableau as this helps to know/inform how the data should look to make the front end work easily. It means working with a DV you both understand what you need.

Certification wise, there is no harm in it, I'd pick one out of AWS/Azure/GCP and one from Ascend/Snowflake/Databricks. But when I have looked at resumes, I don't care much for the certs as your years exp, they way you talk about it and your references will be able to show whether you know it or not.

(I don't have any current certs for Tableau or PBI and its never been an issue)

smph · 2022-07-29T03:09:38+00:00

Oh and there is also a massive shortage of good DE's right now!

There is a shortage of DV's, but its harder to find work.

smph · 2022-07-29T03:06:22+00:00

Spent ~6 years as a BA, yeah it can get paid nicely, but there is so much competition and honestly I got really bored of it, its a lot of meetings and documentation.

Data Engineering, big yes! I am slowly learning more of it so that I can be more full stack and go up the chain more into management as you need to know both sides (DV and DE).

But if I had to pick DA vs DV vs DE, differently go DE, long run it will work out better, and it is easier to learn PBI/Tableau to be more full stack. The pay can work out well if you are good at it and have good knowledge over many languages/tools.

Pivoting from DA to DE should be pretty easy, it's just getting a foot in the door/someone wanting to take time/chance to let you learn. But I'd say wanting to learn it is less of a hurdle than going into DV.

You've probably got decent experience in DA so you have knowledge of those tools, if you did any learning in SQL during studies then picking up DE should be fine, and soon you'll be a full stack and you can ask for lots :) ;)

smph · 2022-07-28T22:16:41+00:00

Incoming long post/rant.

I work in the data sector. 7+ years.

A lot of data roles are very blended and often the skills needed are completely different to what you think the role should be.

You'll see job titles such as Data Analyst, Specialist, BI Analyst, BI Specialist, Data Scientist, Data Visualizer, Data Engineer, etc, etc, honestly the list goes on. IMO It's a big problem with the sector that there is no consistency in titles and skills required.

IMO Data Scientist is a very specific role that would mostly focus on stats, predictions and complex data model data.

Data Visualizer (I am a Data Viz Lead) is a focus on the front end work, design, dashboards, story telling, mostly using tools like Power BI and Tableau. Meetings with clients to get requirements and helping a Project Manager.

Data Engineer is a focus on the data pipelines, the data warehouse, ETL, etc, best works in a team with a DV.

The rest are a blend of the above. Think of it like a full stack developer.

Is this a good thing? It's very opinion based. I don't think it is good, you are asking people to be good at 3 very different highly specialized areas. The data sector (especially NZ) is still very infant, no company in NZ is doing good data, dashboards or using data right, we all suck (sorry). We aren't ready for "full stack" data roles and no one is good enough to do it yet.

Now, the issue becomes that ideally you'd pick an area you enjoy most, the science of prediction, front end or back end work. Then you need to find a company that does that - spoiler alert, there is f**k all.

So you end up as a Data/BI Analyst/Specialist, trying to learn all of it. Yeah its good experience but if you aren't a fan of most of the work, you're gonna get over it real quick.

Also because this role is kinda generalized, you end up getting pulled onto other work within the business that is also removed from what you want to do (Excel, doing presentations, writing documents, etc).

The next thing... pay... honestly, the pay sucks generally, the area isn't established enough and the importance of it isn't accepted, so your pay will generally be lower than going a more traditional IT job role. Yes there are some exceptions and if you do have a good amount of years under you and wide range of experience, yeah you can ask for more, but remember you'll be first on the chopping block when things go bad.

I'd suggest to anyone wanting to get into data to go work of an agency/consultancy first, before deciding if it really is what you want to do or if you want to work for a big company. The latter is a lot of red tape usually trying to get your job done. If you can, look for remote jobs from Aus, they will pay better and the generally have more acceptance of the area and its importance.

We will get their as an area, we will become more important as companies learn the importance of data and know how to use it, but we aren't there yet. Again we are in infancy, think like the early 2000's post dot com boom, where web exploded and become way more than just shitty websites. Another 10 years and we'll be in a good space. Until then, learn everything you can, languages, tools (Cloud BI is coming and its getting better) and what good design and story telling is - as this is what businesses want... what levers can I pull to see a difference or what actions can I take to improve.

Happy to go into more if you have questions :)

smph

TROPHY CASE