Every few months someone publishes a think-piece declaring X dead for developers. The developer exodus is real, they say. Everyone’s on Bluesky now, or Mastodon, or back to blogging. And yet, if you actually look at where technical conversations happen in real time — where a new library gets its first thousand stars, where a hot take about microservices spirals into a 200-reply thread — it’s still happening on X.

X isn’t what it was in 2020. But for developers specifically, the platform still works. It just works differently than LinkedIn, and if you treat the two platforms the same way, you’ll get mediocre results on both.

The fundamental difference: speed vs shelf life

LinkedIn is slow. A post builds momentum over 24 to 48 hours. People comment on it days later. The algorithm resurfaces it when someone in your network engages. It’s a marathon.

X is a sprint. Your tweet gets most of its impressions in the first 60 to 90 minutes. If it doesn’t catch, it’s gone. If it does, the retweets compound fast. This changes everything about how you write.

On LinkedIn, you can take three paragraphs to set up context before you get to the point. On X, the point IS the first sentence. There’s no room for a preamble, and the audience doesn’t have the patience for one anyway. If your tweet starts with “I’ve been thinking a lot lately about…”, you’ve already lost most people.

What actually gets engagement from developers on X

After spending way too long studying what works on the platform, the patterns are clear. Developer engagement on X clusters around a few specific content types.

Tool discoveries and recommendations. “Just found [tool] and it replaces my entire [workflow]. Here’s the setup:” followed by a screenshot or a short code snippet. Developers on X are perpetually hunting for things that make their lives easier. If you can be the person who surfaces those things, people follow you for it.

Concise, opinionated takes. Not rage-bait. Actual opinions backed by experience. “We moved from Kubernetes to a single VPS and our infra costs dropped 80%. Sometimes boring technology is the right technology.” That’s the kind of thing that gets quote-tweeted with “this” by people who’ve had the same experience. If you’ve been building in public on LinkedIn, the same instincts apply here — but compressed.

Short build logs. “Shipped dark mode today. Took 2 hours. CSS custom properties + a class toggle on the body. No library needed.” That’s it. That’s the tweet. Developers respect showing your work, even when the work is small.

Code snippets that teach something specific. Not a tutorial. Not a thread-length walkthrough. One screenshot or code block that shows a single useful technique. The more niche, the better — “TIL you can use git log --all --oneline --graph to visualise your branch history” outperforms a generic “10 Git tips” list.

Humour. This is the big one that separates X from LinkedIn. Being funny works on X in a way it simply doesn’t on LinkedIn. A well-timed joke about dependency hell or a meme about CSS specificity gets shared far more than a polished insight. The developer community on X has a shared sense of humour rooted in the daily absurdity of writing software, and leaning into that is a legitimate growth strategy.

What tanks on X

Just as instructive as what works is what absolutely doesn’t.

Corporate speak of any kind. “We’re thrilled to announce our latest integration with…” Stop. Nobody on X is thrilled. If you sound like a press release, you’ll get ratio’d or — worse — ignored entirely.

Excessive hashtags. This isn’t Instagram. One hashtag is fine. Two is pushing it. Five is a signal that you don’t understand the platform. Most high-engagement developer tweets use zero hashtags.

Thread-bait openers. “I’ve spent 10 years in tech. Here are 15 lessons I’ve learned. A thread:” This worked in 2021. It’s been run into the ground. If your thread opener sounds like it was generated by a “viral tweet template,” people will scroll past it.

Long preambles before the useful content. On X, bury the lede and the lede stays buried. Forever. Front-load the interesting part.

Formatting: the tactical stuff

Optimal tweet length is genuinely shorter than most people think. Data consistently shows that tweets between 70 and 140 characters get the highest engagement rates. You don’t have to hit that every time, but it’s worth noting that brevity is rewarded more aggressively on X than anywhere else.

When it comes to threads vs single tweets, the calculus has shifted. Threads used to be X’s long-form content play. They still work, but the bar is higher now. A thread needs to earn its length — each tweet in the thread should stand alone as something worth reading, not just be a continuation of a sentence you broke up to inflate the thread count. If your thread is really just one tweet’s worth of insight stretched across seven tweets, you’re annoying people.

A better pattern for longer content: write a single tweet with the core insight, then link to a blog post or a longer write-up for people who want depth. This respects the platform’s native format while still giving you a path to detailed content.

Quote tweets are underused by developers. When someone tweets something you have direct experience with, a quote tweet adding your own specific context — “We tried this exact approach and here’s what happened” — performs well because it’s riding existing engagement while adding genuine value.

Patterns worth studying

You don’t need me to name specific accounts. Instead, look for these patterns in developers who consistently get engagement.

The “builder’s diary” pattern: someone who tweets every day or two about what they’re working on. Short, specific updates. “Fixed a gnarly race condition in the queue processor today. The bug only manifested under load. Solution: idempotency keys on every job.” These accounts build a following because they’re consistently interesting in small doses.

The “tool curator” pattern: someone who’s always discovering and sharing dev tools, libraries, and techniques. They become a filter for the firehose. People follow them so they don’t have to evaluate everything themselves.

The “opinionated practitioner” pattern: someone who has genuine takes backed by real experience. Not contrarian for the sake of it — just unafraid to say “I think X is better than Y because of Z” and engage with the replies.

All three of these patterns share a common trait: they’re rooted in real work. Nobody is making things up or performing expertise they don’t have. The content comes from the work, not from a content strategy document.

How ShipPost handles X differently from LinkedIn

The same PR or URL that generates a narrative LinkedIn post should produce something completely different for X. The audience is different, the format is different, and the tone expectations are worlds apart. If you’re thinking about developer LinkedIn strategy alongside X, you need to understand that cross-posting the same text to both platforms is a losing move.

ShipPost generates platform-specific output from the same source material. The LinkedIn variation gets a hook, context paragraphs, and a professional-but-human tone. The X variation gets stripped down to the essential insight — punchier, more opinionated, shorter.

The shitposter tone preset exists specifically for X. It takes the factual content from your PR or URL and rewrites it with the kind of casual, slightly irreverent voice that actually performs on the platform. It’s not about being offensive — it’s about matching the register that developers on X expect and respond to.

You can also use ShipPost to generate LinkedIn posts from your PRs and X posts from the same source in a single session, then tweak each one to fit. Different hooks that work on each platform is something we explored in our LinkedIn hooks guide — and the same principle applies to X, just compressed.

The platform isn’t the strategy

Here’s the thing nobody wants to hear: X, like any platform, is just distribution. The actual strategy is having interesting things to say because you’re doing interesting work. If you’re building things, making technical decisions, solving real problems, the content is already there. X is just where you share it.

The developers who do well on X aren’t “doing content.” They’re doing work and talking about it. That’s the whole secret. No content calendar. No engagement pods. Just work, shared in real time, in a format the platform rewards.

Try ShipPost free — no credit card, no subscription. Bring your own API key.

Developer LinkedIn Strategy for 2026 — the LinkedIn-specific counterpart to this guide
LinkedIn vs X for Developer Marketing — a direct comparison of both platforms
Turn Your PRs into Posts — how ShipPost generates platform-specific content from your merged PRs