Some days I'm excited to code. Some days I'd rather scroll. If my output depended on mood, I'd ship very little.
This post is about building a routine that works on both kinds of day. It isn't a productivity sermon, and it isn't a promise that discipline fixes everything. It's a handful of practical mechanisms, plus an honest note about the limits.
The core idea: don't negotiate with your mood
Motivation is a feeling, and feelings don't follow schedules. Plans that need the feeling to show up will fail on the days it doesn't. Instead, build a system where starting requires almost no decision.
What I do instead of waiting
Define the smallest next task, the night before
Starting is the hard part, and a tiny, clearly defined task lowers the cost. Not "work on the project" but "write the failing test for the dispute timeout." When tomorrow arrives, the first move is already chosen.
Use a timer, and give yourself permission to stop
Set a timer for 25 minutes. You're allowed to stop afterwards. The point isn't the 25 minutes; it's that "just 25 minutes" is easy to agree to, and momentum often carries on. If it doesn't, you've still done 25 minutes, which beats zero.
Remove friction
Editor open, terminal ready, phone in another room. Every step between you and the first line of code is an opportunity for a different decision. Make the desired path the default path.
Count days, not hours
Showing up consistently counts more than a heroic Sunday. A small daily habit compounds; an occasional marathon mostly produces tiredness.
A "minimum viable day"
Decide in advance what counts as a non-zero day. For example:
- Read one file of someone else's code, or
- Write ten lines, or
- Write one paragraph of notes.
On a bad day, hitting the minimum keeps the chain unbroken without demanding energy you don't have. On a good day, you'll naturally do more.
What doesn't work for me
Waiting to "feel ready." Readiness tends to follow starting, not precede it. I've found this idea useful, though you may find the opposite is true for you.
Guilt. Guilt feels like motivation but it's a poor fuel: it makes starting more unpleasant, which makes avoidance more likely.
A note on rest
Burning out helps nobody. I'm not advocating non-stop grinding. On low days, doing less is fine. What deserves attention is doing nothing, every day, for a long time. That pattern usually means something else is going on: stress, sleep, a project you've stopped believing in, or something heavier.
If it's heavier than a motivation problem, talk to someone: a friend, family, a counsellor. A routine can't fix everything, and it isn't supposed to.
A simple weekly check
Once a week, ask three questions:
- What did I actually finish?
- What drained me?
- What's the smallest thing that would make next week easier?
Adjust the system, not your self-worth.
A caveat on advice
Everything above is general practice, not a prescription. People differ: some do their best work in late-night bursts, some in early mornings, some with music, some in silence. The only reliable method is to try one change for two weeks and see what happens.
(This series is itself a small experiment in this idea: one post a day, even when it's modest, because the habit matters more than any one post.)
A sample week (use it as a starting point)
Not a prescription, just a shape. Adjust it to your own life.
| Day | Plan | Minimum |
|---|---|---|
| Mon | 2 focused sessions (25 min × 2) | One session |
| Tue | 1 session on the main project, 1 on learning | Read 10 minutes |
| Wed | Light day: review and tidy | Write 3 lines in the log |
| Thu | 2 focused sessions | One session |
| Fri | Ship something small | Deploy or merge anything |
| Sat | One longer exploratory session, if you want it | Optional |
| Sun | Rest, plan Monday's first task | Write tomorrow's first task |
The "minimum" column is what stops one bad day from ending a streak.
Troubleshooting: when the system fails
"I sit down and still can't start." Make the first step absurdly small: open the file, write one comment, run the failing test. Starting a tiny step beats debating a big one.
"I start but get distracted every five minutes." Put the phone in another room, close the tabs unrelated to the task, and try a shorter timer (15 minutes).
"I'm exhausted, not unmotivated." That's a rest problem. Sleep, food and movement are part of your toolchain.
"I've lost interest in the project." Ask whether it's boredom (push through the dull part with a smaller goal) or a sign it's the wrong project (it's okay to stop, if you write down why).
"I did great for a week, then stopped." Normal. Restart with the minimum day, not by trying to make up for lost time.
A short pre-session ritual
Ten seconds that help me:
- Read the "first task" I wrote yesterday.
- Close everything unrelated.
- Set a 25-minute timer.
- Begin with the smallest piece.
Rituals don't need to be elaborate. They only need to be the same each time, so that starting becomes a habit, not a decision.
Tracking without obsessing
A simple tally of "days I did the minimum" is more useful than hours logged, because it measures consistency. If tracking becomes stressful, stop. A tool that adds anxiety has failed.
When to take a real break
Take time off completely when:
- you're sleeping badly for more than a few days,
- the work feels pointless in a way that isn't going away,
- you're snapping at people or dreading everything,
- or anything in your life is heavier than a project.
A break isn't failure; it's maintenance. Come back with a smaller scope.
The honest summary
Mood is weather and habits are climate. You can't control the weather, but you can build a house that works in all of it.
How do you get moving on a low-energy day? I'd love to steal your best trick.
Top comments (0)