Yesterday, I wrote about how developers use only a few hours weekly to write the code.

It evoked a lot of great comments, like:

– “Coding is a small part of what we do.”
– “Developing is much more than only coding.”
– “Actually coding should be a minor part of great developer time usage.”

That’s all true. The developer’s work is much more than coding, but what these comments missed was that the post was all about *focus* and *productivity*, not coding.

The problem is that distractions are everywhere, and our schedules are so fragmented that we cannot focus on our work — coding, documentation, learning, thinking, problem-solving, or anything that requires our full attention. Fifty-two minutes — it cannot get you even started!

I couldn’t find it in my notes when I first met with Paul Graham’s classic “Maker’s Schedule, Manager’s Schedule”, but it has been an essential resource on understanding my own, as well as any fellow maker’s way of working. I recommend you read it and possibly the Farnam Street excellent blog “Maker vs. Manager: How Your Schedule Can Make or Break You” too, and I promise you will understand my perspective better.

I end this post with Paul Graham’s words:

“All we ask from those on the manager’s schedule is that they understand the cost.” ✌️