Starting this blog
A short intro to why this blog exists, what I want to write about, and where to find me.
This is the first post on my blog.
Nothing too deep for now. I mostly wanted a place that I own. Somewhere inside my portfolio where I can write about what I am building, what I am learning, and the way I think about software, AI, tools, products, and just life.
A portfolio gives the short version. A blog gives a bit more context.
# Why this blog exists
I have always been close to computers, software, technology, and math. That interest got stronger during the pandemic, and then changed again when AI became more accessible.
Software started to feel less like only a career path and more like leverage. You can build tools. You can automate boring work. You can create systems that keep helping after you step away from the keyboard.
That is the kind of thing I want to write about here.
I want this blog to become a public trail of what I am learning and building.
It does not need to be perfect. It just needs to be useful, honest, and clear.
# What I plan to write about
I think this blog will be a mix of technical notes, product thoughts, and build logs.
Some topics will probably show up often:
- AI workflows and agents
- software engineering and developer tools
- building products with small teams
- RedaPro and lessons from shipping an AI education product
- code search, RAG systems, and automation
- mistakes, tradeoffs, and things I would do differently
The kind of writing I want here
| Type | What it means |
|---|---|
| Notes | Short explanations of something I learned or debugged. |
| Build logs | Practical posts about how a project changed over time. |
| Essays | Longer thoughts about technology, work, leverage, and software. |
I do not want every post to sound polished. Some posts can be small. Some can be rough. Some can be very technical.
If it captures something real, it belongs here.
# How I think about building
A lot of my work today comes back to leverage.
I like tools that adapt to my workflow instead of forcing me into a fixed way of working.
That is also how I see this blog.
It is not a content machine. It is an archive I can keep coming back to.
In practice, I will probably write about things while they are still fresh:
- what I was trying to build
- what constraints mattered
- what broke or changed
- what I learned from it
That is the kind of writing I like reading from other builders.
# Where to find me
If you are reading this and want to connect, the best places are:
Right now I am focused on software engineering, AI-assisted workflows, developer tools, and building something great.
More posts soon.