

Writing code was never 100% of the job. The hard part of software engineering is understanding the problem and figuring out the most elegant path to solve it. If AI can do the code-writing part faster, then it’s a good tool to use.
I still spend a third of my week in meetings. I put out on-call fires late at night.
I also spend a good chunk of my time interviewing potential hires. I pretty much expect them to use AI for their code assignments. Including prompt history is a plus if they do. What I do gauge is their ability to explain their code, defend the decisions and know how to adapt to changing circumstances.
I know how to get to this point by starting a couple of decades ago. I do recognise that I don’t have the same grasp of our codebase as if I had written it by hand. I do review everything that gets deployed, but the volume is higher and it doesn’t stick as well.
I don’t know how to get in as a jr today. We’ll know in a few years how it’s done. It’s a new landscape, but if you’re passionate about the field you’ll figure it out.


Remember back when almost every scholar was employed copying books by hand? And then this jerk invents the print press.
The economy didn’t collapse and everyone suddenly had access to more books for cheap. Scholars could spend their time reading books for the sake of reading, not just copying them. They could spend time writing their own books.
Going forward we’ll just have the means to get more done.
There will still be jobs to do. We just don’t have titles for them yet. If I told my grandma back when she was alive that I’m a web developer, she’d think I’d lost my mind and become a spider.
We’re in a slightly better spot now where we have the means to feed and pay everyone without them necessarily having a job. There needs to be a political to do so, though.