The instinct, when you’re learning, is to hide until you’re good. Build in secret. Post only the polished thing. Never let anyone see the messy middle.

I get it. But the single best decision I made early on was the opposite: I learned out loud, where people could see me get it wrong.

Why hiding holds you back

When you only share finished, perfect work, a few things quietly cost you:

• You learn slower. Explaining something half-understood is how you find the holes in your understanding.
• You’re invisible. Nobody can offer you help, opportunities, or corrections for work they never see.
• You set an impossible bar. If you only ever show perfect things, every imperfect attempt feels like failure.

What “in public” actually means

It does not mean performing expertise you don’t have. It means leaving a trail:

1. Write the blog post explaining the thing you just learned, while you still remember being confused.
2. Push the rough project to a public repo with an honest README.
3. Ask the “dumb” question in the open. Someone else has it too.
4. Share the bug that took you all day, and what finally fixed it.

## Today I Learned
`Promise.all` rejects as soon as *one* promise rejects.
If you want all results regardless, you want `Promise.allSettled`.
Spent two hours on this. Writing it down so future-me doesn't.

That’s it. That tiny note will help a stranger, and it’ll help you more.

The compounding payoff

Here’s the part nobody tells you: the trail becomes an asset. Years of small public notes turn into a body of work. People find you through it. The “scary” part — being visibly imperfect — fades fast, and what’s left is a reputation built on showing up and being honest.

You don’t have to be the best in the room to teach what you learned yesterday to the person who’s one day behind you. Start there. Do it where people can see.