I’ve been building software for a long time. From VB6 to .NET, from monoliths to microservices, from on-premise to the cloud. Over the years I’ve seen many trends come and go. Most were noise. Some changed everything.
AI in software development is one of those moments.
Not the hype, but the practice
The internet is full of opinions about AI. Everyone has a hot take. But when I look for honest, practical stories from developers who use AI daily — not as a toy, but as an integral part of their workflow — I find remarkably little.
That’s exactly why I started this blog.
What I see every day
Since I started working with a full AI workflow, the way I build software has fundamentally changed:
- Bugs I used to fix in an hour now take twenty minutes — not because I type faster, but because I spend less time manually gathering context
- Refactoring is no longer a full-day task — AI reads the code, understands the structure, and makes the changes while I watch and steer
- Documentation writes itself — as a byproduct of the development process, not as a chore after the fact
- I make architecture decisions in dialogue — with a tool that knows my entire codebase and can build on it
- I deliver more in less time — not by working harder, but by collaborating smarter
This might sound like a sales pitch. I get that. But it’s simply what I experience every day.
What to expect here
On this blog I share those experiences. Honest, concrete, from practice. No abstract visions of the future, but stories about what it’s actually like when you seriously adopt AI in your development workflow.
Sometimes it’s about tools. Sometimes about approach. Sometimes about where things go wrong — because that happens too.
If you’re a developer wondering whether AI can truly make your work better: keep reading. I’ll show you.