The Productivity Trap — What Actually Works for Me
I spent a long time confusing planning with doing. Building the perfect task system, the perfect template, the perfect folder structure — and then never using any of it. Here’s what I eventually figured out about how I actually work.
The Exam Period Paradox
During exams (high pressure, no free time): I’m weirdly productive on side projects. I reorganize my Obsidian vault, fix my terminal setup, start new repos. Energy is high. Focus is sharp. Constraints force efficiency.
After exams (theoretically unlimited time): Nothing gets done. Tasks pile up. I play Mobile Legend and feel guilty about it.
This confused me for a long time until I understood it: work contracts when there’s no time, and expands when there’s too much of it. During exams, I have one free hour so I use it intensely. After exams, I have “all the time” so nothing feels urgent and nothing gets started.
This isn’t a character flaw. It’s how my brain responds to different conditions.
The Setup Addiction
My real problem: I’m addicted to setup mode. The home server “for years,” the router configs, enhancing Open WebUI, exploring Docker — these live in my head as perfect future projects. But the moment I’d actually start, they become messy, imperfect, real. So I keep them in planning mode where they stay clean. (I do the same thing with my Obsidian vault — reorganizing it is easier than actually writing in it.)
That Later tag in my task list? It was a graveyard, not a parking lot. If I hadn’t done it by now, I wasn’t going to. The tag just carried guilt.
What Actually Gets Me Moving
Looking at the things I did finish, there’s a clear pattern. I get stuff done when I:
- Just start without permission from myself. The genetic algorithm project, the TOTP security setup, KeePassXC — I didn’t plan these, I just did them.
- Have a real reason. New laptop? Immediately try everything. Got a router? Now the server happens.
- Hit a constraint. One free hour between lectures? That hour is gold.
I don’t get stuff done when I “schedule time for it” or “add it to the plan.”
The Rules I Settled On
The 5-minute rule. Don’t “Start Home Server Setup.” That’s too big. Instead: “Spend 5 minutes looking at one tutorial.” If I do more, great. If not, I still broke the seal.
Kill the Later list. Go through every Later task. Ask: “Would I do this today if I had 30 minutes?” Yes → move to daily note. No → delete it. “Maybe” and “I should” are both no. (This got a lot easier once I separated tasks from goals — most Later items were goals pretending to be tasks.)
One active project. I had genetic algorithm, home server, router setup, Open WebUI, WSL scripts, Docker, video compression API — all “in progress.” Pick one. The dopamine from completing beats the dopamine from collecting.
Start messy, ship broken, fix later. My genetic algorithm project was “risky and stupid” (my words) and I did it anyway. That version of me gets things done. Be him more often.
The Hard Truth
Every “Later” task is a lie I tell myself. Every “Explore X” is postponing. Every “Enhance Y” is avoiding shipping.
But — I simplified my daily note template one day by removing all the friction and just writing. And it worked. That was me choosing action over perfection. The goal is to do that with everything else.
See Also
- How I Accidentally Became a DevOps Engineer
- Tasks vs Goals vs Projects — the fix that made the system actually work
- Organizing an Obsidian Vault — another case of setup mode disguised as productivity
- Obsidian Dataview Queries