Episodes tagged: Productivity

We look at a cost that never shows up on any report: the wreckage an interruption leaves behind. Not the thirty-second question, but the twenty-minute rebuild — and why unpredictability, not volume, is what really destroys deep work.

Too many meetings, too little work getting done. James rants about the meeting culture plaguing software teams.

Being busy isn't the same as being effective. James discusses what separates truly productive teams from those just spinning their wheels.

Everyone's talking about AI making developers more productive. But what's the reality? James dives into the hype vs. reality of AI-assisted development.

In this episode we talk with Jay Miller about productivity for developers

In this episode we talk about how many hours you should be working.

This weeks topic is Reactive vs Proactive, whats the difference should I be one or the other or both as a developer? Good developers aim to be proactive, but great developers are able to switch between being reactive and proactive, but what does that even mean?

In this episode we discuss what the difference between Urgent and Important is, and how to use that to be more productive.

In this episode we talk about ways for you to be more productive.