lulzx.comwriting →
← writing

Take the break

seedApr 20252 min read

In 2021 I stopped coding for three months. Didn't touch a keyboard. Didn't think about software. Just existed.

When I came back everything was clearer. Problems that felt impossible before were obvious. Code I'd been stuck on for weeks wrote itself in an afternoon.

I had been sitting inside those problems every day. The same files. The same wrong shape. A weekend off does not move that. The loop is still loaded when you open the laptop on Monday. Three months emptied it. I could see the extra layer I had been defending, the function that should have been deleted, the approach that only made sense because I was tired of starting over.

The work keeps running after you close the lid

A bad week is a bad week. What wrecked me was the stretch where nothing ever fully stopped. The bug stayed in my head in the shower. The unfinished CLI sat on the desk I walked past. Sleep did not reset it. A long weekend did not reset it. I came back sharper because I had actually left. The stuck work had time to go quiet. When I sat down again I was looking at the problem, not at my last failed attempt to solve it.

The break wasn't wasted time. It was the most productive thing I did that year. My brain needed space to reorganize. I did not earn that by grinding harder in month two. I earned it by stopping.

I watch for the stretch where I am still typing and no longer want the file. That is late. The three months were what late looks like when you ignore it long enough.

Off means off

Now I take breaks before I need them. A week off every few months. No guilt. No "just one quick fix." Off means off. The quick fix is how the week becomes a half-week and the half-week becomes another quarter of running hot. I close the laptop. I do not peek at CI. I do not reply to the "tiny" review. I do not "just check" the bot logs. The queue can wait. If it cannot wait, I did not actually take the week.

I still like building. That is why the stop has to be real. A machine can run until a disk dies. I get worse first. The diffs get sloppy. The obvious fix hides. I start protecting work I should throw away. Then I am three months away from a keyboard again, or I am shipping that version of myself into a client repo.

Take the week while you still want to come back. The afternoon where the old problem writes itself is the return on leaving it alone.