The Guilt of Not Coding on Weekends

Two Hours on the Couch

Saturday afternoon. Watching Netflix. Two hours straight.

Not bad. Comfortable, even. But a small voice nags from the back of my mind. "You could be working on your side project right now." "You still haven't looked at that tech you planned to study this week." "Your GitHub contribution graph is getting sparse."

I set down the remote. Guilt rises. The guilt of doing nothing. I'm resting, so why does resting feel uncomfortable?

The Invisible Pressure of "1 Commit a Day"

Developer communities have an invisible pressure.

"One commit a day." "Daily TIL entries." "Weekend side projects." "Solve algorithm problems in your spare time." These are framed as advice, but on the receiving end, they feel like obligations.

Skip them and you feel like you're falling behind. It seems like everyone else is doing it except you. But is everyone really? Social media only shows people who code on weekends. That's because that's how social media works. The person lying on the couch watching Netflix doesn't post about it.

You only see the people running, but far more people are resting. (I know this rationally, but my heart doesn't always follow.)

Your Brain Needs the Downtime

Muscles don't grow during exercise. They grow during rest. Muscle fibers tear during training and rebuild stronger during recovery.

The brain works similarly. After learning new information, sufficient sleep and rest are needed for memories to transfer into long-term storage. You ran your brain at full throttle for five weekdays. Code again on the weekend and your brain never gets a chance to organize.

That Monday fatigue might not be physical tiredness -- it might be information overload that never got processed.

Where Does This Guilt Come From?

Comparison. The anxiety that everyone else is growing while you're standing still.

An uncertain future. Because this industry moves fast, the fear that stopping means getting left behind.

How you measure your own worth. The habit of only valuing "productive me" and not "resting me."

But rest can be productive too. No -- rest is a prerequisite for the next round of productivity. Don't charge the battery and it eventually dies. Burnout comes for those who don't rest.

Saturdays: No Coding Allowed

I made myself a rule.

Saturday is a do-nothing day. No coding. No tech news. No GitHub. Netflix, walks, naps, games -- whatever goes. This day is officially declared "you don't have to be productive."

At first, it was anxiety-inducing. After about a month, I adjusted. After two months, Sundays and Mondays following a Saturday of rest were noticeably better. Code was clearer. Thoughts were sharper.

The guilt hasn't vanished. But I've gotten used to ignoring it.

I Didn't Put Down the Remote

Back on the couch. I picked up the remote.

There'll be a gap in my GitHub graph. The side project can wait until next week. That tech I wanted to study -- I'll look at it during a weekday lunch break.

Today, I rest. And that's not laziness -- it's strategy. At least, that's what I tell myself.

I pressed play on Netflix. The guilt showed up again today, but I didn't put down the remote.

A small victory.