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

推荐订阅源

月光博客
月光博客
人人都是产品经理
人人都是产品经理
Hugging Face - Blog
Hugging Face - Blog
有赞技术团队
有赞技术团队
阮一峰的网络日志
阮一峰的网络日志
罗磊的独立博客
博客园_首页
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
大猫的无限游戏
大猫的无限游戏
博客园 - 司徒正美
S
SegmentFault 最新的问题
Jina AI
Jina AI
美团技术团队
酷 壳 – CoolShell
酷 壳 – CoolShell
小众软件
小众软件
WordPress大学
WordPress大学
爱范儿
爱范儿
博客园 - Franky
量子位
V
V2EX
Apple Machine Learning Research
Apple Machine Learning Research
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
雷峰网
雷峰网

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
I wrote like a consultant until I learned to write like a...
Mirza Iqbal · 2026-06-27 · via DEV Community
Cover image for I wrote like a consultant until I learned to write like a person

Mirza Iqbal

Two years ago I shipped a post I was proud of.

A clean framework. Three layers, named and numbered. The kind of thing I would put in front of an enterprise client and watch the room nod.

I hit publish.

Then nothing.

No replies. No argument. Not even a quiet disagreement. The post sat there like a slide nobody asked for.

If you have ever shipped something you were proud of and heard only silence, you know the specific weight of it. You start to wonder whether the work was the problem, or whether you are.

I did the thing engineers do. I assumed the cure was more rigour. Sharper diagrams. A tighter map of the problem.

So I wrote another system. And another.

Each one was correct. Each one was useless.

Here is what took me far too long to see.

I was writing about systems. The posts that actually move people are about people.

A framework asks the reader to study. A story asks the reader to recognise themselves. I kept handing strangers a textbook and wondering why none of them felt spoken to.

The change was small and it changed everything.

I stopped opening with the thesis. I started opening with a moment. A real one, with a time and a feeling and a person in it, usually me, usually getting something wrong.

The framework did not leave. It moved underneath, where proof belongs, instead of standing at the front where it blocks the door.

The honest version of my opinion is plain. Expertise is not what connects. Being recognised is. You can be the most qualified voice in the room and still be the one nobody remembers, because you spoke to the problem and never to the person carrying it.

I am still bad at this. I catch myself reaching for the clean diagram, for the safe distance of the expert. The pull never fully goes away.

But the moment I lead with a person instead of a system, the room leans in. Every time.

Your turn

What is the last thing you wrote that nobody answered, and was it about a system or about a person?

If this was useful

I work through this in public, the wins and the freezes both, mostly on LinkedIn and YouTube. If the real version of building in the open is useful to you, that is where it lives. Find me on X, GitHub, and the work at next8n.com.