Doing work in a phased "assembly line" style is better!
If there’s one thing I’ve learned, it’s that if I can find a way to do all of one part of a task all at once, it lets me get good at (sometimes even automate) that task.
For example, if I need to do X, Y, and Z to 20 files, I find it’s often way easier and less stressful to do X 20 times, Y 20 times, and Z 20 times, even though it may well mean opening files 60 times instead of 20. In other words, grouping by task rather than file works way better for my brain.
(Arguably there’s some crossover here with CPUs and Data-Oriented Design?)
Anyway, I’m switching the aforementioned htmx demo work to three distinct phases:
As soon as I made the decision, it was light a weight fell off my shoulders and I immediately created the next demo section. (Some creative ideas also occurred to me, of course, so I left myself hints for the next phase.)
Don’t our brains thrive on spontaneity and hate repetition? I guess it’s not so clear-cut. I certainly hate to do something like solve 20 longhand division problems in a row.
And real assembly lines are probably hell on the body, unless you design the process carefully:
But some manual tasks can be zen-like when you get into them. And for some reason, that seems to apply to some mental tasks, too. There’s something pleasurable about a task that is going well and smoothly. The opposite is interrupted, exception-filled, branching work, right?