This is a new beginning.
I recently redesigned my portfolio around a simple idea: make less room for noise, and more room for the work, the thinking, and the learning behind it.
I am currently studying AI Native Development part-time at Technigo. At the same time, I am reading The Pragmatic Programmer—a book first published long before today’s AI tools, but still remarkably relevant. I have also just started a new assignment at Coop Sverige, where the way of working is deeply rooted in specifications and AI-assisted development.
These three things have made me think about what it means to be a developer right now.
AI changes the speed, not the responsibility
AI can help us explore ideas, generate code, review decisions, and move from an idea to a working prototype faster than ever.
But faster implementation does not automatically mean better software.
The real work is still understanding the problem. It is being able to describe what should happen, for whom, under which constraints, and why it matters. A vague request will still produce vague results—even when an AI is doing part of the implementation.
That is why I find spec-driven development so interesting. A good specification is not bureaucracy. It is a way to make thinking visible. It creates a shared understanding before the code exists, and gives both people and AI a clearer foundation to build from.
Returning to first principles
Reading The Pragmatic Programmer alongside learning AI-native development has been a useful reminder that good engineering habits do not disappear when new tools arrive.
Taking ownership. Communicating clearly. Staying curious. Improving a little at a time. Thinking about maintainability—not only whether something works today.
AI changes the tools available to us, but it also raises the bar for clarity. If we can delegate more of the mechanical work, we have fewer excuses not to focus on the decisions that require judgment.
For me, that is the exciting part.
What I want to explore here
This site is not only a collection of finished projects. I want it to be a place to share the process behind them: the experiments, the things that worked, the things that did not, and the lessons worth keeping.
Over time, I want it to grow beyond a portfolio into a collection of essays, working notes, useful snippets, and resources I want to return to.
I will write about AI-native development, product thinking, software craftsmanship, design, and the practical reality of building things in a changing industry.
I do not have all the answers yet. But I am convinced that the best way forward is to keep building, keep reflecting, and keep improving the way we think—not just the way we code.
This is the first post. More to come.