Guide · Breaks
Break reminders for programmers that you won’t snooze forever.
Every break app works on day one. By day five you’re hitting snooze on reflex. The problem usually isn’t the reminder; it’s when it fires and how much it asks of you.
updated
short answer
How do I actually take breaks while programming?
Keep breaks short and specific (two minutes to stretch, twenty seconds to look far away), put them on a cadence you can live with, and never let them fire mid-meeting. Pair the eye break with the 20-20-20 rule and make snooze a real delay that comes back, not a way to make the reminder disappear.
Why break reminders get ignored
- Bad timing. A ping in the middle of a call or a tricky debug session is an interruption, so you dismiss it, and soon you dismiss all of them.
- Too frequent. A reminder every few minutes becomes background noise.
- Too vague. “Take a break” is a decision. “Stand up and roll your shoulders for two minutes” is an action.
- Snooze means never. If snoozing just hides the reminder, every break becomes optional.
The 20-20-20 rule
The American Optometric Association suggests that every 20 minutes you look at something 20 feet away for 20 seconds, and rest your eyes for 15 minutes after two hours of continuous computer use (AOA). The American Academy of Ophthalmology notes that people blink about 15 times a minute normally but only 5 to 7 times a minute at a screen, which is part of why eyes feel dry and tired (AAO).
To be straight about it: Cronch pings on a 45 to 120 minute cadence, so it isn’t a 20-minute eye timer. If you want a reminder every 20 minutes exactly, a dedicated break timer does that better. Cronch makes sure the bigger breaks happen at all, around your meetings and alongside meals and water.
Three breaks worth taking
Stand and stretch, two minutes
Out of the chair. Shoulders, neck, hips. Short enough that you won’t argue with it.
Eye break, 20-20-20
Look at something 20 feet away for 20 seconds. You don’t even have to leave the desk.
Walk it off, five minutes
On your feet, away from the screen. Refill your water on the way back.
How Cronch does it
- You pick the cadence: every 45, 60, 90 or 120 minutes during your work hours. Breaks alternate with water so both happen.
- Each break is one of the three above, with a one-line instruction, not a vague nudge.
- Breaks move to after the meetings you add, stay out of quiet hours, and don’t crowd a meal.
- Snooze pushes a break 15 minutes and it comes back. Skip clears it and doesn’t count against your day.
- History shows breaks taken this week and a streak of days you kept the plan, so you can see whether it’s working.
Breaks are one part of the plan, next to meals and water. You can mark one done from an email, the dashboard, or inside Claude, ChatGPT or Cursor.
Questions
Will Cronch lock my screen?
No. It pings and waits for you. There’s no lockout and nothing to install on your computer.
How often should a programmer take a break?
For eyes, the AOA’s guidance is the 20-20-20 rule and 15 minutes of rest after two hours of continuous use. For the rest of you, a short break every hour or so is a common, sustainable rhythm. Pick a cadence you will keep; a slower one you follow beats a fast one you snooze.
Keep reading
Put breaks on a schedule.
Cronch is in private beta. Join the waitlist and you’ll get one email with your invite when your spot is ready.