Starting to Write in Public
A short introduction to who I am, why I’m starting this blog, and what I’ll be sharing from my adventures of building software.
Who am I and why am I writing here?
I’ve never really been good at writing.
Honestly, anything longer than a work email or a quick message has always felt a bit unnatural to me.
At work, I write a lot. Documentation, solution proposals, RfCs — but that kind of writing is structured, expected and… safe.
This is something different.
For a long time, I’ve mostly been a consumer.
- Reading dev logs
- Following people on Twitter/X
- Learning quietly from others sharing their work
People like Theo, Primeagen and many others have been part of my daily scroll for years.
But I’ve never really contributed anything myself.
I want to change that.
This blog is my attempt to move from passive → active.
- To start sharing instead of just consuming
- To document what I’m learning
- To capture what I’m building
- To be honest about what I’m struggling with along the way
A bit about me
I’m a software engineer working in consulting, which means I spend a lot of time:
- Solving real-world problems
- Writing code
- Thinking about systems, architecture, and trade-offs
But beyond that, I’m also just a person trying to get better at:
- Coding
- Creating
- And now… writing
What this blog is (and isn’t)
This won’t be a polished, corporate-style blog.
I will try to keep it:
- Personal
- Sometimes messy
- Sometimes overly technical
- Sometimes not technical at all
The goal
The goal is simple:
Share when I find or think about something interesting.
And see where it goes.
