Some days I open my codebase and I genuinely ask myself what I am even building.
Not in a motivational crisis kind of way. More like a quiet, dangerous kind of doubt. The kind that doesn't scream at you, it just sits there. Whispering. Is this even worth it?
I am building Limbo. A smart contract security auditing platform. Four tools running simultaneously across your entire codebase, every finding verified by Foundry before it touches a report. I believe in it completely. And some days it still feels like I am building something nobody asked for in a room by myself.
That feeling is normal. What you do with it is everything.
Here is what I figured out.
Developers are really good at one thing nobody talks about, getting bored of their own ideas. You start something, the first week is electric, the second week is okay, the third week you are already thinking about the next thing. The idea that felt like your life's purpose is now just another folder on your desktop.
The problem is not laziness. The problem is that you are letting your feelings run the project.
The day the idea thrills you, you work. The day it does not, you vibe. And slowly, without realizing it, you have built a system where your progress depends entirely on your mood. That is not a project. That is a hobby with ambitions.
The fix I found is embarrassingly simple. Daily limits.
Pick your number. Mine is 5 hours. Every single day, 5 hours goes into Limbo. Not because I feel like it. Not because the idea is exciting today. Because that is the rule.
The day you are locked in and everything is clicking, follow the rule.
The day you are questioning everything and nothing makes sense, follow the rule.
The rule does not care how you feel. That is the whole point.
And what happens when you just follow the rule every day is something nobody tells you about. Progress starts to feel like evidence. You look back two weeks and Slither is working. You look back a month and Mythril is working. The doubt does not disappear but it gets quieter because now you have receipts.
I also have an ego that refuses to let me quit something I love.
That sounds like a flex but it is actually just stubbornness with direction. Limbo is not something I started because it seemed profitable or because someone told me to. I started it because I felt the problem personally. I was a security researcher putting my name on AI-generated audit reports and getting beaten to findings every single time. That pain is real. That pain keeps me going on the days the code makes no sense and the tools are disrespecting me.
If your idea does not have that kind of root to it, the daily limit alone will not save you. You need a reason that does not expire when the excitement does.
So here is the actual system:
Find the thing you genuinely love building. Not the thing that looks good on Twitter. Not the thing you think will make money. The thing you would still be building if nobody was watching.
Set your daily hours and treat them like a meeting you cannot cancel.
Track your progress every single day. Not to feel good about yourself. To have evidence when the doubt comes back.
And when the doubt does come back, because it will, do not fight it. Just open the codebase and follow the rule.
Limbo is still not finished. Echidna and Halmos are still giving me problems. But I have not missed a day. And that matters more than any single breakthrough.
Lock in. Follow the rule. Love what you are building.
The rest will come.
Top comments (0)