Developers & indie hackers

Ship in Public

How developers and indie hackers turn what they build into an audience, one release at a time

Find your course

A few quick questions so we can suggest where to start.

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.

Lessons
8
Time
4 weeks, about an hour a week
Format
Text lessons with exercises
Price
Free

Lessons

  1. Why developers lose at distribution (and how to stop)Distribution is part of shipping. Pick one audience, write a one-line positioning, and use your technical detail as the edge marketers lack.7 min read
  2. Pick two networks, not all of themChoose networks by where your users already talk. A plain guide to X, Bluesky, LinkedIn, Reddit, dev.to, Hashnode and YouTube for builders.7 min read
  3. The release is the postTurn every release into posts without extra writing. Translate changelog lines into user benefits, one change per post, with a screenshot or clip.7 min read
  4. Building in public without oversharingKnow what to share (numbers, decisions, mistakes, lessons) and what to keep private, and build a four-post weekly rhythm you can sustain.7 min read
  5. Writing posts developers don't scroll pastHooks for people who hate hooks. Make the first line carry the post, structure the rest, and format code and text so each network shows it well.7 min read
  6. Long form once, short form everywhereRepurpose one blog post or README into a thread, a LinkedIn post, a Bluesky post and a dev.to or Hashnode cross-post with the right canonical URL.7 min read
  7. Automate the boring part with codePost from your own stack. Create drafts from CI on every release, let your coding agent draft the week, and approve everything before it goes live.7 min read
  8. Measure, listen, and find your first usersRead your own numbers, tag your links, and find the conversations where people already ask for what you built. Your first users are in other threads.7 min read

About this course

Most developers we talk to have the same problem. The code is good, the release went out, and almost nobody noticed. Writing about it feels like a second job, and the advice online is written for marketers with a content team. This course is for the person who has neither the team nor the patience for hype.

We built it around one idea: the work you already do is the content. A release note, a bug you fixed, a decision you made about your schema, a feature you cut to ship on time. Each of those is a post, and with a little structure it takes minutes, not evenings. We use our own product as the running example, so you see the real process: how a changelog entry becomes an X thread, how we choose what to share, and what we keep private.

There are eight lessons. Each one teaches one part of the job, shows a worked example from our own accounts and changelog, and ends with an exercise you can finish with a free tool and no account. Each lesson also has an optional step inside FoPost for when you want the same task done faster or on a schedule. You never need to sign up to follow the course.

Plan on about an hour a week for four weeks, two lessons a week. You need something you are building (or about to build), a place to write drafts, and accounts on the two networks you pick in lesson 2. If you would rather post from code, lesson 7 shows how to do it from your own scripts and CI, with nothing going live until you approve it.