Lesson 5 of 87 min read

Writing posts developers don't scroll past

Hooks 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.

In this lesson you will

  • Write a first line that carries the post without hype
  • Structure a short post so it reads in seconds
  • Choose between code screenshots and code blocks, and format per network

Developers tend to distrust "hooks". The word suggests clickbait: "You won't believe what happened when I…", "Stop doing X", "Here's the secret nobody tells you". Those lines work on some audiences and repel yours. So many developers overcorrect and write posts that start with "So, I've been working on a thing" and bury the interesting part in the fourth sentence.

There is a middle path. A good first line is not a trick. It is the most interesting true sentence in your post, moved to the top. This lesson covers how to find that sentence, how to structure the rest of a short post, and how to format it so each network shows it the way you intended.

The first line carries the post

In a feed, most people see your first line, maybe two, and decide in a moment whether to keep reading. Everything after that is only read by people the first line convinced. So the first line has one job: make the right reader stop.

The right reader is your audience from lesson 1, not everyone. A first line that makes a backend developer stop may bore a designer, and that is fine.

Here are first-line patterns that work for technical audiences without hype:

  • The result first. "Our test suite went from 11 minutes to 3. Here is the one change that did most of it."
  • The surprising fact. "Postgres was not the bottleneck. The ORM was making 40 queries per page."
  • The decision. "We removed our most-requested feature's settings page. Here's why."
  • The specific mistake. "I shipped a migration that locked our biggest table for six minutes."
  • The useful claim. "You can debug most webhook failures with three curl commands."
  • The plain announcement. "You can now schedule posts from your CI pipeline." For release news, plain is often best.

All of these are true statements with specifics. None of them withholds the point to force a click. That is the line between a hook and clickbait: a hook gives the reader something, clickbait only promises it.

(Those examples are illustrations, not our numbers. When you write your own, use figures you measured.)

Rewrite the first line, before and after

The fastest way to improve a post is to find its best sentence and move it up. Here are three rewrites.

Before:
Hey everyone! Been a busy few weeks. I've been working on
improving the performance of the sync engine and I'm really
happy with how it turned out. Sync is now much faster.

After:
Sync now sends only what changed, not the whole file.
On a large config, that's a few kilobytes instead of the
full upload. Here's how the diffing works:
Before:
Excited to announce that version 2.0 is finally here after
months of hard work! Lots of new features and improvements.

After:
v2.0: you can roll back any migration with one command,
including the ones that drop columns. Upgrade notes below.
Before:
Some thoughts on testing.

After:
We deleted 30% of our tests last month. Coverage went down.
Bugs in production didn't go up. Here's what we cut and why.

The "after" versions share a pattern: they start with the most specific true thing, drop greetings and excitement words, and make clear what the rest of the post will give you. (These are hypothetical projects; use your own facts.)

A checklist for the first line:

  • Could someone in your audience act on or learn from this line alone?
  • Is there a number, a name of a tool, or a concrete before/after in it?
  • Did you delete "excited", "thrilled", "finally", "amazing", "powerful"?
  • Does it avoid withholding the point ("you won't believe…")?

Structure the rest

After the first line, a short post needs a shape that reads in seconds. For most technical posts this one works:

  1. First line: the point.
  2. Context: one or two sentences on why it matters or what the old situation was.
  3. Detail: the specific how, as a short list or two short paragraphs.
  4. Close: a link, a question, or nothing. Not "let me know your thoughts!" by default; ask a real question only when you want real answers.

Keep paragraphs to one to three lines. On a phone, a five-line paragraph looks like a wall. Use line breaks generously, but not every sentence on its own line; that reads as a gimmick.

Lists help when you have three or more parallel items. Use plain hyphens; they work everywhere. Do not overuse bold or italic. Some networks have no text formatting at all, and the "bold" you see in feeds is made with special Unicode characters that screen readers can read out oddly or skip. Use it sparingly, if at all, and never for whole sentences.

Before you schedule, do a sixty-second last pass:

  • Read it out loud. Anything you would not say to a colleague, cut.
  • Delete the first sentence and see if the post gets better. Often it does.
  • Check every number has a source you could point to.
  • Check every link works and goes where the post says it goes.

Code in posts: screenshot or text?

Developers want to show code. Where it goes depends on the network and the size of the snippet.

SituationUse
Up to about one line, like a command or a flagInline text in the post, so it can be copied
A few lines on X, Bluesky or LinkedInA clean, cropped screenshot with large font, plus the text in a reply, the alt text or a link
Anything longerA link to a gist, the docs or a blog post, with a screenshot of the key lines
dev.to, Hashnode or your blogA real fenced code block; these platforms render Markdown

Screenshot rules: use a large font, a theme with good contrast, and crop to the lines that matter. Remove anything secret (tokens, internal hostnames, real user data). Add alt text that describes what the code does, so people using screen readers get the point too.

Format per network

The same text does not look the same everywhere. A few differences to plan for:

  • X has a tight character limit on standard posts. Long posts become threads (lesson 3). Line breaks show as written.
  • LinkedIn shows only the first lines before a "see more" cut. Your first line matters even more there. It keeps line breaks, but extra blank lines can collapse depending on how the text was pasted.
  • Bluesky has its own length limit and handles links as cards. Keep posts short and self-contained.

The practical approach: write the core version once, then adjust per network. Shorten for X, add a "why it matters" line for LinkedIn, trim for Bluesky. Formatting tools help you see the result before you post, so you are not fixing it after it went live.

Worked example: how we write our own first lines

We apply the same rules to our own posts. Here is a real kind of case: announcing a release that added a hook library, a set of opening-line patterns you can start a post from, under templates. The irony of announcing a hook library to people who hate hooks was not lost on us, so the post had to follow its own advice.

A first draft in the usual announcement style would start like this:

New: the hook library! A big collection of proven hooks
to make your posts stand out and grab attention.

It fails the checklist: "proven" is a claim we cannot back, "stand out" and "grab attention" say nothing, and the exclamation mark adds noise. The rewrite:

X:
A first line is the only line most people read.
The new hook library under templates gives you opening
patterns per network. Pick one, it opens in the composer
with the opening filled in, and you write the rest.
LinkedIn:
Most posts fail in the first line, not the last.

We added a hook library under templates: opening-line
patterns grouped by network. Pick one and it opens in
the composer as your first line. The rest is still yours
to write, with your own facts.

The rewrite leads with a true, useful observation, says exactly what the feature does in one sentence, and makes no promises about results. The LinkedIn version keeps a short first line so it survives the "see more" cut.

Recap

  • The first line is the most interesting true sentence in your post, moved to the top.
  • Hooks give the reader something; clickbait only promises it. Write hooks.
  • Structure short posts as point, context, detail, close, in short paragraphs.
  • Code: inline for one line, screenshot plus copyable text for a few, a link for more.
  • Write once, then adjust length and emphasis per network before posting.

Exercise

Format one post for two networks

  1. Pick a post you wrote for lessons 3 or 4, or write a new one about something you did this week.
  2. Find the most interesting true sentence in it and move it to the first line. Run it through the first-line checklist.
  3. Restructure the rest as point, context, detail, close, with paragraphs of one to three lines.
  4. Paste it into the free LinkedIn post formatter and adjust until the first lines work above the "see more" cut.
  5. Paste the same post into the free X post formatter and shorten it to fit, or split it into a short thread.
  6. Done looks like: two versions of one post, each formatted for its network, with the same first idea and no hype words.

Go further

Per-network previews in the FoPost composer

In the FoPost composer you write the post once and see a preview for each connected network side by side, then edit any one network's version without touching the others. Open the composer, pick your two accounts, paste your post and adjust each preview until it reads right. See the composer page for how overrides work.

Check yourself

  1. 1What separates a hook from clickbait?

    A hook gives the reader the point or something useful in the first line; clickbait withholds it to force a click.

  2. 2When should code go in a screenshot instead of text?

    For a few lines on networks without code formatting, as a clean cropped image, always with the copyable text in a reply, alt text or link.

  3. 3Why does the first line matter even more on LinkedIn?

    LinkedIn shows only the opening lines before a "see more" cut, so the first line decides whether anyone expands the post.

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.