And if you hire engineers that only know how to use AI (or make all your engineers use it), then the AI companies own you.
If you hire a software engineer and they apply their software engineering practices, they should be able to do a pretty damn good job. I remember when I started 18 years ago. I was able to achieve the impossible just by applying best practices and planning before even writing one line of code. Basically doing the “engineering” part. In parallel I’d study the language, do some POCs and I was still able to deliver on time.
But, it all depends on who you end up hiring. Not everyone is as diligent.
Where I have failed is when managers expect miracles to be delivered within impossible timelines. At first you trust their judgment thinking that they know how much time something takes to make, but they make bullshit estimates to look good and then blame you when it’s not delivered on time.
The only thing senior engineers have is a bullshit detector and the ability to say no because they actually know from experience how long it takes to do something. It’s not necessarily about their ability to do it, it’s their ability to argue back.
Software engineering back then sounds like academia
They don’t care because they think they’re gonna be able to replace them, too. They’re wrong, but that’s not gonna stop them.
Every junior you don’t hire today is a senior you’ll have to overpay for in three years.
A junior becomes a senior in 3 years? Unlikely. I’d say mid-level in 5. What kind of finger-painting has a junior fully capable of coding any part of a project and mentoring mids in only 3 years?
The kind that fired all the other juniors and then had the seniors quit
I’m against AI, but I do appreciate this nuanced, realistic, balanced opinion.
That’s a good thing


