Does writing one LinkedIn post feel like you’re trying to write a damn book?
You start with one idea. Then you realize you need to explain some background. Which reminds you of another point. But that point needs context.
If you have kids and are now thinking of “If You Give a Mouse a Cookie,” you would be right.
And now your quick post has seven sections, will take two hours to write, and you’re reconsidering whether you wanted to post anything in the first place.
Stop making movies
Developers approach content like they’re making a film. Setup. Character development. Plot. Resolution.
Approach it that way while trying to post consistently and suddenly you’re thinking about trilogies. Prequels. Sequels.
That is one of the quickest ways to talk yourself out of ever starting.
Make sitcoms instead
I’ll date myself here, but think of an episode of Friends.
Sure, there are general underlying themes, relationships, history. But an episode is generally just an episode.
Joey gets locked in a cabinet trying to make a sale. Rachel convinces Ross’s date to shave her head. Robin Williams and Billy Crystal randomly crash Central Perk in a scene that was completely unscripted.
Small, focused ideas shared quickly, while still maintaining the underlying thread.
As a developer, your content can work the same way.
Don’t write “Everything I Know About Azure Service Bus.” Write about the time you realized a queue was the wrong choice.
Don’t explain Clean Architecture. Explain one boundary you think developers routinely get wrong.
Don’t write your complete philosophy on becoming a senior developer. Tell me one thing you understand today that you didn’t understand five years ago.
Tomorrow? Another episode.
The larger story tells itself
Over time, people start understanding:
- What you know
- How you think
- What you care about
- What kinds of problems you’re good at solving
You don’t have to tell your whole story in every post. Just give me one good episode.