
AI is putting me through the 5 stages of grief!
Coding Chats Episode 85 - John talk to Ian, a 51-year-old software engineer with 25 years of experience, who describes going through something like grief as AI takes over work he spent decades mastering. He no longer reads the code it writes, which leads him and host John to debate when that’s acceptable and when it isn’t. Ian calls the pace of change “exciting and terrifying at the same time.” John argues the grief is unwarranted: cheaper software will mean more to build, and engineers still own requirements, testing and delivery. They disagree on a few points, such as on-the-fly user interfaces, but both lean optimistic about the profession, and agree to revisit their predictions in two years. 00:00 – Welcome and why Ian is "grieving" over AI in software development 03:11 – Do we still need to read the code? Trust, outcomes and safety-critical systems 06:15 – Code review in practice, and what makes someone an engineer 10:21 – Requirements, analysts and the full software lifecycle 13:41 – From punch cards to DevOps: the pace of change 18:22 – Why requirements work stays human (the drill bit story) 20:29 – Is English the programming language of the future? 23:04 – How much software will be written? The spreadsheet analogy 27:05 – Do we still need tests? UI stability versus custom UIs 29:23 – Demand for software and the future of junior developers 35:18 – UIs that evolve with the user 40:24 – Internal tools, AI-generated software and the "mainframes of the future" 43:01 – Training juniors and long-term demand for engineers 44:06 – Missing the craft: coding as a hobby 46:21 – Adapting to industry-wide disruption 48:00 – Wrap-up and a two-year follow-upIan's Links: https://www.linkedin.com/in/%E2%80%8Bian-miell-694496/ John's Links: John's LinkedIn: https://www.linkedin.com/in/johncrickett/ John’s YouTube: https://www.youtube.com/@johncrickett John's Twitter: https://x.com/johncrickett John's Bluesky: https://bsky.app/profile/johncrickett.bsky.social Check out John's software engineering related newsletters: Coding Challenges: https://codingchallenges.substack.com/ which shares real-world project ideas that you can use to level up your coding skills. Developing Skills: https://read.developingskills.fyi/ covering everything from system design to soft skills, helping them progress their career from junior to staff+ or for those that want onto a management track. Takeaways AI coding tools have gone from a helpful accelerator to something that can work across whole microservice codebases, which is why experienced engineers are feeling real grief. Whether you need to read AI-generated code depends on the stakes: skip it for a throwaway tool, read every line for safety-critical systems. Human code review has always been weak, with big pull requests tending to get a rubber-stamp “LGTM”. Engineers have always been the people who care what’s under the hood, but where that “hood” sits keeps moving up the stack. Requirements gathering, such as finding out what customers actually need rather than what they ask for, remains a core engineering skill that AI doesn’t replace. Cheaper software could create more demand for engineers, much as spreadsheets led to more accountants rather than fewer. Junior developers can still learn by starting at a higher level of abstraction and working down, as earlier generations did with BASIC, C and assembler. Part of the grief is losing the craft of writing code by hand, though coding can survive as a hobby, like Sudoku or crosswords. The pace of change is dizzying and no one can say what software will look like in two years, so the hosts agree to revisit their predictions then.