Build in Public — Best Practices

Philosophy

Build in public isn't marketing. It's letting people watch you work. The best posts feel like you're narrating your thought process to a friend who's also a senior engineer. No hype sludge. No "I'm excited to announce." Just: here's what I built, here's why it matters, here's what I learned.

What to Share (and What Not To)

Share:

• Technical decisions and the reasoning behind them ("Chose SQLite over Postgres because...")
• Architecture insights ("Here's how the 9-tier routing pipeline works")
• Failures and what you learned ("Spent 3 hours debugging a race condition. Root cause: ...")
• Before/after metrics ("Compaction death spirals: 26 → 0 after Mnemos")
• Open source releases with context, not just links
• Counter-intuitive findings that surprised you