Re:Maker's Schedule, Manager's Schedule (2009)
by kazinator on Wednesday July 28, 2021 @07:48PM
(#27991170)
I don't think this article tells the full story.
When you love what you're making, you can do it in small increments amid interruptions, and pick up right where you left off. Your brain never leaves "maker mode"; the gears keep spinning in the background while you're away from it.
That's how it's been on my side projects for years.
You might get large blocks of uninterrupted time at a job during weekday office hours, but not in side projects evenings and weekends. Not if you have a family.
When you love the project, you will be surprised at how well you can progress in 5, 10, 15-minute intervals virtually as if they were a single block of time.
I've returned to half-done code (not even syntactically valid), half-written commit messages, debug sessions, and picked it up without skipping a beat.
I think the interruptions are harmful when you're working on something you don't fully understand. You had to ramp up on it quickly, and to get through the task, you're juggling a whole clump of new, unfamiliar information in your short-term memory --- some of it not even proper information, but unconfirmed, competing hypotheses on how various things work. You have to work hard just to build that up so you can navigate and contextualize what you're doing. Much of that short term information can vaporize if you are interrupted.
But that's not exactly the situation of maker. The maker knows what he or she is making. He or she understands the existing thing, inside out; none of that vaporizes due to an interruption.
So how can someone deal with interruptions who is in this situation? I think: write stuff down! Don't carry it all in your head. Document. Open a "knowledge file" and type. If you have three competing, unconfirmed hypotheses about how something works, write them out. After an interruption, you can reload the context by re-reading that file. If you have a plan about what your next steps are, write those steps down. Write down what you've already tried and the results.
When you love what you're making, you can do it in small increments amid interruptions, and pick up right where you left off. Your brain never leaves "maker mode"; the gears keep spinning in the background while you're away from it.
That's how it's been on my side projects for years.
You might get large blocks of uninterrupted time at a job during weekday office hours, but not in side projects evenings and weekends. Not if you have a family.
When you love the project, you will be surprised at how well you can progress in 5, 10, 15-minute intervals virtually as if they were a single block of time.
I've returned to half-done code (not even syntactically valid), half-written commit messages, debug sessions, and picked it up without skipping a beat.
I think the interruptions are harmful when you're working on something you don't fully understand. You had to ramp up on it quickly, and to get through the task, you're juggling a whole clump of new, unfamiliar information in your short-term memory --- some of it not even proper information, but unconfirmed, competing hypotheses on how various things work. You have to work hard just to build that up so you can navigate and contextualize what you're doing. Much of that short term information can vaporize if you are interrupted.
But that's not exactly the situation of maker. The maker knows what he or she is making. He or she understands the existing thing, inside out; none of that vaporizes due to an interruption.
So how can someone deal with interruptions who is in this situation? I think: write stuff down! Don't carry it all in your head. Document. Open a "knowledge file" and type. If you have three competing, unconfirmed hypotheses about how something works, write them out. After an interruption, you can reload the context by re-reading that file. If you have a plan about what your next steps are, write those steps down. Write down what you've already tried and the results.