The week of 200 commits

There are normal weeks and there are weeks where something inside you breaks — in the good sense. Where you sit down at 8 in the morning and when you look at the clock again it's 2 AM the next day. And you aren't tired. You're on another frequency.

This was one of those weeks.

I won't go into details about what I was building. It doesn't matter. What matters is the mental state. Because anyone who has had a week like this knows exactly what I'm talking about: that zone where decisions flow without friction, where problems show up and resolve almost by inertia, where every finished thing feeds the next one.

Psychologists call it flow. Mihaly Csikszentmihalyi wrote a whole book about it. But honestly, the word falls short. Flow sounds like a calm river. This is more like a controlled fire.

The cost of obsession

Let's be honest: nobody has a week like this without sacrificing something. You sleep less. You eat weird. Your social life shrinks to "I'll text you later". The gym becomes something you'll "pick up Monday".

And here's where the people who don't build things tell you that "you have to balance". That "health comes first". That "no project is worth your wellbeing".

They're right. In general.

But there are moments where balance is the enemy of momentum. Moments where the right thing — the strategically right thing — is to let go of the brake and let inertia carry you. Not as a lifestyle. As temporary tactics.

Nietzsche talked about amor fati — loving your fate, even the hard parts. I'd add something: loving the intensity when it arrives. Not resisting it. Not trying to domesticate it with "wellness" routines. Riding it like a wave and squeezing everything out of it before it passes.

Because it always passes.

The difference between busy and productive

Being busy 80 hours a week is not the same as having a 200-commit week. Most people who work "a lot" are spinning in circles — answering emails, attending meetings about meetings, moving things from one column to another on a Jira board.

A real production week feels different. It feels like you're creating mass. As if every hour added real weight to something that didn't exist before. You aren't maintaining — you're building. You aren't reacting — you're deciding.

There's a Paul Graham line that stuck with me: "The difference between a maker and a manager is that the maker needs long uninterrupted blocks of time, and the manager needs short fragments." A 200-commit week is what happens when a maker has a whole week of long blocks. No interruptions. No meetings. No one asking for "just a minute".

It's almost obscene what you can do when no one interrupts you.

What no one tells you about building something of your own

When you work for someone else, your productivity has a ceiling. You can be the best on your team, deliver double, stay late — and your compensation rises linearly, if at all. Your effort goes through a filter of corporate politics, budgets, and the speed of the slowest employee on the team.

When you build something of your own, there's no ceiling. But there's also no floor. Every hour you invest is a bet. You don't know if what you're building at 2 AM is going to matter or if it's a feature nobody asked for. There's no boss to validate. There's no sprint review where someone says "good job".

It's just you, your code, and the constant question: is this good enough?

That question is simultaneously the best and the worst thing about building something of your own. The best because it pushes you to standards no employer would demand. The worst because it never shuts up.

The trance of the night creator

There's something about the night. It isn't just that there are fewer distractions — it's that your brain works differently after 11 PM. The rational part relaxes a little. The internal editor lowers its guard. And then you start making bolder decisions, writing braver code, solving problems that during the day seemed impossible.

Yes, sometimes those night decisions are garbage and the next day you revert them. But sometimes — more often than people admit — they're brilliant. Because the night takes away the fear of breaking things.

Kafka wrote at night. Balzac got up at 1 AM. Tesla slept two hours. I'm not romanticizing insomnia — I'm saying there's a pattern. The ones who build things that matter have a strange relationship with the clock. Time stops being something you "manage" and becomes something you use until it runs out.

And then what?

The week ends. Friday arrives and you look back and there's something real that didn't exist before. Something that works. Something that solves a problem. Something that has your invisible signature on every line.

And you feel a strange mix of pride and emptiness. Pride because you did it. Emptiness because the intensity goes away and you go back to the normality of sleeping 8 hours and answering emails and doing things "at a healthy pace".

But something changed. Not just the project — you. Every week like this shows you a little more of what you're capable of. It recalibrates your standard of what "a lot of work" means. It ruins comfortable mediocrity for you forever.

And you can't go back.