The Real Cost of Context Switching
Developers spend 10+ hours per week in meetings and lose 23 minutes refocusing after each one. Here's the real cost of context switching.
Blog
Short, practical reads on building, shipping, and working together without unnecessary process.
Developers spend 10+ hours per week in meetings and lose 23 minutes refocusing after each one. Here's the real cost of context switching.
The Slack + Notion + GitHub Issues stack your small team cobbled together is not a system. Here's what a focused tool stack actually looks like.
Paul Graham wrote about the maker's schedule in 2009. Fifteen years later, we're still scheduling standups at 9:30am and wondering why developers can't get into flow before lunch.
We tested Geekbot, Range, and DailyBot for 3 months each. They're all fine. But the real question is whether async standups are worth doing at all.
I asked 50 developers what they'd use if Jira disappeared tomorrow. Not one of them described another project management tool. Here's what they actually want.
The average developer spends 10.9 hours per week in meetings. We did the math on what that costs in shipped code, focus time, and morale.
You duct-taped Slack, Notion, and GitHub Issues together and called it project management. It's not a system — it's three tools pretending to talk to each other.
Every year a new tool promises to be "Jira but simpler." The problem isn't Jira's complexity — it's the assumption that your team needs project management software at all.
Tools should support decisions and delivery, not become the center of the work day.
Teams can handle hard work. What hurts motivation is effort that does not feel meaningful.
Every new tool solves one problem and creates a few new ones if the team is not careful.
You start the day with noise before real work even begins. Here is why that happens and how to fix it.