Episodes tagged: Software Development

As AI becomes embedded in software development, ethical questions arise. James discusses the moral considerations teams should be thinking about.

Technical debt accumulates in every codebase. James discusses who's responsible for creating it and who ultimately pays the price.

James takes a cynical look at the current state of software development in 2026. What's working, what's broken, and what needs to change?

AI coding assistants are transforming how we write software. But are we developing a dependency that weakens our fundamental skills? The answer, like most things in technology, is nuanced.

The office isn't coming back the way it was. Remote and hybrid work is here to stay. The question isn't whether to adapt, but how to build strong teams without shared physical space.

The gap between what developers understand and what clients understand isn't just a communication problem—it's often the root cause of failed projects. Bridging this gap is everyone's responsibility.

Not every project deserves to be finished. Knowing when to walk away is as important as knowing how to build. The sunk cost fallacy has killed more good ideas than any technical failure.

Every successful product is defined as much by what it doesn't do as by what it does. Learning to say no is the most important skill in software development.

Good documentation is as important as good code. Yet it remains the most neglected aspect of software development, treated as an afterthought rather than a core deliverable.