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

推荐订阅源

D
Darknet – Hacking Tools, Hacker News & Cyber Security
宝玉的分享
宝玉的分享
Hugging Face - Blog
Hugging Face - Blog
Recent Announcements
Recent Announcements
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Vercel News
Vercel News
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
T
The Blog of Author Tim Ferriss
博客园 - 司徒正美
Cyberwarzone
Cyberwarzone
S
Securelist
www.infosecurity-magazine.com
www.infosecurity-magazine.com
The GitHub Blog
The GitHub Blog
云风的 BLOG
云风的 BLOG
T
Tenable Blog
NISL@THU
NISL@THU
博客园 - 三生石上(FineUI控件)
V
Vulnerabilities – Threatpost
N
Netflix TechBlog - Medium
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
S
SegmentFault 最新的问题
WordPress大学
WordPress大学
C
CXSECURITY Database RSS Feed - CXSecurity.com
G
Google Developers Blog
Forbes - Security
Forbes - Security
月光博客
月光博客
博客园 - 叶小钗
Spread Privacy
Spread Privacy
Last Week in AI
Last Week in AI
H
Help Net Security
TaoSecurity Blog
TaoSecurity Blog
Scott Helme
Scott Helme
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
Stack Overflow Blog
Stack Overflow Blog
N
News and Events Feed by Topic
爱范儿
爱范儿
aimingoo的专栏
aimingoo的专栏
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
The Hacker News
The Hacker News
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
P
Privacy International News Feed
D
DataBreaches.Net
O
OpenAI News
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
Latest news
Latest news
J
Java Code Geeks
Project Zero
Project Zero
V
V2EX
Security Latest
Security Latest
AI
AI

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
You're Promoting Confidence, Not Leadership
Jono Herring · 2026-05-07 · via DEV Community

A contractor lead walked into our org with strong language, strong opinions, and all the right lead-shaped signals ... then a basic desktop and mobile navigation effort took about 6 months. That gap is why I say if your system rewards how someone sounds in the room more than what their team can consistently ship, you are buying charisma at a leadership price tag.

I am not talking about someone we were considering promoting. I am talking about someone who came in already positioned as a lead from prior roles, and in our system he should never have been in that seat.

He was vocal, opinionated, and communicative. On the surface, he looked lead-like. Under real delivery pressure, the signal changed. He could not reliably deliver, he could not delegate and deliver through others, and he took everything on himself until he became the bottleneck. Strong talk. Weak follow-through. One basic desktop and mobile navigation effort took roughly 6 months. That was the receipt, and it was not because the problem was unsolvable. Lead-level leverage was missing. When someone in a lead seat cannot break work down, delegate with clarity, and keep momentum through the team, the org pays twice ... once in delay and once in trust.


This is where promotion conversations get uncomfortable. Most leaders agree that communication matters. It does. You cannot lead if nobody understands you. Communication is a multiplier sitting on top of delivery leverage. Strip the leverage out from under it and you get an illusion amplifier. You can make a weak operating system look healthy for a while. Then deadlines slip, teams stall, and trust drops quietly.

In our case, we exited that contractor lead and transitioned to another front-end lead. The replacement was quieter, still communicative, and far more effective where it mattered. He delivered when he said he would deliver, helped the team, earned trust, and showed up when needed. That is lead material, and that contrast is the entire point. Personality style was a red herring. The scoreboard was the story.

A lead is not measured by how convincingly they speak about execution. A lead is measured by whether execution compounds through the team.

The Promotion Mistake Hiding in Plain Sight

Teams often say they value leadership and execution. Their criteria usually reveal what they really reward.

If your signals are mostly presentation-heavy, you will drift toward promotable appearance.

  • strong meeting energy
  • polished updates
  • confident framing
  • visible ownership language

Those can all be useful, and none of them prove leverage on their own.

A polished status update is still just a polished status update.

Leverage is harder to fake.

  • work lands when promised
  • complexity gets delegated, not hoarded
  • teammates become more effective, not more dependent
  • delivery quality holds under pressure

If your system does not explicitly score those, you will accidentally reward charisma over compounding. Most organizations think they do not do this until you ask one practical question in calibration ... "Show me the evidence this person delivers through other people under pressure." If the room answers with presentation examples, communication polish, or "strong executive presence," you already have your answer ... you are scoring narrative, not leverage.

What to Evaluate Instead

If you want better lead calibration, evaluate for these 4 behaviors.

  1. Delivery reliability. Do they ship what they commit to at lead scope?
  2. Delegation quality. Can they distribute work without dropping quality or context?
  3. Team multiplication. Are people around them becoming stronger and faster?
  4. Pressure behavior. When things get messy, do they create clarity or chaos?

Notice what is missing from this list ... volume, presence, meeting dominance.

A person can be brilliant in a room and still be a drag on team throughput. A person can be quiet and still run a championship-level operation.

One nuance that matters ... communication remains essential. I am not anti-communication here. A lead who cannot communicate is also a risk. Communication is table stakes, not differentiation. Differentiation at lead level is execution multiplication. Can this person make the team better at delivering together, not just themselves better at talking about delivery? That is the question.

Why This Is an Org Risk Before It Is a Personality Debate

Introverts versus extroverts misses the point. Your promotion system is only as healthy as the signals it trusts. If your signals are noisy, you get noisy leaders, and noisy leaders create unstable systems. Unstable systems produce the exact problems everyone blames on "execution culture," and then companies run another leadership workshop and call it transformation while the bar does not move because the scoreboard did not change.

Once this pattern sets in, it cascades. Strong doers stop trusting upward decisions. Emerging leaders copy performative behaviors because those look rewarded. Promotion debates become political instead of operational. Eventually you get a leadership layer that is great at recapping execution and weak at driving it, and then companies blame "talent market issues" for the culture they just incentivized.

The Calibration Check I Use

If you want a practical filter, use this during promotion conversations.

  1. What meaningful outcome did they own at this level?
  2. What part of that outcome happened through team leverage, not individual heroics?
  3. What evidence shows they improved other people’s execution quality?
  4. What happened when constraints got ugly?

If answers are fuzzy, narrative-heavy, or overly dependent on intent language, wait.

The Interview Trap That Creates This

This promotion pattern usually starts upstream in hiring. Someone interviews well, presents strongly, has good language for strategy, and checks all the boxes in a panel environment built around articulation. Then real work begins, and real work asks different questions.

  • can they break ambiguous scope into deliverable chunks
  • can they delegate without dropping context
  • can they recover when assumptions fail
  • can they keep team momentum when pressure spikes

If your hiring and promotion systems over-index on narrative skill, you will repeatedly import the same risk into lead roles. Keep communication sacred ... and bolt it to delivery leverage in your criteria so polish cannot travel alone.

What This Costs the Team

When the wrong lead signal wins, the cost is not just one missed project. It spreads into trust, execution quality, and retention.

The Quiet Tax on Real Operators

The most expensive part of bad promotion signals is not visible in a single quarter.

It is the quiet tax you place on your actual operators.

When people who multiply teams keep getting ranked below people who multiply impressions, your strongest builders start making a different calculation. They stop asking "How do I grow here?" and start asking "What does this place actually reward?"

That question changes behavior fast:

  • some adapt by performing the rewarded theater
  • some disengage and do only what is required
  • some leave and take leverage with them

Leadership teams usually experience this as "retention noise" or "market churn." It is often signal design debt.

One practical check that helps surface this early is to review promotions backward from outcomes six months later:

  1. Did this person increase team throughput predictably?
  2. Did they reduce decision latency under pressure?
  3. Did they make other people stronger in measurable ways?
  4. Did delivery quality improve around them?

If two or more answers are unclear, your promotion criteria were probably over-indexed on in-room performance.

If that makes people uncomfortable in calibration, good. Discomfort is cheaper than six more months of narrated under-delivery.

One extra safeguard worth adding is a six-month proof review at promotion time. Ask one blunt question ... "Did this person create stronger decisions and better delivery through others, or did they mostly create better updates about the same delivery?" That distinction keeps your system honest when charisma and certainty are competing with operating leverage.

I like this review because it strips away interview glow and calibration politics. The scoreboard gets a vote. People can still grow into a role, absolutely. But when growth into role becomes a default justification for weak leverage evidence, you are running optimism as policy.

And optimism as policy usually creates one predictable outcome ... the team with the highest standards starts feeling gaslit by the team with the loudest updates.

Another way to protect against this drift is to require one "through-others" proof in every lead promotion packet. Not a personal hero story. A concrete example where they set direction, delegated execution, and improved the outcome through the team. This requirement sounds small, but it instantly separates individual excellence from lead-level leverage. If the packet cannot produce that proof, the timing is wrong even if the person is talented.

When talk gets promoted above leverage, teams do not get led. They get narrated.

This Week

Take your lead-level criteria and run one simple test. For each criterion, ask whether it predicts delivery leverage or presentation quality. If it mostly predicts presentation, rewrite it. Then calibrate one recent lead decision against the rewritten criteria and see what changes.

If you want a sharper test, do this in your next calibration.

  • remove names
  • remove personality language
  • review only delivery leverage evidence

Then compare outcomes with the version where names and presence context are included. If the ranking changes dramatically, your system is more biased toward presentation than performance. You do not need a villain to explain that drift. You need clearer criteria.

If this resonates, read Your Team Is One PTO Away from Missing the Quarter for what low-leverage leadership looks like at system level.

Promotion systems are culture systems. Who you elevate is what you multiply. If you multiply confidence without leverage, you get louder problems, and louder problems always show up as execution problems later.


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