惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

N
News and Events Feed by Topic
Malwarebytes
Malwarebytes
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
C
Cybersecurity and Infrastructure Security Agency CISA
F
Future of Privacy Forum
C
Cisco Blogs
T
The Exploit Database - CXSecurity.com
A
Arctic Wolf
S
Securelist
K
Kaspersky official blog
S
Schneier on Security
T
ThreatConnect
T
Tenable Blog
Spread Privacy
Spread Privacy
T
True Tiger Recordings
AWS News Blog
AWS News Blog
F
Fox-IT International blog
量子位
T
Threatpost
V
Vulnerabilities – Threatpost
C
CERT Recently Published Vulnerability Notes
Cisco Talos Blog
Cisco Talos Blog
GbyAI
GbyAI
宝玉的分享
宝玉的分享
腾讯CDC
G
Google Developers Blog
aimingoo的专栏
aimingoo的专栏
Cyberwarzone
Cyberwarzone
有赞技术团队
有赞技术团队
S
SegmentFault 最新的问题
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
V
Visual Studio Blog
U
Unit 42
雷峰网
雷峰网
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
Simon Willison's Weblog
Simon Willison's Weblog
O
OpenAI News
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The GitHub Blog
The GitHub Blog
The Register - Security
The Register - Security
MyScale Blog
MyScale Blog
小众软件
小众软件
A
About on SuperTechFans
Last Week in AI
Last Week in AI
Y
Y Combinator Blog
博客园 - 三生石上(FineUI控件)
美团技术团队
Google Online Security Blog
Google Online Security Blog
P
Proofpoint News Feed
MongoDB | Blog
MongoDB | Blog

DEV Community

Managing multiple docker hub accounts using docker-use System Design Interview: Decentralized Web Crawler Metric Cardinality: High or Low? 4 Steps to Making the Right Choice 로컬 LLM 셋업 가이드 (v23) GEO vs SEO in 2026 — What Google's May Guidance Changed Cursor Review 2026 — Honest 'Not For Me' Take From a VSCode User Hello from rikuq — a practitioner blog for solo AI SaaS founders Why DevOps Engineers Need Practical Tutorials, Not Just Theory AI Agents in CI/CD: Give Them Context, Not Production Authority Now I See Why Translators Are Panicking Over AI—Should Coders Panic Too? Diffusion Language Models: How NVIDIA's Nemotron-Labs DLM Is Killing Token-by-Token Generation Chatbots GPT pour le support client : ce que les équipes françaises ont réellement besoin de savoir I Hit the 1,232-Byte Wall So You Don't Have To Google Just Rebuilt the Search Box (Again) — But This Time It's Different Aether: A local Android assistant built with Gemma 4 BoxAgnts Introduction (1) — Out of the Box mkdev: trusted HTTPS for localhost, mapped by name Just one question, one answer. Why Java Still Rules the Programming World in 2026 Four Architectures for Letting Claude Edit Elementor (and Why We Shipped Clone-and-Mutate) yard-yaml 0.1.1: safer UTF-8 handling for YAML documentation I Built a Mac App That Keeps Your Clipboard in Sync Across All Your Android Devices Stop Using UUIDs: Why B2B SaaS Needs ULIDs in Laravel 🐘 I'm a non-technical founder who built a Slack approval tool. Here's what actually broke first. Open-Sourcing Our Game AI Stack — SDKs, Templates, and CLI Tools for NPC Dialogue I Built an AI System That Makes 1,000 Decisions a Day. Here's Where I Drew the Line. Lets Encrypt DNS Challenge with Traefik and AWS Route 53 Building an agent-ready website: how to make your site readable for ChatGPT, Perplexity and autonomous agents A productivity tool with GitHub as your cloud database How We Built Dynamic NPC Dialogue with LLMs — Lessons from Early Access cmux: The Native macOS Terminal Built for Running AI Coding Agents in Parallel Deep Atlantic Storage: Rewriting in Rust How I Built a Bulk Image Optimizer with $0 Server Costs Using Vanilla JS and Canvas API Humans and Machines read differently, I think I have a fix? Claude Code Deleted 92 Images Without Asking. This Happens More Than You Think. Method Calling Stack in Java I Built Schedule Sensei & Pushed It to GitHub – Here's What's Inside (And I Need Your Help 👀) OIC: From a Working Toast Watcher to a General "Watch It for Me" Agent Memory is two-thirds of what an AI chip costs to build The XState persistence problem is five years old. Here is what we built to finally solve it. i added MCP support to my SaaS in an afternoon. here's the whole thing. Framework: Link Building ☁️ Importing existing S3 buckets into Terraform state made easy with terraform import existing s3 bucket I Built a Token System on Solana (Without Any Backend Code) 터미널 AI 에이전트 구축 (v21) I Built an AI 3D Model Generator — Here's How I Handle Meshes in the Browser 🛡️ PromptGuard: I Built a Local AI Privacy Firewall That Sanitizes Your Prompts Before They Leave Your Machine PostgreSQL WAL Bloat: Why Automatic Management Is Often Insufficient? Seven PRs Before Lunch: Parallel Claude Code Tabs Plus Audit-Before-Bump Deployment using all three Kubernetes probes Qwen 3.6 Has Four Tiers. Here's How to Route Without Burning Cash. RAG 시스템 실전 구축 (v21) How I handle my errors in PHP The Blind Spot in Treasure Hunt Engine Configuration: Long-Term Server Health Run NVIDIA NIM on Your Own GPU — Same API, Different Endpoint Webflow SEO Implementation 로컬 LLM 셋업 가이드 (v21) How Logs Travel From Your EKS Pod to Datadog 𝗦𝘁𝗼𝗽 𝗖𝗿𝗮𝗺𝗺𝗶𝗻𝗴 𝗙𝗼𝗿 𝗘𝘅𝗮𝗺𝘀, 𝗦𝘁𝗮𝗿𝘁 𝗕𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗥𝗲𝗮𝗹 𝗦𝗸𝗶𝗹𝗹𝘀 How to Use EXPLAIN ANALYZE in PostgreSQL: A Visual Guide gRPC Performance: tonic (Rust) vs grpc-go Benchmarked at Scale Hack The Box (HTB): Cap Machine (Full Walkthrough) Visual Search Optimization studygemma: AI study buddy for CS students Architectural Tradeoffs in Webhook Idempotency and SaaS API Versioning One Open Source Project a Day (No. 75): Understand Anything - The AI Engine That Turns Any Codebase Into an Explorable Knowledge Graph From mock-only-works to real-world-works: 48 hours of reCAPTCHA debugging I built a free music tool AI Talking Avatar Pipelines Broke Our Ad CTR by 3.7% 800G to 400G Breakout: How to Scale 400G Networks with 800G Ports 터미널 AI 에이전트 구축 (v20) Topical Authority Architecture Inside Hermes Agent's Session Memory: What X-Hermes-Session-Id Actually Does How Logs Travel From Your EKS Pod to Datadog The Hidden Journey Inside / Kubernetes Is it safe to connect my bank account to AI? No Room — The World of Aying (8/12) Fossils — The World of Aying (10/12) Familiar Stranger — The World of Aying (9/12) Being Seen — The World of Aying (7/12) [I Ran an AI Agent for 30 Days Straight — Here's the Boring Engineering That Made It Work] Gemma 4: The 128K Multimodal Powerhouse in Your Terminal How to Consolidate Your QA Toolstack: A Practical Buyer's Guide The Thank-You Email Almost Nobody Sends (And Why That's Your Edge) Schema Types 2026 Idempotency Keys: The API Safety Net You're Probably Not Using How to let Claude see my Plaid bank data Kiro Did It: Build a Simple Portfolio Website with Kiro IDE | From Prompt to HTML Prototype Islands of Commerce: What Marketplace Founders Can Learn from 60 Years of Island Biogeography React Pointer Hooks: Hover, Long-Press, Double-Click, Scratch, and Click-Outside Without the Bugs Engineering decisions for my video call tool VBScript Still Lives: How a Custom Go VM Brought Classic ASP to Linux and Mac What Happens When You Teach Old Scripting Languages New Runtime Tricks? I Tested 6 AI Coding Assistants for a Month. Here's What Actually Works. Extendscript Still Has Life Afriex Webhook Integration Guide: Signature Verification, Event Handling, and Production Best Practices The Blind Alleys of Veltrix Configuration How an ESP32 Turned a LEGO WALL-E Into a Real Working Robot The Flawed Promise of Real-Time Event Handling SSH Login Taking Forever? Check Your DNS Settings Found 897 Fake Followers on DEV.to. Here's How I Proved It.
Why I Track HRV Every Morning (And How It Actually Changes My Day)
Richard Lemo · 2026-05-25 · via DEV Community

HRV is only useful if it changes your day

I have tracked HRV every morning for a few years now. Not because I like graphs. Because it is the only number that consistently talks back when I am lying to myself.

I build web stuff, coach baseball, and play the biohacker hobby game. That combination makes it very easy to run on willpower and caffeine until something breaks. HRV is my early warning system.

But here is the key point. I do not care about the exact number. I care about what I do differently because of it. No behavior change, no point.

The setup: cheap, boring, and consistent

I do not treat HRV like a gadget fashion show. I want boring and repeatable.

My morning routine:

  • Wake up, bathroom, water.
  • Sit on the same chair.
  • Same 60–90 second HRV reading with a chest strap and phone app.
  • Eyes open, normal breathing, no breathwork tricks.

I care about three things only:

  • My rolling baseline. Roughly the 7–30 day trend.
  • Today vs that baseline. How far up or down.
  • Direction. Is it drifting up, flat, or sagging over a few days.

The app gives me a recovery score. That score is just math on top of the HRV number, but it is easier to work with a simple traffic light in my head.

The traffic light: green, yellow, red

I run my life on a very dumb, very useful mental model.

  • Green: Nervous system looks ready. HRV at or above baseline. Resting heart rate normal.
  • Yellow: Slightly suppressed HRV or resting heart rate a bit elevated, or both. Body is stressed but not falling apart.
  • Red: Noticeably down HRV, sometimes paired with a big bump in resting heart rate, plus I feel like cardboard.

That is it. No decimal worship. I do not care if my RMSSD is 68 or 72. I care if the light is green, yellow, or red and where that sits relative to my baseline.

The important part is what I decided in advance for each color. If you make rules on the spot you will negotiate yourself into dumb decisions.

Green days: permission to go heavy

On a green day, I treat HRV clearance as permission. Not as pressure.

I have three decision buckets that change when I see green: training, work, and recovery inputs.

Green training rules

Green usually means:

  • Hard session goes ahead: heavy lifts, sprint work, or a tough baseball practice.
  • Volume is allowed to climb: I may add a set or two, or stretch the conditioning a bit.
  • Experiment window is open: if I want to test a new drill, a different sprint pattern, or a new strength block, I try it on a green day.

Example from last month: I had a planned heavy lower body day with some sprint repeats. HRV was clearly green, slightly above baseline after two nights of solid sleep. Instead of just running the default, I pushed the sprint count by 20 percent and added one heavier top set on squats.

The session felt good, no grindy reps, and HRV stayed stable the next morning. That told me my body could handle that new load. So I locked that progression in as the new normal for the block.

Green work rules

Green day equals high-quality cognitive work window.

  • I schedule my hardest coding or design work as early as possible.
  • I avoid early calls. I move meetings to the afternoon if I can.
  • If there is a tricky refactor or a gnarly WebGL experiment, this is the day.

HRV does not directly tell me about focus, but there is a pattern. When recovery is solid, my willingness to sit with hard problems is much higher.

Green recovery rules

When I see green I do not celebrate with junk behavior. I do the opposite.

  • Keep caffeine normal, do not double it just because I feel good.
  • Stick to my usual bedtime rather than “rewarding” myself with a late night.
  • Give myself a small recovery boost, like a longer walk in the sun.

Green is where you build new capacity. You can only do that if you do not instantly spend all the extra energy on random nonsense.

Yellow days: ego control territory

Most days are not green or red. They are slightly off. That is where the traffic light actually earns its keep.

Yellow is where my ego wants to ignore the data. This is also where I have made the most dumb training mistakes in the past.

Yellow training rules

On a yellow day I do not cancel training. I change the framing.

  • Intensity stays, volume drops: I still lift heavy or move fast, but I cut sets or total reps.
  • Or volume stays, intensity drops: I keep the number of sets, but I stay well away from failure and keep heart rate lower.
  • No new experiments: I do not test 1RMs, new sprint distances, or brutal circuits.

Concrete example. My HRV is slightly below baseline after a late-night game or a long coding session that turned into a 1 AM situation. I had planned 5 x 5 heavy bench and a bunch of accessory work.

On a yellow day, I might keep the 5 x 5 but drop the load by 5–10 percent, skip one accessory exercise, and cut conditioning in half. I still show up. The workout still happens. I do not dig a deeper hole.

Yellow work rules

Yellow days are for progress without heroics.

  • Ship small pieces. Fix bugs, clean up code, handle admin.
  • Push big decisions to a green day if possible.
  • Be very suspicious of “one more hour” thinking in the evening.

If I force a late-night coding binge on a yellow day, HRV usually hits red the next morning. I have seen that pattern enough times to consider it basically deterministic for me.

Yellow recovery rules

On yellow I start turning dials.

  • Earlier cutoff for screens and work.
  • A bit more carbs in the evening to support sleep.
  • Move non-urgent life tasks to another day.

The idea is simple. Yellow means “you are drifting.” I want to see if I can pull myself back toward green tomorrow without skipping life.

Red days: forced humility

Red is where HRV saves me from myself. This is the only color where I am willing to scrap the plan completely.

Red usually comes from one of a few predictable causes for me:

  • Travel and broken sleep.
  • Back-to-back high intensity days because I ignored a yellow signal.
  • Getting sick, or fighting something off.
  • Two days of very late games or events.

Red training rules

On a red day I have a simple default.

  • No high-intensity training.
  • LISS cardio only: easy walk, light bike, mobility.
  • If I feel awful, full rest.

If I already stacked a few red or deep yellow days in a row, I usually remove any training pressure completely. I let the system reset. Every time I ignored that, HRV punished me with a longer slump and worse sleep.

One specific pattern: if HRV tanks and resting heart rate is up, and perceived effort spiked on what should have been an easy session the day before, I do not negotiate. I shut it down for that day. That combo almost always means something is off globally, not just “I am a bit tired.”

Red work rules

On red days I lower the ambition floor.

  • Cancel non-essential meetings if I can.
  • Move deep work to another day. Only do it if I somehow feel unusually sharp despite the score.
  • Knock out simple, mechanical tasks and stop pretending I will architect a whole new feature set in that state.

I had to get over the guilt of this. But every time I pretend I am fine on a red day, I pay for it later with sloppy code and more time spent fixing mistakes.

Red recovery rules

Red is where I go heavier on interventions.

  • Hard stop on screens at least an hour before bed.
  • Light dinner, no late heavy meals.
  • Walks instead of workouts, sunlight early in the day.
  • If possible, a short nap, but capped so I do not wreck the night.

I also use red days as an audit. Why am I here? Was it a one-off travel day or have I been stacking small stupid decisions for a week?

Where HRV actually changed my behavior

HRV itself did not change much in my life on day one. The traffic light and pre-committed rules did.

Here are a few specific shifts that stuck.

I stopped pretending sleep does not matter

Before HRV, I treated sleep like a flexible variable. If I wanted to code late or watch a game, I did it. I would “catch up” later.

HRV showed me something simple. Two short nights do more damage than one really short night. The second late night pushes the nervous system into a state where the next day is always worse than it feels in the moment.

Green-to-red swings after stacked short nights convinced me to protect at least five nights a week. I still have late nights, just fewer in a row.

I stopped proving toughness to no one

Most of the athletes I coach, and most developers I know, have the same problem. We mistake stubbornness for discipline.

HRV gave me a clean excuse to stop that. If the score is red and the trend has been sliding for three days, I do not get bonus points for “pushing through.” I get slower progress and more nagging injuries.

It took a while, but now if the traffic light is red and I still feel the itch to max out something, I treat that as a bug in my behavior, not a sign of commitment.

I started planning weeks, not days

Tracking HRV showed me that what I do on Monday is still echoing around on Thursday.

So now I design weeks around likely traffic lights:

  • Monday and Thursday are likely green: main heavy training and hardest coding.
  • Tuesday and Friday are more flexible: if I see yellow, those become lighter work or technique days.
  • Weekend is the buffer: travel, games, or family stuff that may push HRV around.

This is not perfect. Life rarely respects my plans. But thinking in terms of green / yellow / red probability has made my training blocks far more stable.

HRV is not a boss, it is a negotiating partner

I do not outsource decisions to HRV. I use it as one more voice in the room.

Sometimes I override it. For example, if it is a once-a-year event or competition, I am going to show up and do the thing, even on a red day. I just go in with my eyes open. I expect a recovery tax afterwards and I plan around it.

Most days though, the traffic light is enough to keep my ego in check and my training productive.

If you want to steal this system

If you want to copy anything here, copy the decision loop, not the tech.

  • Pick one HRV method. Keep it boring and consistent.
  • Track for a few weeks without changing anything just to see your baseline.
  • Define your own clear green, yellow, red thresholds in that app or in a notebook.
  • Write down rules for each color before you see the next score.
  • Commit to following those rules for a month and see what happens to performance and mood.

I think most people obsess over gadgets and miss the point. HRV is not about who has the highest number. It is about having a simple, brutally honest mirror that you agree to listen to every morning.

That is why I still track it. Not because I care about today’s exact milliseconds. Because it changes what I do at 9 AM.