Afleveringen
-
Why do performance reviews reward visibility over impact, and why do so many developers leave them feeling misunderstood? In this episode, James unpacks why performance reviews are quietly broken, and what that’s doing to teams.
-
Developers leave jobs all the time, but rarely share the real reasons. James explores why developers quit and what companies miss.
-
Zijn er afleveringen die ontbreken?
-
James takes aim at management practices that are hurting developer productivity and morale. What do managers need to stop doing?
-
James explores spec-driven development and how it changes the way developers actually work with AI tools to build better software.
-
AI can help write code, but it can also make your codebase worse. James explores the pitfalls of AI-generated code and how to avoid them.
-
As AI becomes embedded in software development, ethical questions arise. James discusses the moral considerations teams should be thinking about.
-
No-code platforms promise to democratize development, but they keep falling short. James examines why no-code struggles to deliver on its promises.
-
A gap is forming between teams that embrace AI tools and those that don't. James explores what this divide means for the industry.
-
AI can generate code quickly, but that code still needs experienced eyes. James explains why senior review remains critical.
-
LLMs are powerful tools, but they're not junior developers you can just hand tasks to. James discusses how to think about AI assistants correctly.
-
The AI replacement debate continues. James provides a nuanced take on which jobs are safe and which might be at risk.
-
In modern systems, observability is essential. James discusses why you can't afford to skip proper monitoring and tracing.
-
Cloud costs spiral out of control for many organizations. James explores the common reasons and what you can do about it.
-
APIs are often an afterthought, but they're products that developers consume. James discusses why API design deserves more attention.
-
Clean Architecture became a religion for some developers. James challenges the dogmatic adherence to architectural patterns.
-
The pendulum is swinging back to monoliths. James discusses why monolithic architectures are making a comeback and why they were never really a bad idea.
-
Event-driven architecture is everywhere now. But is it always the right choice? James examines when to use it and when to avoid it.
-
Serverless computing has taken off, but it's often misused. James explores when serverless makes sense and when it doesn't.
-
Microservices promised scalability and flexibility. But for most teams, have they delivered? James takes a critical look at the microservices hype.
-
Too many meetings, too little work getting done. James rants about the meeting culture plaguing software teams.
- Laat meer zien
