Stretch breaks for developers and designers who lose track of time

If you code, design or write for a living, you probably know the feeling: you sit down after lunch, look up, and it's dark. Flow is the best part of the job, and it is hard on your body. The fix is not a timer that breaks your concentration on a fixed schedule. It is taking breaks at natural stopping points, like a build, an export or a commit, and using reminders that only count the time you're actually working and let you finish the thought first.

Then, after a long session, give your body five minutes to undo what the last three hours did to it. The routine near the end of this post covers the parts that suffer most: eyes, neck, shoulders, wrists and hips.

Why flow and breaks don't get along

Deep work takes a while to load. You build up a picture of the problem in your head: the call stack, the layout grid, the shape of the argument. An interruption at the wrong moment can throw that picture away, and getting it back takes far longer than the break did. So people who do this kind of work learn, quite reasonably, to protect it.

The trouble is that the body keeps its own time. Hours with the same posture leave the hips and lower back stiff, the neck pushed forward, the shoulders up near the ears, and the wrists and fingers working without a pause. Eyes locked on a screen at one distance blink less and tire. None of this hurts in the moment, which is exactly why flow lets it build up.

The goal is not to break flow more often. It is to break it at the right moments.

Stop at natural stopping points

Most creative and technical work has pauses built in, if you look for them. Each one is a chance to stand up for a minute without losing your place.

• A build or compile. If it takes more than a few seconds, stand up while it runs.
• The test suite. Run the tests, walk to the window, come back to the result.
• A commit or a push. You've just closed a small loop. That is a natural seam.
• Opening a pull request. The work is out of your hands until someone reviews it.
• An export or a render. Designers and video editors get these built in. Use them for a stretch, not for checking messages.
• Saving a version. A design file milestone, a draft sent for comments.
• The end of a section. For writers, the end of a paragraph or a scene.

Leave yourself a way back in

A break is easier to take when coming back is easy. Before you stand up, write the next step down: a comment in the code saying what you were about to do, a sticky note on the artboard, a line at the bottom of the draft. Many writers stop on purpose when they know what comes next, so that the next session starts easily, and the same trick works for code and design. With a note in place, the break costs you almost nothing.

Why reminders work better when they wait for active time

A plain timer doesn't know anything about your day. It goes off in the middle of a meeting, while you're making lunch, two minutes after you came back from a walk, and in the middle of the one line you've been trying to write for ten minutes. Many people who do deep work end up switching such timers off, and fair enough.

A reminder works much better when it:

• Counts only active time. Time spent away from the keyboard is not time spent sitting at it.
• Waits for a real stretch of work. A stand up prompt after an hour of continuous work means something. One on the hour, whatever you were doing, mostly doesn't.
• Can be put off without guilt. If you can say "in a moment" and get reminded once more, you'll finish the thought and then go.
• Stays out of the way when it should. On calls, in presentations, when you're not there.

This is roughly how the Movement characters in Notchpals behave. Take Bizzy, a bumblebee who thinks you and it are the busiest team ever. Its Stand up visit comes only after 55 unbroken minutes at the Mac, and the clock ignores time you're not there: two minutes without touching the keyboard or mouse and Notchpals treats you as away. Stretch visits are rationed from one daily allowance shared across the whole crew, so there's no stream of interruptions.

BizzySo much typing! Your fingers out-buzzed ME! Shake them out! Now!

If it arrives mid-thought, press Later. Bizzy takes it well.

BizzyOkay, later then! I'll return soon, buzzing gently. Very gently.

Twenty minutes later it checks back once, if the reminder still applies, which is usually long enough to reach the next commit. Press Later again and it drops the subject.

Two of the quiet rules matter for this kind of work. Nothing visits while the microphone or camera is on, so a pairing call or a design review over video goes on undisturbed. And nothing visits while the app in front on the notch's display is in full screen. That suits presenting, but if you live in a full screen editor or canvas all day, the reminders wait until you leave it, so a normal window may serve you better. If you have Bolt for Focus, the menu bar can also start a 25-minute or 50-minute focus session. While it runs, Bolt's own visits still come, and so do a critically low battery and a meeting that is about to start. Everything else waits.

A five-minute routine after a long session

When you do surface after a couple of hours, run through this before you sit back down. Move slowly, and stop anything that hurts.

1. Stand up and walk. Go and refill your water, the long way around. Thirty seconds of walking gets the blood moving before you stretch.
2. Look far away. Find a window or the far wall and look at it for twenty seconds, blinking slowly a few times. This is the 20-20-20 rule done once, properly.
3. Neck. Tip your right ear toward your right shoulder and hold for a slow breath or two, then switch. Then tuck your chin back gently, as if making a double chin, and hold for a few seconds.
4. Shoulders and chest. Roll your shoulders back a few times. Then stand in a doorway, put your forearms on the frame at shoulder height, and step forward until you feel a stretch across your chest.
5. Wrists and forearms. Hold one arm out, palm down, and use the other hand to ease the fingers gently toward you. Then palm up and repeat. Switch arms. Finish by spreading your fingers wide and making a loose fist a few times.
6. Hips. Step one foot back into a short lunge, keep your back upright, and tuck your hips under slightly until you feel a stretch at the front of the back leg's hip. Hold, then switch.
7. Calves. Rise onto your toes and lower slowly, ten times.

That's it. Five minutes, and you'll come back to the desk looser and with fresher eyes. For more desk stretches with clear steps, see the two-minute desk stretches.

Make the long sessions a little kinder

A few setup habits make the stretches less necessary to begin with.

• Keep water on the desk, but not too much. A glass, not a two-liter bottle, so refilling gets you up.
• Use keyboard shortcuts. Every shortcut you learn is a mouse trip your wrist doesn't make. There is more on the hands in wrists, keyboard and trackpad.
• Raise the screen. Top at or a little below eye level. A laptop flat on the desk pulls your neck forward all session.
• Make text bigger rather than leaning in. Command and plus zooms in most apps.
• Plan the long sessions. If you know an afternoon is going to be a deep one, take a real break before it starts: lunch away from the desk, a short walk.

When to get it checked

Stiffness that goes away after a stretch is normal. Pain that lingers, tingling or numbness in your hands or fingers, weakness in your grip, or headaches that keep coming back are worth taking to a doctor or a physiotherapist, sooner rather than later. Hand and wrist trouble in particular is worth checking early, and no routine in a blog post replaces someone actually looking at you.