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

推荐订阅源

Microsoft Security Blog
Microsoft Security Blog
WordPress大学
WordPress大学
S
SegmentFault 最新的问题
爱范儿
爱范儿
B
Blog RSS Feed
Last Week in AI
Last Week in AI
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Blog — PlanetScale
Blog — PlanetScale
Vercel News
Vercel News
Jina AI
Jina AI
aimingoo的专栏
aimingoo的专栏
I
Intezer
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Attack and Defense Labs
Attack and Defense Labs
The GitHub Blog
The GitHub Blog
小众软件
小众软件
AI
AI
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
N
News and Events Feed by Topic
腾讯CDC
D
Docker
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
罗磊的独立博客
人人都是产品经理
人人都是产品经理
W
WeLiveSecurity
N
News and Events Feed by Topic
Security Archives - TechRepublic
Security Archives - TechRepublic
C
Check Point Blog
Webroot Blog
Webroot Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
H
Help Net Security
Recorded Future
Recorded Future
H
Hacker News: Front Page
T
Troy Hunt's Blog
V
V2EX
Forbes - Security
Forbes - Security
Stack Overflow Blog
Stack Overflow Blog
The Register - Security
The Register - Security
P
Palo Alto Networks Blog
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
博客园 - 叶小钗
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
S
Security Affairs
The Hacker News
The Hacker News
Simon Willison's Weblog
Simon Willison's Weblog
博客园 - 三生石上(FineUI控件)
B
Blog
Apple Machine Learning Research
Apple Machine Learning Research
C
Cyber Attacks, Cyber Crime and Cyber Security
D
DataBreaches.Net

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
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.