Shipping Without Burning Out: The Rhythm I Keep

This is my fifth year as a freelance engineer with long-term clients. The hardest thing to sustain is not technical quality — that can be trained. It is the rhythm.

My day in three blocks

1. Morning (07:00 — 11:00): deep work. No Slack, no email. I stash two or three of the hardest tasks here.
2. Midday (13:00 — 16:00): collaboration and code review. I open every comms channel and answer in batches.
3. Late afternoon (16:30 — 18:00): light tasks, documentation, and prep for tomorrow.

Small rules with big payoff

• No personal notifications on the work laptop. Consistency makes focus recover in seconds.
• Close the laptop before dinner. Work will always be there; the body will not.
• Schedule breaks. I run a 90-minute ON / 15-minute OFF timer. This ultradian rhythm variant helps a lot.

Weekly: one learning day, one empty day

Every week I set aside one day for learning (reading papers, trying a new runtime, writing posts like this one) and one day completely empty of client work. That empty day is what keeps me fresh for the following week.

Measure energy, not hours

I stopped tracking work hours back in 2022. I track energy on a 1-5 scale. Days I score 4 or 5 are days where deep work feels effortless. More than three days at 2 in a row is my signal to pull back before quality drops.

A long engineering career is built on rhythm, not productivity bursts. Slow and consistent — that is the luxury worth defending.