CHABOT.DEV — A FIELD JOURNAL — VOLUME I, NO. 4

09    PLATFORMS   ✣

Twitter / X.

For approximately fifteen years, Twitter was the central informal gathering place of "dev Twitter" — a global, mostly-public, real-time conversation among software developers, technical analysts, founders, and journalists. Since Elon Mus…

For approximately fifteen years, Twitter was the central informal gathering place of “dev Twitter” — a global, mostly-public, real-time conversation among software developers, technical analysts, founders, and journalists. Since Elon Musk’s October 2022 acquisition, that role has been substantially eroded but not entirely replaced.

History (developer relevance)

  • Founded. 2006 by Jack Dorsey, Noah Glass, Biz Stone, Evan Williams.
  • Developer launch. Twitter API launched in 2006; for several years the API was unusually open and powered a thriving third-party client ecosystem (Twitterrific, Tweetbot, Echofon, Twitterific, TweetDeck, etc.).
  • Peak developer-platform years. Roughly 2008–2013, when Twitter was the standard distribution channel for technical blog posts, startup launches, and conference back-channels.
  • 2012 API restriction. Twitter began limiting third-party clients, breaking many tools and souring relationships with developers.
  • 2018 further restrictions. Token-bucket throttling and API limits.
  • 2022 Musk acquisition. October 27, 2022. Within weeks ~80% of staff reduced.
  • 2023 API repricing. Free API tier eliminated; new commercial pricing tiers introduced. Killed remaining third-party clients (Tweetbot, Twitterrific officially shuttered).
  • 2023 rebranding. Twitter became X.
  • 2024–2026 status. Substantial migration to Bluesky and Mastodon. Some senior developers maintain X presence for reach; many cross-post; a portion of the community has left entirely.

What X is still useful for

Despite the migration, X retains meaningful reach for DevRel work in 2026:

  • Senior industry conversation. Many founders, executives, and analysts still operate primarily on X.
  • AI engineering. Some of the AI community remained on X partly because of Musk’s xAI presence and partly because of established networks.
  • Launches. A coordinated launch announcement still reaches many engineers on X.
  • Cross-platform amplification. Posts on X that link to Hacker News, dev.to, or YouTube produce non-trivial click-through.

What it is no longer useful for

  • Comprehensive developer reach. Many developers, particularly those who left in 2022–2023, no longer see X content.
  • Reliable link distribution. X’s algorithm penalises posts with external links; reach for content with links is significantly lower than for native text.
  • Third-party tool integration. API restrictions broke the analytics, posting, and integration tools many DevRel teams relied on.

Notable developer voices remaining

Approximate followers as of 2026 (snapshots, refresh from platform):

  • DHH (David Heinemeier Hansson, 37signals / Rails) — >700K
  • Patrick Collison (Stripe) — >400K
  • John Resig (jQuery creator, Khan Academy) — >700K
  • Linus Torvalds maintains limited presence
  • Brad Frost (design systems) — >100K
  • Cassidy Williams (GitHub) — >200K
  • Kelsey Hightower — >250K
  • Theo Browne (t3.gg) — large frontend audience
  • Lee Robinson (Vercel) — large Next.js audience
  • swyx (Shawn Wang) — large AI-engineering audience
  • Levelsio (Pieter Levels) — large indie-hacker audience

Many of these accounts cross-post to Bluesky in 2024–2026.

How DevRel teams operate on X in 2026

  • Treat it as one channel of several rather than the channel.
  • Cross-post critical content to X, Bluesky, LinkedIn, and your own newsletter.
  • Prioritise native content (X favours posts without external links).
  • Use threads for longer-form content.
  • Engage with existing developer conversations through reply rather than only broadcasting.
  • Recognise the trust deficit. Some developers’ impression of company-account engagement on X has degraded; named-individual posting is more credible.

API and developer-platform status

X’s developer platform technically still exists at developer.x.com but is much-reduced from peak Twitter API:

  • Free tier limited.
  • Paid tiers expensive for hobby developers.
  • Many endpoints removed or restricted.
  • No more third-party client ecosystem of any meaningful scale.

For most developer-product DevRel teams, X integration is no longer a viable build target.

Cultural shifts since 2022

  • Tone has shifted. The conversational, expert-rich character of “dev Twitter” 2014–2021 has thinned.
  • Algorithmic feed. The “For You” feed dominates; chronological “Following” is available but de-emphasised.
  • Verification. Blue-check meaning changed; visibility is partly paid-tier-gated.
  • Quote-replies and engagement-bait. More common than in earlier era.
  • Cross-posting. Many users primarily post on Bluesky and mirror to X; the original-content centre of gravity for the technical community has partially shifted.

See also