Connect your Claude, Codex or OpenClaw for full transcripts on millions of podcasts. Two week free trial, cancel anytime.
The InfoQ Podcast · Hands-On Engineering Podcasts · August 2026
Asked to predict how software engineering changes from here, Hast first rejected the comparison between an LLM and a car-welding robot, on the grounds that one is deterministic and the other is not. The advice to calm down comes from a team that uses Claude daily and had spent the episode explaining why they went back to writing code by hand. He followed it by arguing that token prices are still subsidised and that the economics have to change before the tools do.
…why, it will just rub it in your face and okay, because you already did that, so how you taught me. Given that we should wrap up our conversation, what predictions do you have moving forward? You choose the scale in terms of how software engineering will change or how working in a team will change.
…are. Maybe we have to move in that direction. And when they have so much control over the application, then we can maybe verify the solution on another abstraction and then we can take full usage. But I have no idea, and I don't think it's tomorrow. I know I don't think it's next year either.
The problem with car analogy or the robot analogy is that a robot that welds car parts is a highly scripted thing, it's deterministic, it does the same thing every time, while an LLM by nature does not. So, I think, first of all, I would like to say that everyone should probably take a chill pill, just drop the fovo, because I don't think that anyone will be out of a job anytime soon as software developers. I think the term that coding is solved is absolutely wrong. As I said, it's very dependent on context and what you're working with. I think we're still very much in an AI bubble. So, that I think we need to keep calm and carry on and see if the bubble deflates or if the world economy crashes or whatever happens, and then see both what the actual cost of using an LLM will be after. Because if you're not doing the coding, if you're outsourcing the coding…
Thank you. Is there anything else that you would like to add, guys?
Yes, there are two things I like to add. First, it's just the journal where the Synthef published their article is called Journal of Systems and Software, which is a well-respected journal. The other thing I would like to add is that I think we have solved this junior problem in our team. You know…
I know Europe is really warm, but don't just spend the entire summer bibe coding, do fun stuff, see the sun.