Learning in Public

Learning in public is one of the most effective things you can do as a developer. When you write about what you're figuring out, you solidify your own understanding and leave a trail for the next person who hits the same wall.

Why it works

Writing forces clarity. If you can't explain it simply, you don't understand it well enough yet.

A small workflow example

Here's a tiny shell snippet I use to capture notes quickly:

#!/usr/bin/env bash
# til — Today I Learned
note="$*"
date=$(date +%Y-%m-%d)
echo "## $date\n\n$note" >> ~/til.md
echo "Saved: $note"

Call it with til "async params are a Promise in Next 15+" and you have a permanent record.

The compounding effect

Small posts compound. A note that takes 10 minutes to write can save someone else an hour. Do it consistently and you build a body of work that outlasts any single project.