Building in Public
Why I decided to start writing about the things I build, learn, and struggle with as a software developer.
Building in Public
For a long time, I've had folders full of unfinished ideas, side projects, notes, screenshots, and snippets of code. Some turned into working products. Most didn't.
What they all had in common was that they taught me something.
I've spent years learning software development through tutorials, documentation, open-source projects, work, and countless hours of trial and error. Along the way, I realized that a lot of what we learn never gets shared. We solve a problem, move on to the next one, and eventually forget how we got there.
That's one of the reasons I started this blog.
The Reality of Learning Tech
From the outside, software development often looks like a straight path. Learn a language, build projects, get a job, and keep progressing.
The reality is much messier.
There are days when everything works perfectly, and there are days when a missing semicolon or a misconfigured environment can consume hours. There are projects you're proud of and projects that make you wonder what you were thinking when you wrote the code.
Every developer has those moments.
This blog isn't about pretending to have all the answers. It's about documenting the process of finding them.
What I'm Working On
Most of my time is spent building software, learning new technologies, and exploring ideas that seem interesting.
Some of the topics you'll find here include:
- Backend development
- Artificial Intelligence and automation
- System design and architecture
- Developer tools and workflows
- Side projects
- Career lessons and experiences
- Things that fail and what they taught me
Not every post will be a technical tutorial. Some will simply be observations from the journey.
Why Write?
Because writing forces clarity.
It's easy to think you understand something. It's much harder to explain it in a way that someone else can understand.
Writing helps me organize ideas, document lessons, and create a record of progress over time. Years from now, I want to be able to look back and see how far I've come—not just through completed projects, but through the things I learned along the way.
A Small Promise
I'll try to keep these posts honest.
Not just the wins, but also the mistakes, wrong assumptions, failed experiments, and lessons learned from them.
If you're a developer, builder, student, or simply someone curious about technology, I hope you'll find something useful here.
This is the beginning of the journey.
Let's see where it goes.