@h_thoreson software engineers will increasingly become systems builders. We're not going away but the job is going to change a lot.
With a few exceptions, it's going to be tough to make a career out of being an expert in the minutiae of $tech_stack. A good senior eng can use a coding agent to fluidly move between tech stacks they may not actually know very well.
@h_thoreson fully agree with @nocoursewalks. Yesterday I managed to add an incredibly complex feature to a Python app just using AI and a knowledge of coding practices.
The broad strokes will be enough to get most things done. I’m sure you’ll still get artisanal hand coders that will charge a premium, but the majority of developers will be doing some kind of assisted development.
I’m starting a new job next month, my first non-contract job since 2001, and I’m going to try and position myself as a team lead for small group working on agentic development. I think in five years time if you’re not working in some form with AI, then you’re not working.
@DavidAnson @gary_bbgames @h_thoreson expertise still matters! And it's not like we live in a binary world where code is either hand rolled or vibe coded.
Most of my prompts are to reduce toil, like "rewrite this function to use <type> instead of <ugly type>" or to replace search like "this function has <issue>, suggest some fixes." It is faster and less effort and I don't get bogged in minutiae. I hand edit after each prompt as needed.
I was a hard skeptic three months ago, not anymore.
@DavidAnson @nocoursewalks @h_thoreson this is the best attitude to have. Keep an eye on it, be wary and verify everything… but it’s a tool that has gone from little use to over half my time in the last 3 months.
The speed of improvements is scary.