How to reply on X as a developer so people follow you
By Naod Tadele · · 5 min read
When you have a small audience, your own posts reach almost nobody new. Your replies do. A good reply under a bigger account's post is read by everyone who reads that post, and some of them will tap your name.
That only works if the reply is worth reading. "Great post!" is not. This guide shows what a good reply looks like and how to fit it into a day that already has a job in it.
Why replies work
A reply borrows attention from a post that already has an audience. It also shows how you think, which a bio can't. And it starts real conversations, which is how followers turn into people who care what you build.
The goal is not to get noticed by one big account. The goal is to be useful in front of the people who read it.
Pick the right posts
You don't want the biggest accounts. Their replies are buried within minutes. Look for:
- Accounts a bit bigger than you, in your niche, who actually answer replies.
- Posts less than an hour old. Early replies get read.
- Posts where you know something. If you have no real experience with the topic, skip it.
Make a list of 20 to 30 accounts and check it once or twice a day. A short list beats scrolling the whole feed.
Four reply types that add value
- Add an experience. "We hit the same thing. Our fix was X, and it cost us a week."
- Add a counterpoint, politely. "This holds for small teams. For bigger ones I'd watch out for X."
- Ask a specific question. One that shows you read the post and the author could answer in a line.
- Add a missing detail. A tool, a number from your own project, or a link that helps (only if it truly adds something).
All four share one trait. The reply would still be useful if your name wasn't on it.
What to avoid
- Empty praise. "Love this." It gives readers nothing and gives you nothing back.
- Self promotion. Dropping your product link under someone else's post reads as spam.
- Arguing to be seen. Hot takes in replies attract the wrong followers.
- Replying to everything. Ten thoughtful replies a week beat fifty quick ones.
Examples
A bigger account posts about the pain of writing postmortems. A weak reply:
So true!
A better one, from someone building the fictional product Nightshift:
The worst part for me was the timeline. Rebuilding who did what at 3am from chat logs took longer than the fix. Started pulling it from the alert history instead, saved about an hour a week.
It has a real detail, a real result, and no link. If readers want more, your profile is one tap away, and your pinned post should be ready for them.
A question works too:
Do you write these while the incident is still fresh, or the next morning? We keep going back and forth.
Use replies as a source of posts
A good reply often hides a post. If you wrote three sentences about rebuilding a timeline, you can expand them into a full post on your own account. Replies are also where you learn which problems people actually care about, which is better than guessing.
Keep a note of the questions you answered most often this week. Those are your next posts.
A simple daily routine
Fifteen minutes is enough:
- Open your list of accounts and scan the newest posts.
- Pick the two or three where you have something real to add.
- Write each reply, then read it once and cut anything vague.
- Check yesterday's replies and answer anyone who responded.
Do this for a month before judging it. Replies compound slowly, and the first week usually feels like nothing is happening. Pair it with a bio and pinned post that welcome the visitors you get: see how to write an X bio and pinned post.
How Loudcode helps
Replies take your attention, so your own posts shouldn't take much more. Loudcode reads your GitHub commits, pull requests and releases, plus revenue from Stripe, Polar or RevenueCat, and drafts build in public posts for X in your voice. When someone follows you after a good reply, there is a recent post waiting for them. You review every draft, and nothing is posted until you approve it. For ideas to fill the gaps, see the build in public post ideas.