UK-Al05

That often means employers big budgets and training.

Game VC is called being a publisher.

I have feedback in the past that people don't like diagrams upfront, because it presents a finished solution.

Probably reducing its capabilities to make the new model look better.

I've seen multiple countries do exactly that, then quietly drop it after a few years. If it doesn't look serious that doesn't actually help negotiate.

These are almost always negation strategies rather than serious initiatives.

Some of the worst team developers I have ever met, are people who presented at conferences a lot. It's ego thing.

It's not meant to give you complete coverage. It's meant to guide to meeting the acceptance criteria.

This is why people don't see the problem with tests that agents generate after the implementation. They look exactly like what they write.

The document is comparing salaries of staff engineers, and EM's. In my experience staff engineer positions are even rarer then EM positions.

The average VC business is not very strong. They rely on power laws.

Normally when you give an unreasonable promise, or have to implement ugly hack then it is known about and explicit that is what is happening. The problems come when you make a unreasonable promise, but no one knows that.

The best AI workflows works heavily with tests at the moment. Having tests up front means the Ai knows its failed, and attempts to fix it.

Isn't fluid intelligence learning? and crystallized intelligence stuff you already know?

It's not one or the other. Those fit in spec driven development already. I have skills that integrate writing and implementing specs.

Promotion at most companies is competitive. So multiple people want the same role. So you need a sorting mechanism.

That's just a bad dev. Good devs don't think of just the happy path. My experience of QA as a quality focused dev has not been good.

Yes

And yet the tolerance for bad decisions is much higher in bigger companies. Make a bad decision at large company and simple intertia will keep you going. Make a bad decision in a small company and you're out of business.

They are talking swapping fields completely like going into plumbing. Not simply picking up new tech.

Intelligence scales with social skills.

Unless you have a condition like autism which allows skewed development, which a lot software engineers do have.

This youtuber has the 9070XT working on the latest steamos https://www.youtube.com/watch?v=_U6-R6XtCUQ&pp=ygUXZXRhIHBya....

I think that's changed recently. Recent release notes state it's added support for RDNA4

The whole point is to just use the steam UI only, and steam deck verified games. Anything else and your on your own.

The difference is they let you if you want to.

Used != Prefer

Lots of places are not like this. I work at a large tech company, at its not like this at all.

My machine is not locked down. I can use vim or whatever ide/editor I want. We don't use scrum/safe, we're expected to contribute to the actual system design. etc If I have a choice, i'm not working at a place like that.

However if you work in dotnet at a traditional "enterprise", it is highly likely to be like this. I have a choice, so i'm not going to choose that.

Wanting replaceable talent drives the tech decisions to only use the "standard" microsoft stack. Other companies value picking the right tool, then teaching people. The best companies don't even care what language you use, and are happy to bring you up speed.

I've found a position that uses dotnet which does not have this culture which is good. But i can totally imagine not picking dotnet to avoid this culture.

When a lot of dotnet shops operate this way the difference is negligible.

I'm not saying all dotnet places are like this, but they are common.

And .NET is the language of choice for "Enterprise". So that's what the majority of jobs are.

Where as large 'tech' companies don't tend to be like this.

The problem is thats how a lot of .net shop operate. I say this as .net developer.

.NET gets selected because a lot of non tech companies need to do software things, and they pick the stack fits in with their current WinTel stack. The main concerns is having replaceable talent to reliably do x. They're not trying to innovate. They are often doing something like sending out insurance quotes by email. They do this by having strict processes, and having developers stay in their lane. Expect rigid scrum, using dependencies only supported by Microsoft etc, Locked down Dev machines with visual studio only, ask for microsoft dev certs, and expect pre-approved enterprise design patterns up the wazoo. They don't want innovative developers, they want you to fit into the pre existing framework designed by an architect. Your skills can die in such an environment.

There are companies that use .NET that aren't like this, but you have to go out your way to find them.

After 100k, you get childcare benefit removed. This mean less money you pocket going from 99999 to 100k.