spacekitcat

That feels like a bold and possibly dangerous thing to say without evidence.

I think an important factor is how fast the team need you to hit the ground running.

Where there’s time for new developers to get up to speed with a new tech stack, I completely agree with you.

I think the biggest hurdle going from Java to C# is how you think about asynchronous code, more so for desktop software. My last role was C# with me coming from Java and I got a few rude awakenings.

From this day forward, I will refer to this sort of attack as a PiTM attack. Not much you can do to stop me I'm afraid.

So long as you expand the acronym in the first use, no one reasonable cares.

Eh, you don't get to control the language of others. If someone wants to say PitM, that's their business.

Yes, I feel a bit robbed by 90s computers when I pick up old manuals or cheap programming books for things like the BBC Micro.

I’m jealous that older generations get to say they wrote their first program on iconic hardware. Computers of my time were much faster, but they were very generic.

We do RFCs, I dislike the concept. It feels like an extension of this troubling trend of taking away autonomy from engineers.

Big brain comment here.

Listen, I know what I’ve experienced.

Edit: No actually, I can't understand what this is? You are trying to convince me my experiences are wrong. You don't seem to actually want to understand my point of view, so what is this? Why are you wasting both of our time like this?

Striving to build an environment where effort is made to attribute credit where it's due and to strive for equality of outcome for all is what we need to do. You're still picking the 'best person for the job' according to your own biases for what constitutes the 'best' (because how else could it work?), but you're also making an effort to ensure that your team/department/company isn't just all white (straight etc) men.

I think proponents of meritocracy are naive.