A movement app for developers.
Developers sit longer than almost any other knowledge worker because flow state suppresses normal body-feedback signals and because the culture rewards uninterrupted deep work. A 60-second hourly nudge is short enough not to crash flow, long enough to undo most of what four hours of debugging does to a spine. Lives in the menu bar. Free. Made by a nonprofit. Doesn't ask for a github login.
If you ship code for a living, this is going to feel personal. The kind of work you do encourages exactly the postures and durations of sitting that the body objects to most, and the cultural defaults around it ("uninterrupted blocks of deep work," "real engineers code for six hours straight," "I'll just finish this bug") make it harder to interrupt than almost any other kind of desk job.
This isn't a piece about how developers should hustle less or work fewer hours. It's a piece about what a body does when you hold it perfectly still for the length of a film, several times a week, for years. It does specific things. None of them are good.
Why developers specifically
The combination is unusual. Most desk jobs involve enough meetings, enough cross-team coordination, enough context switching that a person stands up and moves a few times a day whether they meant to or not. Developer work pattern-matches differently: long, voluntary stretches of unbroken concentration, often in a single application, often in a single position, often without consciously noticing the passage of time.
The mechanism that makes this possible is flow state, and flow state is wonderful for solving problems and terrible for noticing your body. The same neurochemistry that makes the hour feel like ten minutes also suppresses the small "stand up" signals the body normally sends. By the time you do notice, your hips are tight, your neck is cooked, and you've been hunched for so long that getting back to vertical takes conscious effort.
None of this is rare. The line of dev twitter that says "I'm thirty-four and my back is sixty" is essentially every senior engineer we know.
The patterns that show up over a year of full-time coding
1. The lumbar ridge.
A stiff, painful band across the lower back that shows up by the end of any long debugging session and takes overnight to fully resolve. Caused by sustained spinal flexion. Worse if you sit with your laptop on the couch.
2. The cervical jut.
The forward-head posture that creeps in over a screen, especially with multi-monitor setups where one screen is even slightly low. Shows up as a neck-and-shoulder ache that radiates into headaches by year two.
3. Forearm tension.
Not RSI, but the foothills of it. A low-grade tightness in the forearm muscles, sometimes with a vague ache near the elbow, that comes from many small repeated movements held against gravity for hours.
4. The hip flexor anchor.
The hip flexors lock into a shortened position so reliably that standing up from a long sitting block makes you walk like you're sixty for the first few steps.
5. Eye fatigue at week three of a sprint.
Eye muscles do all the work of refocusing at one distance for hours. After a sustained stretch, evenings feel blurrier than they used to and it takes longer to fall asleep. See the 20-20-20 rule for the mitigation.
"won't this break my flow?"
This is the only objection that matters, and it's worth taking seriously. A movement reminder that breaks flow is worse than no reminder at all. Most people who try a break app and stop after a week stop because it pulled them out of focused work too aggressively.
The thing that prevents this is the duration. A sixty-second standing reminder doesn't ask you to start a meditation, watch a video, or follow a routine. You stand up. You walk to the kitchen. You sit back down. The mental model of what you were doing survives intact because the interruption was short enough not to overwrite it.
Some research even suggests this kind of brief interruption helps. The "incubation" effect, where stepping away briefly returns you to a problem with sharper thinking, is well-documented in problem-solving studies. The hourly stand is a tiny incubation cycle. The bug you couldn't see at minute 58 is sometimes obvious at minute 62.
What a developer-friendly movement app actually looks like
Here's the criteria list, written from the dev's perspective.
- Lives in the menu bar. Doesn't take up window space, doesn't break tiling, doesn't interrupt your IDE.
- Fires reliably with Focus mode on. The whole point is that you're heads-down. If the app respects Focus too much, it won't reach you when you most need it.
- Respects "i'm in the middle of something." A snooze button that buys you five minutes, no streaks-as-punishment if you take it.
- No account, no telemetry, no GitHub integration. The app doesn't need to know what you're working on. The app needs to know how often to nudge you.
- Open about its business model. Free core, optional premium, no surprise paywalls a month in.
- Cross-platform if you context-switch. Mac at work, Linux at home, sometimes iPad on the couch. The reminder should travel with you.
- Doesn't try to be a fitness app. No calorie tracking, no heart rate, no "Today's Workout." The job is the reminder. Anything else is feature creep.
The list above is the brief we wrote for ourselves when we built Supermoo, but it would apply to any tool you're evaluating. Run any candidate through it. Use whatever survives.
Install one. Set it to nudge once an hour. Use it for two weeks without judging it. If your back feels different by Friday of week two, keep it. If it doesn't, uninstall it and try a different one. The category is small enough that you can pick a winner in a month.
Either way, the chair was never going to fix itself. You're a programmer. You know what passive systems do over time.
moo handles the hourly part.
Free, no account, Mac menu bar (also iPhone, Android, Apple Watch, Chrome).
Made by a 501(c)(3) nonprofit. Doesn't ask for your email. Doesn't track what you ship.
