How I Built a Daily Coding Habit (And Stopped Abandoning Side Projects)

How I Built a Daily Coding Habit (And Stopped Abandoning Side Projects) I have started and abandoned more side projects than I can count. The pattern was always the same: a burst of motivation on a weekend, three intense coding sessions, then nothing for two weeks. By the time I came back, I had lost all context. The codebase felt unfamiliar. The enthusiasm was gone. Another repo joined the graveyard. The problem was never ideas or technical skill. It was consistency. I could write code for eight hours when I was excited, but I could not write code for thirty minutes when I was not. And "not excited" describes most weekday evenings after a full day of work. What changed was not willpower. It was systems. Specifically, separating what I need to do (tasks) from what I need to repeat (routines), and scheduling routines like immovable blocks in my week. The Task vs. Routine Distinction Most to-do apps treat everything as a task. "Implement auth flow" sits next to "practice algorithms" in t