INFORMAZIONI SU QUESTO EPISODIO
When AI makes writing code faster, how do you decide whether your team is building the right thing?
In this episode of Tech Talks Daily, I speak with Johnny Halife, CTO at Southworks, about what happens to software engineering when code generation becomes easier but decisions still require experience. The pressure to deliver faster is familiar. The harder question is whether teams have the review capacity, testing processes, and deployment infrastructure to turn that extra output into useful software.
Johnny describes a different way of directing AI coding agents. Engineers need to specify the outcome, define what finished work should look like, and provide checks that can show whether it meets the required standard. Constantly telling an assistant what to do next can keep a person busy without giving the system enough responsibility to complete a coherent piece of work. We discuss how to create tasks that are small enough to review and substantial enough to delegate.
We also talk about context. Giving an AI system access to institutional knowledge sounds sensible, but adding every document to every conversation creates its own problems. Johnny describes borrowing from open source contribution practices, including README files, contribution guidelines, and records of architectural decisions. His approach combines an explanation of why the system works as it does with directions for finding additional information when needed. It is a useful way to think about onboarding an agent without expecting it to absorb the entire history of a business at once.
The phrase human in the loop comes up frequently in AI discussions, so I ask what it should mean in practice. Johnny describes checks before work begins and a review of test results and other evidence at the end, supported by progress updates along the way. The person responsible needs to set expectations and assess the outcome. Being available for an alert is only one part of that responsibility.
An unnamed streaming platform project provides a practical example. Johnny explains how Southworks developed the supporting process in stages, improving documentation, tests, and the infrastructure around the developer workflow. He reports a tenfold increase across requests, changes, and delivered value, although we do not have an independently verified measure or a detailed breakdown. His broader observation is that the same improvements made the environment easier for human engineers to understand and work in.
Finally, we discuss hiring and professional development. Johnny values software and cloud knowledge, curiosity, clear writing, time management, and the judgment to choose between competing possibilities. AI can make experimentation quicker, but someone still needs to decide which experiment deserves attention and when to stop.
I would love to hear how this compares with your own experience, so please share your thoughts. Where does work now wait in your engineering team, and how are you helping people make better decisions about what to build?
