To some extend, you're right, but I'd still say that pre AI you had to at some point to write some notes, come with a plan and read more code.

I've always found an enormous amount of good practices (not just engineering ones) in aircraft operations and engineering that would be applicable to software engineering.

I've always day dreamed of an IT organization that combined those with the decision-making procedures and leadership of modern armies, such as the US Army one.

I've re-read multiple times FM22-100 which I find strikingly modern and inspiring:

https://armyoe.com/wp-content/uploads/2018/03/1990-fm-22-100...

While I do understand that business leadership cannot compare to the high standards of those required by way more important stakes, I think there's many lessons to learn there too.

My experience is that juniors have an easier time to ramp up, but never get better at proper engineering (analysis) and development processes (debug). They also struggle to read and review code.

I fear that unless you heavily invest in them and follow them, they might be condemned to have decades of junior experience.

It was already dying and with no chances of making up share, most online usage comes from mobile, nobody cares about installing Firefox there but us nerds.

So they need some kind of pivot.

Gemini 2.0 flash was good already for some tasks of mine long time ago..