--- title: "How to remember to eat while coding · Cronch" description: "Why developers skip lunch in flow, and a practical way to stop: fixed meal times, a no-cook fallback and reminders that wait until your meeting ends." canonical: "https://cronch.io/remember-to-eat" last-updated: "2026-10-07" --- # How to remember to eat while you’re coding. You don’t skip lunch on purpose. You open the editor at 10, look up at 3, and the meal you meant to have never happened. Here’s why that keeps happening and what actually fixes it. updated october 7, 2026 ## How do I remember to eat while coding? Decide meal times before the day starts, put them where you’ll see them, and make eating the easy option: pick the food in advance and keep a no-cook fallback. Then use a reminder that moves out of your meetings instead of firing in the middle of them, so you don’t learn to ignore it. ## Why lunch disappears Forgetting to eat while programming is rarely about willpower. A few things stack up: - **Flow hides hunger.** Deep focus pushes background signals down. Hunger shows up later as a headache or a short temper, not as “time for lunch”. - **Remote days have no cues.** In an office, people stand up for lunch around you. At home, nothing changes at noon unless you make it change. - **“After this test passes” never ends.** There is always one more small thing, and each one feels shorter than a meal. - **Meetings eat the window.** When the only free hour is 12 to 1 and a call lands at 12:30, lunch quietly drops off the day. - **Deciding is work.** If you still have to choose what to eat, it loses to the code you already understand. ## What works 1. **Set meal times before you start** Pick rough times for breakfast, lunch and dinner based on your working hours, not on how hungry you feel at 9am. Lunch around 12:30 and an afternoon snack on long days is a good default. 2. **Put meals where your day lives** That means your calendar or a reminder you already respond to. A meal that only exists in your head loses to a failing build every time. 3. **Decide the food ahead of time** Choose today’s lunch in the morning, or keep a short list of meals you like that fit your diet. When the reminder fires, there should be nothing left to decide. 4. **Keep a no-cook fallback** Yogurt and fruit, a wrap, leftovers. On the days you only have ten minutes, eating something now beats a perfect meal you never get to. 5. **Route around meetings** A reminder that fires mid-call trains you to dismiss it. Move the meal to right after the meeting ends instead of skipping it. 6. **Make done a single action** Logging calories turns a reminder into a chore. Done, snooze or skip is enough to keep the habit honest. ## A schedule you can copy Here is the idea written as a crontab, for a 9:30 to 18:00 workday. Adjust the hours to yours; the point is that meals have times, just like your deploys. ``` # m h dom mon dow job 35 9 * * 1-5 breakfast 30 12 * * 1-5 lunch --after-meetings 30 15 * * 1-5 snack --no-cook 45 17 * * 1-5 wind-down 0 19 * * * dinner --cook=quick ``` ## How Cronch does it Cronch is that schedule, run for you. You answer a few questions once (diet, allergies, how much you want to cook, the food you love), and every workday it: - plans breakfast, lunch and dinner around your work hours, with an afternoon snack on long days; - moves a meal to after a meeting ends when the two collide, and never pings during quiet hours; - suggests a meal that fits your diet, allergies and budget, with a short recipe or a pre-filled Uber Eats, DoorDash or Google Maps search (you check out yourself); - pings you when it’s time, by email or on the Today dashboard, and Done, Snooze 15 or Skip is the whole interaction. When you’re hungry right now, say so: “I’m starving, 10 minutes, no cooking” gets options that fit. You can do that on the dashboard or from [Claude, ChatGPT, Cursor or the terminal](https://cronch.io/mcp). ## Questions ### Is an alarm on my phone enough? It can be. A fixed alarm works well on days without meetings. It breaks down when your calendar moves, because the alarm fires mid-call and you dismiss it. That is the part a calendar-aware reminder fixes. ### Do I have to track calories? No. Remembering to eat is a scheduling problem, not a tracking problem. Cronch never asks you to log food: you mark a meal done, skipped or snoozed. ### Does Cronch order the food? No. It opens a search on the delivery app you already use, and you choose and pay there. Cronch never places orders or stores a card. ## Keep reading - [Water reminders for developers that skip meetings](https://cronch.io/water-reminders): Hydration pings that wait until your call ends. - [Break reminders for programmers that fit your day](https://cronch.io/break-reminders): Short breaks you’ll actually take, on a cadence you pick. - [How to plan meals around back-to-back meetings](https://cronch.io/meals-around-meetings): Where lunch goes when the calendar is full. - [Cronch MCP server for Claude, ChatGPT and Cursor](https://cronch.io/mcp): Your day inside Claude, ChatGPT, Cursor and the terminal.