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

推荐订阅源

Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
月光博客
月光博客
MyScale Blog
MyScale Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
爱范儿
爱范儿
P
Proofpoint News Feed
人人都是产品经理
人人都是产品经理
Last Week in AI
Last Week in AI
罗磊的独立博客
G
Google Developers Blog
Y
Y Combinator Blog
博客园 - 【当耐特】
WordPress大学
WordPress大学
大猫的无限游戏
大猫的无限游戏
博客园 - 叶小钗
J
Java Code Geeks
酷 壳 – CoolShell
酷 壳 – CoolShell
V
Visual Studio Blog
美团技术团队
宝玉的分享
宝玉的分享
Jina AI
Jina AI
小众软件
小众软件
T
Tailwind CSS Blog
A
About on SuperTechFans

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
Why does a post with 400 impressions get zero replies?
Deva · 2026-06-04 · via DEV Community

Deva

Why does a post with 400 impressions get zero replies?

I ran an audit on the last 8 LinkedIn posts my content system generated. 0 of 8 ended with a question. 6 of 8 ended on a line of hashtags. Every single one closed as a monologue. Good impressions, nearly zero replies.

The failure was architectural, split across two layers: generation and critique.

The generation problem

In generate.py, the dominant format is image_text (10 of 12 scheduled posts per cycle). That format had no closing instruction at all. The text format said "end with one opinion OR one open question" and the model defaulted to opinion every time, which made sense from its perspective: opinions are lower variance, easier to write confidently. Rule 11 sent hashtags to the post's final line, so even when a question appeared, it was buried above a tag wall.

The model was following its instructions perfectly. The instructions just did not specify the one thing that matters for engagement: whether the exit invites a response.

The critic problem

critic.py scored hook quality and information density. It did not score the close. A draft could spend 90% of its length making a sharp, substantive point and then end with "Thoughts welcome #buildinpublic" and it would pass. No one was watching the door.

This is the kind of bug that is easy to miss because the drafts look good. The rubric was measuring the right things for quality. It just was not measuring the right thing for engagement.

The fix

I added rule 16 to the system prompt: the last line must be a specific, answerable question or a clearly debatable take. Not a summary, not hashtags.

Rule 11 now moves hashtags one line above the close. They still help with reach, they just do not occupy the final position.

The format hints now explicitly mandate a closing question for text, image_text, and carousel formats. No more format ambiguity where the model picks the default lower variance option.

Most importantly, I added a FLAT CLOSE hard fail to the critic rubric: if the draft ends without a reply on ramp, verdict is revise, score is capped at 3. The post does not ship. It regenerates until it gets the close right.

I ran fresh generation to verify. New posts end with a specific question. I fed the critic a deliberately flat closing draft and it hard failed immediately.

What I would do differently

Add the critic gate first. The generation prompt change reduces the probability of a bad close. The critic gate is what makes it a guarantee. If I had added FLAT CLOSE as a rubric dimension from day one, I would have caught this after 1 post, not 8.

The general principle: if your generation prompt says "do X or Y," your critic must explicitly fail Y when Y is the wrong choice. Ambiguous generation instructions need unambiguous critic tripwires.

Does your content system have a critic layer, or are you shipping whatever the generator returns?