Why I'm building in public
And documenting the process
Welcome to the very first edition of Dev Notes.
Here’s a simple question I’ve been thinking a lot about lately:
Why build in public?
For me, there are two answers: accountability and connection.
I’m a software developer who spends a lot of time building things. Side projects, tinkering with ideas, exploring what’s possible with tech, I’m always doing something. But too often, those projects stay stuck in my local environment. Or worse, in my head.
By sharing what I’m building, what I’m learning, and even what I’m struggling with, I’m inviting others in. And that changes everything.
Accountability
When I know someone might be watching, or even just waiting for the next update, it lights a fire. It’s not about going viral or chasing recognition. It’s about showing up. Building in public turns an isolated process into something more structured, more consistent. It’s easier to quit when no one knows you started. This changes that.
Connection
The internet has a funny way of turning strangers into collaborators. By documenting my journey, I’m hoping to connect with other devs, makers, and curious people who are also building something. Maybe you’ll relate to something I build. Maybe you’ll have advice. Or maybe you’re just here to see if this thing turns into something real. Either way, I’m glad you’re here.
What to Expect
In Dev Notes, I’ll be sharing:
Behind-the-scenes updates on what I’m building
Lessons from projects, both technical and personal
Tools I’m experimenting with
Wins, fails, pivots, and ideas in progress
This newsletter isn’t polished. It’s not meant to be. It’s the notes you’d find in the margins of a dev’s notebook. Quick thoughts, real updates, and honest reflections from someone who’s building in public and documenting the process.
If that sounds like your kind of thing, stick around by clicking this button to get each new edition.
Jonny