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

推荐订阅源

Google Online Security Blog
Google Online Security Blog
S
Security @ Cisco Blogs
Recent Commits to openclaw:main
Recent Commits to openclaw:main
人人都是产品经理
人人都是产品经理
The Hacker News
The Hacker News
W
WeLiveSecurity
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
The Cloudflare Blog
博客园 - 司徒正美
雷峰网
雷峰网
L
LINUX DO - 最新话题
博客园 - 叶小钗
云风的 BLOG
云风的 BLOG
The Last Watchdog
The Last Watchdog
V2EX - 技术
V2EX - 技术
S
Security Affairs
有赞技术团队
有赞技术团队
月光博客
月光博客
T
Threatpost
T
Tor Project blog
O
OpenAI News
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
V
V2EX
Know Your Adversary
Know Your Adversary
Project Zero
Project Zero
博客园 - 三生石上(FineUI控件)
D
Docker
AWS News Blog
AWS News Blog
AI
AI
P
Proofpoint News Feed
K
Kaspersky official blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
D
Darknet – Hacking Tools, Hacker News & Cyber Security
www.infosecurity-magazine.com
www.infosecurity-magazine.com
S
Securelist
F
Fortinet All Blogs
F
Full Disclosure
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
量子位
Hacker News - Newest:
Hacker News - Newest: "LLM"
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
P
Palo Alto Networks Blog
Cyberwarzone
Cyberwarzone
Cisco Talos Blog
Cisco Talos Blog
美团技术团队
N
News | PayPal Newsroom
T
The Blog of Author Tim Ferriss
MyScale Blog
MyScale Blog

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
Your Team Doesn't Need a Buddy. It Needs a Coach.
Jono Herring · 2026-05-09 · via DEV Community

I have sat in too many 1:1s where everyone felt better walking out and nothing changed two weeks later. No clear gap named. No behavior contract. No follow-through. That is why I believe most managers fail people in one of two ways. They run 1:1s like status meetings, or they run them like friendship maintenance.

Both feel safer than coaching, and neither grows people. I am a huge believer in Radical Candor by Kim Scott. It is one of the foundational books in my leadership toolkit because it names something most leaders quietly avoid ... people prefer clarity, even hard clarity, over relational fog. Not cruelty. Clarity. There is a difference.

I have gotten this wrong before too. I have leaned too relational in moments where direct coaching was needed, and all I really did was postpone growth conversations that would have helped sooner.


When managers avoid mentoring, 1:1s become project check-ins. Tickets, blockers, updates, next steps. Useful operationally. Empty developmentally. When managers avoid confrontation, they become buddies. High empathy, low challenge. Good vibes, slow growth. Both are forms of comfort for the manager, not growth for the person.

You can feel this pattern fast. The manager feels supportive. The engineer feels encouraged. Then two sprints pass and the same behaviors are still there because nothing concrete got challenged or contracted.

A 1:1 that never creates productive tension is usually a status ritual with a human face.

Coaching Is a Performance System

Championship teams do not happen because players are talented. They happen because talent is paired with coaching that raises standards consistently. People remember Brady and Belichick, Jordan and Jackson, Jeter and Torre for a reason. Strong players need strong coaching pressure, or talent gets misallocated into whatever feels easiest that week.

Engineering teams are no different. If your highest performers are never challenged, they plateau. If your struggling performers are never confronted, they linger. If everyone gets the same soft feedback language, nobody knows where they actually stand. When people do not know where they stand, they start guessing what leadership wants. Guessing creates politics. Clarity creates growth.

The Manager vs Leader Split

Managers often optimize for role stability. Leaders optimize for person growth. That sounds small. It changes everything.

When you develop people only for current role convenience, you create a short-term staffing win and a long-term attrition plan. People feel it fast. They may stay physically for a while, but mentally they exit early. When you develop people toward who they want to become, you may lose some to bigger opportunities. You also build a reputation where stronger people want to work with you because they know growth is real, not performative. The irony is this usually improves retention, not hurts it. People do not leave only because work is hard. They leave when growth is fake.

This is where manager-vs-leader stops being philosophy and becomes retention math. If strong people keep saying some version of "I am not growing," start with coaching quality before you blame compensation or market conditions.

And this is where many teams get stuck. They think mentorship quality is a "soft" variable while attrition is a "hard" metric. In practice, they are directly connected. Poor coaching quality delays growth, delayed growth weakens trust, weak trust accelerates exits.

A Better 1:1 Structure

If you want to stop buddy-mode and status-mode, run 1:1s with 3 sections.

  1. Reality. Where are you truly strong right now, and where are you not?
  2. Stretch. What behavior at the next level are you not yet demonstrating consistently?
  3. Contract. What is one concrete action you own before next 1:1, and what support do I owe you?

That structure keeps empathy and standards in the same room. You are not choosing between being kind and being direct. You are choosing whether to be useful.

Everyone loves "supportive leadership" until supportive leadership starts asking for evidence.

Use feedback language people can execute.

Weak ... "You need to be more strategic."

Better ... "At next level, you need to delegate this class of work and spend that time framing trade-offs for the team. This week, delegate one workstream with clear ownership boundaries."

Weak ... "You're doing great, keep going."

Better ... "You execute well, but your risk callouts are late. By next check-in, I want one proactive risk flag before it escalates."

Specific feedback is actionable. Vague encouragement is emotional sugar.

The Confrontation Most Managers Avoid

Many managers say they do not want to be "the a*sshole." Fair. But there is another failure mode nobody likes to name ... being so relational that people cannot tell if you believe in their growth enough to challenge them.

Silence is not kindness when the person is drifting. Vague praise is not support when the person needs direction. Delayed feedback is not empathy when the consequences get bigger every sprint. You do not need to be harsh. You do need to be honest.

The practical bar is simple.

  • state the gap clearly
  • tie the gap to their own goal
  • define the next behavior
  • commit support and follow-up

That is coaching. Anything else is often avoidance with nicer wording.

One practical way to reduce confrontation avoidance is to separate intention from behavior in your language.

  • "I know your intent is strong."
  • "The behavior I need to see at next level is X."
  • "Here is the first place we will test it."

That keeps the person respected while keeping the standard non-negotiable.

If your feedback style protects your comfort more than their growth, you are managing your own anxiety first ... and calling it mentorship second.

A Simple Coaching Scorecard

If you want this to be operational, track 1:1 quality with three weekly checks.

  1. Was one growth gap named clearly?
  2. Was one next-level behavior contracted?
  3. Was follow-up evidence reviewed?

If two or more are "no," it was a check-in, not coaching. This scorecard is intentionally simple so it actually gets used. Either you named a gap, contracted a behavior, and followed up, or you did not. If you cannot answer those three with evidence, your team is not being coached ... it is being managed for updates.

The Hard Part Is Not Giving Feedback ... It Is Holding the Line

Most managers can have one hard conversation.

Fewer managers can hold the same standard for six weeks when deadlines get loud, people get emotional, and every excuse starts sounding reasonable.

That is where coaching systems usually break.

You name a behavior gap on Monday. By the following sprint, pressure rises, roadmaps wobble, and everyone silently agrees to deprioritize development language because delivery feels more urgent. Then you wonder why the same growth gap is still there at quarter close.

The gap is not awareness. The gap is consistency under stress.

One framing that helped me was this ... every unchallenged repeated behavior is a standard you just approved. You may not have intended to approve it. Your team still reads your silence as approval.

That is why follow-up is not administrative overhead. Follow-up is the core leadership act:

  • "We agreed this would change. What changed?"
  • "Where did it break under pressure?"
  • "What support is still missing from me?"

Those questions keep dignity in the room while keeping the bar in the room.

And yes, sometimes the answer is that your expectation was unrealistic for the current context. Great. Adjust it in public. Real coaching is not rigidity. It is honest calibration. But do not call it calibration when what actually happened was avoidance.

If you want to know whether you are drifting into buddy mode, watch what happens after discomfort. Coaches stay present after discomfort. Buddies relieve discomfort and move on. That one difference determines whether your people feel briefly encouraged or permanently developed.

If you want one practical stress test, run this at the end of each week with your direct reports ... "Which feedback from me changed how you worked this week?" If they cannot answer, you are likely giving advice that sounds supportive but is not landing as behavior change. That does not make you a bad manager. It means your coaching loop needs one more turn. Better question, tighter contract, clearer follow-up. Small changes there compound hard over a quarter.

Coaching quality is not measured by how clear you felt while giving feedback. It is measured by whether behavior changed when the week got hard.

This Week

Pick one 1:1 and run one coaching moment you have been postponing.

  • state the gap clearly
  • define the next-level behavior
  • agree on one measurable action by next check-in

Then follow up. No follow-up equals performative candor.

Said differently ... if every hard conversation dies in your notes app, you are not coaching. You are journaling.

If you want one forcing function, end the 1:1 with this question ... "What will be true in two weeks if this conversation actually worked?" Write the answer down and review it together next time. That one move will tell you whether your 1:1s are changing behavior or just reducing tension for an hour. If the same gap appears three 1:1s in a row with no new action, stop calling it development. It is now avoidance debt, and leadership owns it.

If this resonates, pair it with Most 1:1s Are Career Drift Meetings for the growth-roadmap side of the same system.

Your team does not need another manager who is easy to work for. They need a leader who is clear enough to grow under. At work, real care often looks less like comfort and more like a standard you can actually hit.


One email a week from The Builder's Leader. The frameworks, the blind spots, and the conversations most leaders avoid. Subscribe for free.