Learn in public

Most developers learn in secret. They absorb content, solve problems, improve — and don’t talk about it with anyone. The logic behind this is: “when I’m good enough, then I’ll start sharing.”

The problem is that this day rarely comes.

From consumer to creator

The internet is full of people who only consume content. And there’s nothing wrong with that — everyone starts that way. But if you want to accelerate your career, it’s worth making this transition:

Consumer → Creator

This doesn’t mean becoming a YouTuber or writing academic papers. It means documenting what you’re learning as you learn. A post about a bug you fixed. A repository with examples you created to understand a concept. A Twitter thread explaining something that confused you last week.

The goal isn’t to teach like a master. It’s to document the journey.

Luck surface area

There’s a concept called Luck Surface Area — something like “the surface area of luck”:

Luck = What you do × How many people know about it

When you learn in public, opportunities start finding you — jobs, invitations, partnerships — instead of you having to hunt them down. The more you share, the larger that surface becomes.

Documentation for your future self

There’s a practical and immediate benefit that sometimes goes unnoticed: you’re creating a knowledge repository for yourself.

Six months from now, when you forget how you solved that authentication problem or configured that environment, you’ll be grateful you wrote about it. The post that seems too simple to publish today might be exactly what you’ll need tomorrow.

The expert myth

You don’t need to be the world’s biggest expert on a subject to talk about it. In fact, someone who just learned something often explains it better than someone who’s known it for years — because they still remember how hard it is to understand the basics.

Someone who has already mastered a subject tends to skip steps without noticing. Someone who just learned it still remembers every obstacle along the way.

Where to start

• Write about a problem you solved this week
• Share a repository you created to study
• Explain a concept that took you time to understand
• Document a setup that took a while to get working

Nothing needs to be perfect. The criterion is simple: was this useful to me? If so, it’ll probably be useful to someone who’s at the same point you were.