Why I Built Yet Another Engineering Blog
There are already enough programming blogs. I didn't build this one to teach frameworks—I built it to document the real engineering decisions behind the products I ship.
A few days ago I was explaining one of my projects to a potential client.
I shared the GitHub repository.
Then I realized something.
The code showed how I built it.
It didn't explain why.
Why I chose one architecture over another.
Why I threw away an approach after two hours.
Why a tiny implementation detail ended up making the biggest difference.
That's what this blog is for.
There Are Already Enough Tutorials
The internet doesn't need another React tutorial.
Or another article comparing AI models.
Or another "Top 10 VS Code Extensions" list.
People are already doing a great job writing those.
I'd rather write about things that happen while building actual products.
The bugs.
The trade-offs.
The decisions.
The mistakes.
Most Articles Start With Real Work
I build software almost every day.
Some days it's an AI feature.
Some days it's a new SaaS idea.
Sometimes it's an external client project.
Sometimes it's just fixing something that annoyed me for weeks.
Whenever I run into an interesting problem, I'll probably write about it here.
Not because I think I've found the perfect solution.
Mostly because future me will probably forget why I solved it that way.
AI Changed How I Work
AI is part of my workflow now.
Claude writes code with me.
Cursor helps me move faster.
ChatGPT is often the first place I explore ideas.
They're incredibly useful.
But they still don't decide what gets built.
Good software is mostly about making decisions.
Choosing the right trade-offs.
Keeping things simple.
Knowing when not to use AI.
That's the interesting part.
Why I Keep It Short
I'm not trying to write books.
If I learn something useful, I'd rather publish it while it's still fresh.
Some posts will take three minutes to read.
Some will be longer case studies.
Either way, I'd rather publish consistently than disappear for three months waiting for the "perfect" article.
What You'll Find Here
Most posts will fall into a few topics:
- AI Engineering
- Full Stack Development
- Product Engineering
- Developer Workflows
- Building SaaS Products
- Lessons from client projects
Everything comes from real work.
No rewritten documentation.
No clickbait.
No articles written just because a keyword is trending.
If something worked, I'll explain why.
If it failed, I'll explain that too.
Hopefully a few years from now this becomes more than a blog.
It becomes a record of everything I built—and everything I learned along the way.
Thanks for stopping by.
