Lesson 2 of 87 min read

Pick two networks, not all of them

Choose networks by where your users already talk. A plain guide to X, Bluesky, LinkedIn, Reddit, dev.to, Hashnode and YouTube for builders.

In this lesson you will

  • Choose two networks based on where your audience already talks
  • Know what each developer-heavy network is good and bad at
  • Understand community norms before you post on Reddit or in forums

The usual advice is to "be everywhere". For a solo developer that advice is a trap. You open accounts on every network, post the same link to all of them for two weeks, get little back, and quit. The problem was not effort. It was spreading a small amount of effort so thin that no single place saw enough of you to notice.

This lesson helps you pick two networks: one where you post short updates often, and one where you go deep less often. Two is enough to build a habit and small enough to keep it. Everything else can wait, or can receive copies later once your rhythm is stable.

Choose by where your users talk, not where you scroll

Developers often pick networks by habit: "I read X, so I'll post on X." That works only if your audience reads X too. Start from the audience you chose in lesson 1 and ask three questions:

  1. Where do they ask for help? People ask questions where they expect knowledgeable answers. That is where your tool is relevant.
  2. Where do they share what they built? That is where builders pay attention to other builders.
  3. Where do the decision makers read? If someone else approves the purchase (a team lead, a CTO), you may need a second network for them.

A quick way to answer: search for the problem your tool solves, in your audience's words, on each candidate network. Count real conversations from the last month. Not follower counts, not hashtags, actual threads where people describe the pain. The network with the most of those is your first candidate.

What each network is good for

Here is our plain read of the networks developers use most. It is a starting point, not a law; your audience may behave differently.

NetworkGood forWatch out for
XShort build updates, threads about decisions, replying in publicFast feed, posts fade quickly; links can get less reach than native text
BlueskyBuilder and open-source conversations, a calmer feedSmaller in some niches; check your audience is there
LinkedInBuyers, team leads, hiring managers; longer posts about outcomesTone is more formal; pure code talk lands less often
RedditDeep discussion in focused communities, honest feedbackStrict self-promotion norms; each subreddit has its own rules
dev.to and HashnodeLong technical articles, tutorials, postmortemsSlower pace; best as a home for depth, not daily updates
YouTubeDemos, walkthroughs, "watch me fix this" videosHighest effort per piece; plan for fewer, better videos
DiscordA home for your own users and contributorsNot a discovery channel; people join after they find you elsewhere

Notice the pattern. Some networks are for reach (X, Bluesky, LinkedIn): short, frequent, discoverable. Others are for depth (Reddit, dev.to, Hashnode, YouTube): fewer posts, more effort, longer life. A good pair usually has one of each.

A decision rule for your pair

Use this rule to pick:

  • If your users are other developers who build in the open (open-source maintainers, indie hackers, tool authors): X or Bluesky for reach, plus dev.to or Hashnode for depth.
  • If someone else signs off on buying your tool: LinkedIn for reach, plus a long-form home (your own blog, cross-posted to dev.to or Hashnode) for depth.
  • If your users cluster in a few specific communities: one reach network, plus participation in those Reddit communities or forums, following their rules.
  • If your tool is visual or hard to explain in text: one reach network, plus YouTube for short demos.

Then pick the one you will actually open every week. A slightly worse network you use beats the ideal one you avoid.

What about the others? Keep your handle reserved if you like, put your positioning line in the bio, and leave a link. Copies can go there later, once your two-network rhythm is steady. Lesson 6 covers how to spread one piece of work across more places without more writing.

When should you switch? Give a pair at least four weeks of steady posting before you judge it. Switch if, after that, your posts get no replies from people in your audience (not just likes from friends), or if you find you dread opening the app every week. Do not switch because one post did badly; single posts are noisy. Lesson 8 shows how to read your numbers so the decision rests on more than a feeling.

Reddit and community norms

Reddit deserves its own section because developers often get it wrong in the same way: they post a link to their project, it gets removed or downvoted, and they decide Reddit is hostile. Usually the post broke the community's norms.

The norms vary by subreddit, but the general shape is consistent:

  • Read the rules first. Most communities list them in the sidebar or the "about" section. Many limit self-promotion, require a specific flair, or only allow "show your project" posts on certain days.
  • Be a member before you are a marketer. Communities notice accounts that only post their own links. Answer questions, comment on others' work, and contribute for a while before you share your own.
  • Share for discussion, not for clicks. A post that explains a problem, what you tried and what you learned invites replies. A bare link with "check out my tool" invites removal.
  • Disclose that it is yours. Say "I built this" plainly. Hiding it and getting caught costs far more than saying it up front.
  • Keep promotion a small part of what you post. A common rule of thumb in many communities is that your own links should be a small minority of your activity. Check each community's rules for the exact expectation.

Reddit also publishes site-wide rules and guidance on self-promotion; read the current version before you post. The same norms apply to forums, Discord servers and Slack communities you do not own: give first, follow the local rules, and say when something is yours.

Worked example: how we chose our primary networks

We had to make this choice too. Our audience is developers, indie founders and small teams. Our primary networks are X, LinkedIn, Bluesky and Discord. Here is the reasoning, so you can see the rule applied rather than just the result.

  • X is where many builders post short updates and where developer tool conversations happen in public. It is our main reach network for release posts and threads.
  • LinkedIn is where founders and team leads read, the people who decide whether a team adopts a tool. We post outcomes there, not internals.
  • Bluesky has a strong builder and open-source crowd. Our posts there are close to our X posts, adjusted for its conventions.
  • Discord is not for discovery. It is where people who already found us ask questions and give feedback.

We also have Instagram, Facebook, Threads, TikTok, YouTube and Pinterest accounts. They receive copies and occasional visual posts, but we do not plan our week around them. That is the point of a primary pair (or in our case, a primary set for a team): the planning goes into a few places, and the rest gets what is left.

Here is what the same announcement looks like on two of our networks, for a release that added GIF support to the composer:

X:
You can now add GIFs to posts in the composer.
Pick one, preview it per network, schedule it like any image.
Small change, asked for a lot. Changelog ->
LinkedIn:
A small release: GIFs now work in the composer, with the
same per-network preview as images and video.

Why small things like this matter to a team: the post you
planned should not need a second tool just because it has
a GIF in it. Requests like this one come in through our
public feature requests board, and we read them.

Same fact, different reader. X gets the short "what changed". LinkedIn gets a line about why, because its readers care about how a team decides what to build.

Time budget

Picking networks should take one sitting, not a month of research:

StepTime
Search your problem words on four candidate networks15 minutes
Fill in the table for your audience5 minutes
Apply the decision rule, pick your pair5 minutes
Read the rules of two communities you plan to join10 minutes

Recap

  • Two networks you keep beat seven you abandon. Pick one for reach and one for depth.
  • Choose by where your audience asks for help and shares work, measured by real conversations.
  • Reddit and other communities reward members, not marketers: read the rules, give first, disclose.
  • The same news needs a different shape for each network's reader.

Exercise

Draft a post that reads like a member

  1. Pick the community on your depth network where your audience talks (a subreddit, a dev.to tag, a forum). Read its rules and the top posts of the last month.
  2. Open the free Reddit caption generator and describe your project and what you learned building it.
  3. Take the draft and rewrite it so it leads with the problem and what you learned, not the product. Move the link to the end and add "I built this" plainly.
  4. Read it as a member of that community would. Remove anything that sounds like an ad: adjectives, exclamation marks, calls to "check it out".
  5. Write one sentence for each of your two chosen networks explaining why you picked it.
  6. Done looks like: a community-ready draft you would not be embarrassed to see removed by a moderator (because it would not be), plus your two networks written down with a reason each.

Go further

Connect your two networks in FoPost

When your pair is chosen, connect both accounts in FoPost so you can write once and see each network's version side by side. Go to channels, connect your two accounts, then open the composer and draft your first post for both. See cross-posting for how per-network versions work.

Check yourself

  1. 1Why pick one reach network and one depth network?

    Reach networks bring frequent, discoverable updates; depth networks hold longer pieces that last. Together they cover both without spreading you thin.

  2. 2How do you measure where your audience talks?

    Search for the problem in their words on each network and count real recent conversations, not followers or hashtags.

  3. 3What is the most common reason a developer's Reddit post gets removed?

    It breaks the community's self-promotion norms, usually by being a bare link from an account that has not taken part in the community.

Academy

Keep reading, free

Tell us a little about you and the rest of this lesson, and every lesson in every course, opens on this device. No account and no card.

What describes you best?
Where do you post today? Pick any that apply.
What do you want most right now?

We use your answers to suggest lessons and to improve the Academy. They are never shown publicly. Read our Privacy Policy.