DEV Community: NutriCounter

Track Your Water Like You Track Your Habits — The Case for a Daily Water Log

NutriCounter — Fri, 09 Oct 2026 06:06:20 +0000

Developers instrument everything. Uptime dashboards, error budgets, CI pipelines with graphs for days. Then we run our actual bodies on vibes — 'I probably drank enough water today' — and wonder why the 3 PM slump hits like clockwork. Hydration is one of the few health inputs that's fully measurable, fully controllable, and fully free. It deserves the same treatment we give our systems: a defined target and a log.

Vague goals fail. 'Drink more water' has no target, no feedback loop, and no definition of done — the same reason 'improve performance' is a bad ticket. What works instead is a number and a tracker. Your number depends on your weight and activity. A 60 kg desk worker and a 90 kg runner don't share a hydration target, and pretending they do is how people end up both under-hydrated and annoyed at the advice. Get your personal number first, then the tracking becomes trivial: you're just closing the gap between intake and target, the same way you'd close any other metric gap.

The whole system is: (1) know your daily target, (2) log as you go, (3) glance at the running total. That's it. No special bottle with time markers, no app with seventeen permissions, no subscription. A daily water tracker that takes your weight and activity and spits out your target covers step one in about a minute; a simple log — even a notes file — covers steps two and three. The magic is the feedback loop, not the tool. Once you can see 'I'm at 1.1 of 2.6 liters and it's 2 PM,' the correction is automatic. You don't need motivation; you need visibility. Every observability engineer already knows this.

What changes when you actually track: afternoon headaches drop (the most common cause of the 3 PM headache is mild dehydration, usually misdiagnosed as 'I need coffee'); snacking decreases (thirst and hunger share signaling pathways); workout quality improves (even 2% dehydration measurably degrades endurance); sleep gets easier (chronic evening dehydration correlates with worse sleep quality). None of this requires perfection — hitting your target most days beats hitting it perfectly for one week and quitting.

Edge cases worth knowing: coffee counts (the water in the cup offsets caffeine's mild diuretic effect for habitual drinkers); big workout days need roughly 0.5–1 extra liter per hour of hard exercise; spread intake across the day instead of force-gulping at 9 PM; and food counts too — roughly 20% of most people's water comes from food.

You wouldn't run a service without metrics. Stop running your body without them. One target, one log, two minutes a day — and the data will tell you what 'drink more water' never could.

How I Built a Free Calorie Calculator Anyone Can Use

NutriCounter — Thu, 08 Oct 2026 08:33:41 +0000

A few years ago I started tracking what I ate because my doctor told me I needed to lose weight. Nothing dramatic — just eat a little less.

It wasn't. Every app I tried wanted a sign-up or a subscription before showing me a single number. All I wanted to know was: how many calories should I actually eat in a day? That question turned into a small side project, and the project turned into NutriCounter, a free set of health tools I keep building in my spare time.

Start with the math, not the code

Before I wrote anything, I had to understand what a calorie target even is. It comes down to two things: how much energy your body burns at rest, and how much you burn moving around.

The first part is called your BMR (basal metabolic rate), and the common way to estimate it is the Mifflin-St Jeor equation. It takes your weight, height, age, and sex and gives you a number. Then you multiply that by an activity factor — sedentary, lightly active, and so on — and you get your TDEE, total daily energy expenditure. Want to lose weight? Eat a bit less than that number.

That is all a calorie calculator does. The formulas are public, well-studied, and older than the web itself. The hard part was never the math — it was making the result easy to understand for someone who has never heard the words "Mifflin-St Jeor."

Keep the interface boring

I see a lot of health tools that look like video games. For my own tool I went the opposite direction. One form, four or five fields, one big readable result.

Weight, height, age, sex, activity level — that is all I ask for. The result page shows your BMR, your TDEE, and suggested calorie targets for losing, maintaining, or gaining weight. No account, no email, no paywall. If a tool is supposed to help people, the first screen should not be a pricing page.

The whole thing is plain HTML, CSS, and JavaScript. No framework. That was a deliberate choice: it loads fast on cheap phones and works fine on slow connections, which matters.

Units and languages matter more than features

One early lesson: half the world does not use pounds and inches. If your calculator only accepts imperial units, you have quietly told most of the planet to go away. Adding metric support took a couple of hours.

Same story with language. I translated the site into six languages — not with perfect polish, but good enough to be useful. Most health questions people type into search engines are not in English.

What I would do differently

If I started over, I would talk to real users earlier. I spent weeks on the food diary and exercise tracker before I had any idea whether anyone wanted them. Next time I will ship the smallest useful thing first and let feedback decide what gets built next.

I would also worry less about the design. My first version was ugly and people used it anyway.

Why free

This part is simple. I built the tool I wished existed when my doctor gave me that advice. Putting a paywall on it would defeat the purpose. The site runs on cheap hosting and the calculators are just math — there is nothing to charge for. If you want to try it, it is at nutricounter.net, along with the rest of the toolkit.

Sometimes the most useful thing you can build is the simplest one.

How Much Water Should You Actually Drink? Let's Do the Math

NutriCounter — Thu, 08 Oct 2026 06:22:46 +0000

How Much Water Should You Actually Drink? Let's Do the Math

"Drink eight glasses a day" is the programming equivalent of "just restart it" — advice so generic it ignores every variable that matters. Your actual water needs depend on your body weight, activity level, climate, and diet. Let's replace the folk rule with something closer to an actual formula.

Why the 8-glasses rule fails

Eight 8-ounce glasses is about 1.9 liters. For a 55 kg person sitting in air conditioning all day, that might be plenty. For a 95 kg person training in summer heat, it's nowhere near enough. The rule also ignores that roughly 20% of daily water typically comes from food — fruits, vegetables, cooked grains, even meat contribute meaningful fluid.

A better baseline: weight-based intake

Sports-medicine guidelines commonly suggest 30-40 ml of water per kilogram of body weight per day as a baseline for a moderately active adult in a temperate climate. The math is simple:

60 kg: 1.8-2.4 L/day
75 kg: 2.25-3.0 L/day
90 kg: 2.7-3.6 L/day

That's your starting point, before adjustments.

Adjust for the real variables

Exercise: add roughly 500-750 ml per hour of moderate activity, more for intense sessions or heat. Weigh yourself before and after a long workout sometime — each kilogram lost is about a liter of fluid to replace.

Climate: hot or humid environments increase sweat loss significantly. Air-conditioned offices do the opposite extreme — dry air increases insensible water loss through skin and breathing, which most people underestimate.

Diet: high-protein diets and high-fiber diets both increase water needs. So does alcohol (it's a diuretic) and excess caffeine, though moderate coffee still counts toward fluid intake.

Don't overthink it — but don't guess either

You don't need to carry a graduated cylinder. The practical approach: compute your baseline once with a water intake calculator, adjust for your activity and climate, then build the habit — a glass with each meal, one during deep-work sessions, one after exercise. Your urine color is the runtime check: pale straw is the target, dark yellow means drink more, completely clear all day means you can ease off.

Hydration won't fix bad sleep or a bad diet, but chronic mild dehydration genuinely degrades concentration, reaction time, and mood — the exact things knowledge work depends on. It's one of the cheapest performance upgrades available: compute your number, then just drink it.

Free health calculators at NutriCounter.

Your Body Has a Baseline Power Draw. Here's How to Calculate It.

NutriCounter — Wed, 07 Oct 2026 06:01:53 +0000

Your Body Has a Baseline Power Draw. Here's How to Calculate It.

Every machine has an idle power draw — the watts it burns just sitting there, powered on, doing nothing. Your body is no different. Even if you spent the entire day lying perfectly still, you'd burn somewhere between 1,400 and 2,000 calories just keeping the lights on: brain running, heart pumping, lungs moving, cells repairing. That number has a name. It's called your basal metabolic rate, or BMR.

Most developers I know can tell you their laptop's idle wattage but have never once computed their own. That's backwards — it's the single most useful number in all of nutrition, and you can calculate it in about sixty seconds.

BMR: the idle loop

BMR is the energy cost of being alive. It's driven by a handful of inputs — age, sex, height, weight — and it declines slowly as you age and scales with lean mass. Two people of the same weight can have meaningfully different BMRs if one of them carries more muscle, because muscle tissue is metabolically expensive to maintain even at rest. Think of it as the difference between a machine with more cores: higher idle draw, always.

The classic way to estimate it is the Mifflin-St Jeor equation, which is what most calculators under the hood are running: for men, (10 × weight in kg) + (6.25 × height in cm) − (5 × age) + 5; for women, the same with − 161 instead of + 5.

You can do this on paper, or skip the arithmetic entirely with a basal metabolic rate calculator that runs the formula for you.

TDEE: BMR plus everything else

BMR is only the baseline. Your total daily energy expenditure — TDEE — adds the cost of everything you actually do: walking to the kitchen, typing, fidgeting, that evening run. TDEE is estimated by multiplying BMR by an activity factor, from 1.2 (sedentary, desk all day) up to 1.9 (heavy physical work or serious training).

This is where most people go wrong. They pick a calorie target from a generic chart — "2,000 calories a day" — without ever computing their own numbers. A 6'2" developer who lifts weights and a 5'4" developer who doesn't exercise have TDEEs that can differ by 800+ calories. The same 2,000-calorie diet is a deficit for one and a surplus for the other. The chart doesn't know you exist. The math does.

Turning the number into a target

Once you have your TDEE, the rest is simple arithmetic: want to lose weight? Eat roughly 300–500 calories below TDEE. Maintain? Eat at TDEE. Gain muscle? Eat roughly 200–300 above, with enough protein and resistance training.

Recompute every few weeks, because BMR drifts as your weight changes — lose 10 kg and your idle draw drops, which is exactly why plateaus happen. People call it a broken metabolism; it's just the equation updating its inputs.

The developer takeaway

You wouldn't ship code without knowing the baseline metrics, and you shouldn't run a diet without knowing yours. BMR and TDEE are the two numbers behind every calorie target that actually works. Compute them once, set your target from the math instead of a chart, and re-run the calculation when the inputs change — just like you'd re-benchmark after changing the hardware.

Written by NutriCounter — nutricounter.net

Ship Your Health Like You Ship Code: The 2-Minute Daily Tracker

NutriCounter — Mon, 05 Oct 2026 06:02:41 +0000

Ship Your Health Like You Ship Code: The 2-Minute Daily Tracker

You'd never ship a feature without metrics. Dashboards, alerts, error budgets — you instrument everything, because what gets measured gets fixed. Then you close the laptop and run your actual body with zero observability. No logs. No trends. Just vibes and a vague feeling that "I should probably eat better."

That asymmetry is fixable in about two minutes a day.

Your Body Is a System. Instrument It.

Think of a daily tracker as the observability layer for your health. Each evening you log the basics — roughly what you ate, how much water you drank, whether you moved — and the tracker turns it into trends: calories in, macros, hydration streaks, week-over-week direction. One day of data is noise. Thirty days is a dashboard. And dashboards change behavior without any willpower involved, because nobody wants to stare at a red week.

This is the same feedback loop that makes CI work. You don't get better at code by resolving to "write better code" — you get better because the pipeline fails loudly and the metrics are visible. A calorie tracker is that pipeline for your habits: log the day, see the numbers, adjust tomorrow. The loop is the product.

The 2-Minute Protocol

The reason most tracking attempts die by day four is friction. Complicated apps, barcode scanning every snack, weighing portions — that's a system designed for abandonment. The sustainable version is deliberately rough:

Log once, in the evening. Not after every meal — once, before bed, from memory. Approximation beats precision you won't sustain.
Track three things only. Food (rough calories), water (glasses), movement (yes/no + minutes). Anything more is scope creep.
Review weekly, not daily. One bad day is an outlier, not a failure. The Sunday 5-minute review is where the signal lives: did the week trend the right way?

That's the whole protocol. Developers are good at this — it's just a cron job with a weekly retro.

What the Data Actually Teaches You

The first insight hits around week two: your "normal" eating is probably 300–500 calories more than your mental model says. Not because you're lying to yourself, but because humans are terrible at estimating — the same way we estimate story points. The tracker is the calibration tool.

The second insight is about patterns, not meals. You'll see that the bad days cluster — late nights, skipped lunches, stressful deploys. Fix the pattern (keep a real lunch, hard stop at midnight) and the meals fix themselves. You're debugging the system, not shaming the user.

Start Tonight

You don't need a wearable, a meal plan, or a new identity. You need a 2-minute log and a weekly glance at the trend line. The developers who stick with it aren't the disciplined ones — they're the ones who made the feedback loop too easy to skip noticing.

Instrument the system. Watch the dashboard. Ship the healthier version.

Free health calculators at NutriCounter.

Sleep Math for Developers: 90-Minute Cycles Beat 8 Hours

NutriCounter — Sun, 04 Oct 2026 06:03:45 +0000

Sleep Math for Developers: 90-Minute Cycles Beat 8 Hours

You optimize everything else — CI pipelines, query plans, render loops. But your sleep? Most of us still chase a round number like "8 hours" and wake up groggy anyway. The reason is that sleep isn't a quantity problem. It's a timing problem.

Your Brain Sleeps in 90-Minute Blocks

A full sleep cycle — light sleep, deep sleep, REM — takes about 90 minutes. Waking up in the middle of a cycle (deep sleep, say) triggers sleep inertia: that heavy, underwater feeling that no amount of coffee fixes in the first hour. Waking up at the end of a cycle, during light sleep, feels dramatically easier — even with slightly less total sleep.

This is why you can sleep 7 hours and feel great one day, then sleep 8 and feel wrecked the next. It's not the hours. It's where the alarm landed.

Do the Math Backwards

Pick your wake-up time first, then count backwards in 90-minute chunks and add ~15 minutes for falling asleep. Want to wake at 6:30 AM? Your ideal bedtimes are 11:15 PM (5 cycles), 9:45 PM (6 cycles), or even 12:45 AM (4 cycles). Four complete cycles at the right boundaries beats five interrupted ones.

A bedtime calculator does this arithmetic for you — plug in when you need to wake up, and it returns the optimal bedtimes ranked by cycle count. No mental math at midnight when you're already half-asleep.

The Developer's Sleep Protocol

Fixed wake time, even on weekends. Your circadian rhythm is a clock, not a suggestion. A 30-minute drift is fine; a 3-hour weekend swing is a weekly timezone change.
Kill the blue light 60 minutes before bed. Your editor's dark theme doesn't save you — screens suppress melatonin regardless of theme.
Keep the room cold. Core body temperature must drop to initiate deep sleep. 18–19°C is the sweet spot.
Caffeine has a half-life of 5–6 hours. That 4 PM coffee is still 50% in your system at 10 PM. Cut caffeine after noon if you struggle to fall asleep.

Track It Like You'd Track a Bug

You wouldn't debug a performance issue without metrics. Sleep deserves the same treatment: note bedtime, wake time, and a 1–5 morning rating for two weeks. Patterns emerge fast — you'll spot the late-night snack that costs you an hour of deep sleep, or the gym session that buys you one.

Free health calculators at NutriCounter.

How Much Water Should You Actually Drink? Let's Do the Math

NutriCounter — Sat, 03 Oct 2026 06:03:41 +0000

How Much Water Should You Actually Drink? Let's Do the Math

Why the 8-glasses rule fails

A better baseline: weight-based intake

Sports-medicine guidelines commonly suggest 30–40 ml of water per kilogram of body weight per day as a baseline for a moderately active adult in a temperate climate. The math is simple:

60 kg → 1.8–2.4 L/day
75 kg → 2.25–3.0 L/day
90 kg → 2.7–3.6 L/day

That's your starting point, before adjustments.

Adjust for the real variables

Exercise: add roughly 500–750 ml per hour of moderate activity, more for intense sessions or heat. Weigh yourself before and after a long workout sometime — each kilogram lost is about a liter of fluid to replace.

Climate: hot or humid environments increase sweat loss significantly. Air-conditioned offices do the opposite extreme — dry air increases insensible water loss through skin and breathing, which most people underestimate.

Diet: high-protein diets and high-fiber diets both increase water needs. So does alcohol (it's a diuretic) and excess caffeine, though moderate coffee still counts toward fluid intake.

Illness: fever, vomiting, or diarrhea can spike fluid needs dramatically — this is the one case where "drink as much as possible" is genuinely the right advice.

Don't overthink it — but don't guess either

Free health calculators at NutriCounter.