How do you avoid doom-coding while learning or experimenting? – Ask HN
Lately I have observed this algo in myself while learning something new. I constantly code for very short bursts sometimes on the phone or laptop at night, keep jumping between tools and end up consuming more than creating. It comes off as productive but seldom compounds.
A straightforward explanation that has provided me with a helpful point of thought is.
Make a mode selection.
Did conclusions actually occur?
Most doom-coding sessions are loaded with input, no closure.
There are 2 small changes that improved it for me.
Start sessions with a small, visible output goal (one function, one note, one commit).
Time-box input aggressively. I stop scrolling after 15-20 minutes of scrolling.
At the conclusion of every session, I would write what I would do next, even if I don’t do it. ~
Wanting to know how others do this.
Do you intentionally separate learning sessions and building sessions?
Do you have any heuristics to know when you have avoided input?
566
393