Hello, world: why I'm starting to write in public
A short note on what this blog is for, and what to expect from it.
Every engineer I respect has a habit of writing things down. Not just design docs and postmortems, but the half-formed ideas in between: why a system turned out the way it did, what a trend actually means, and where the conventional wisdom is wrong.
This blog is my attempt to build that habit in public.
What I’ll write about
- Engineering practice: architecture, tooling, and the trade-offs behind them.
- The industry: how teams, companies, and technologies are changing.
- Lessons learned: things I got wrong, so you don’t have to.
A small example
Posts support code with syntax highlighting in both light and dark mode:
export function readingMinutes(body: string): number {
const words = body.split(/\s+/).filter(Boolean).length;
return Math.max(1, Math.round(words / 230));
}
The best way to find out whether you understand something is to try to explain it.
If something here resonates or you think I’m wrong, leave a comment below. I read every one.
Discussion