Developers are reachable, but not through the channels most marketing playbooks assume. They block ads, ignore cold email, and distrust anything that feels like a funnel. They do pay attention to peers, to genuinely useful content, and to being where the work happens. Distribution for developers is mostly about earning attention, not buying it.

Where developers are

  • Search. The default entry point. Developers search by task and land on docs, tutorials, and Q&A. Owning task-intent search is the most durable channel you have.
  • Peer networks & word of mouth. The strongest force in developer adoption. Tools spread developer-to-developer and team-to-team. Everything that increases the odds a happy developer tells another is distribution.
  • Community platforms. GitHub, Stack Overflow, Reddit (r/programming and niche subs), Hacker News, Lobsters, Discord/Slack communities, and increasingly Bluesky and Mastodon for technical discussion. Presence means participating, not posting brochures. The shares now have a current measurement: Stack Overflow’s 2026 survey asked which platforms developers “worked with last year” (10,741 answers; a panel recruited largely through Stack Overflow itself, so discount its own 69%) and got GitHub 70%, YouTube 58%, Reddit 54%, LinkedIn 38%, Discord 33%, Hacker News 24%, X 16%, Bluesky 13% and Dev.to 10% - so X now trails Hacker News among developers, and the platform below is one that more than half of them used last year. Reddit is closing its outside doors: it announced on 2026-09-30 that RSS feeds end on 13 November 2026 and public API access closes for good by March 2027, citing AI scraping, with new API applications stopping 31 October and a $1M fund to move third-party apps onto its own Devvit platform. Anything that watches or posts to subreddits from outside - a listening tool, a feed reader, a social-monitoring vendor - needs a plan this quarter; participation by a person in a browser is unaffected.
  • Content platforms. Dev.to, Hashnode, personal blogs, YouTube (long-form tutorials and conference talks), and technical newsletters.
  • Events. Conferences, meetups, hackathons, and workshops - high cost, high trust, best for depth and relationships rather than reach. Decide the objective before the budget (leads, launch, community, customer time), because an event booked for “awareness” is the one most teams cannot say afterwards whether it worked. The running of them belongs to community and DevRel.
  • Open source. A useful open-source project is a distribution channel: it earns stars, contributors, and top-of-mind presence with exactly the right people. The repo is the page that channel lands on.
  • AI assistants & answer engines. A growing share of first impressions are machine-mediated: a coding assistant or answer engine paraphrases your docs - and, increasingly, compares you against alternatives when a developer (or their agent) is choosing a tool. You cannot buy presence here; you earn it with retrievable docs and specific, quotable facts, and you measure it by asking assistants task-shaped questions in your category and checking whether, and how accurately, you appear. What pays and what is ritual is answer engines’ subject.
  • Agent rails. The directories, marketplaces and protocols an agent reaches your product through - the model vendors’ connector directories, the platform-owned agent marketplaces, the publisher programmes - are curated, reviewed channels with queues of their own, and building the integration and distributing it are two different jobs. The rails inventory, the queue risk and the dual-listing rule are agent rails’ subject.

Earned beats paid

For most developer products the ranking is: earned > owned > paid.

  • Earned - a developer’s blog post, a HN front page, a conference talk, a GitHub trending spot, a peer recommendation. Highest trust, hardest to manufacture, worth the most.
  • Owned - your docs, blog, community, newsletter, and open-source repos. The compounding base you fully control.
  • Paid - sponsorships (newsletters, podcasts, conferences, OSS) tend to outperform display/programmatic, because they borrow trusted context. Straight ads to developers are usually a poor return.

Per-platform tactics are deliberately not in this guide. How a Show HN title should read this month, what format a Reddit post needs in a given subreddit, which LinkedIn hook is working - that is real craft and it dates in weeks, so it lives in the swipe file as sourced artifacts you can go and look at rather than as prose here that would be quietly wrong by the time you read it. This section is about which channels to be in at all, and that changes slowly.

Channels that repel

  • Interruptive ads and pop-ups on technical content.
  • Cold sales outreach to individual developers, especially “I noticed you use X” spam.
  • Gating everything behind forms - it shrinks reach far more than it grows pipeline.
  • Astroturfing. Fake community engagement, undisclosed shilling, or planted reviews. If discovered - and it usually is - the reputational cost dwarfs any short-term gain.

Pick few, go deep

You cannot be excellent everywhere. Concentrate on the two or three channels where your specific developers actually are, and earn a real presence there, rather than spreading thin across every platform. Depth builds the trust that breadth can’t.