About

How It Started

My fascination with computers started with an Amiga 500. Like many kids of that era, I spent countless hours playing games, replacing broken joysticks and trying to understand how these machines actually worked.

When personal computers became more common, my curiosity shifted from using technology to understanding it. My first experience with the Internet came through a 56k dial-up modem. For a teenager growing up in Poland, it felt like the world suddenly became much larger.

IRC chats with people from other continents, online communities and the early days of digital content created a fascination with technology that eventually became a career.

Chasing An Old Question

During my studies in Software Engineering, I became fascinated by a question that still influences how I think today:

Can people create software without becoming programmers?

Inspired by Adobe Flash and Lego Mindstorms, I created VisMode as my Master's thesis. The idea was to allow people to design business processes visually and generate applications without writing code.

Seventeen years later, AI, no-code and low-code platforms are exploring many of the same ideas. The technology changed. The problem remained surprisingly similar.

Building Products And Companies

After university I worked on products and platforms across multiple industries, including video streaming, analytics, healthcare, enterprise systems and subscription businesses.

Later I co-founded software companies and worked closely with startups. For the first time I was no longer responsible only for technology. I had to think about customers, budgets, hiring, sales and product-market fit.

That experience changed how I look at software development. Building software is important. Building the right software is far more important.

Bridging Business And Technology

Throughout my career I worked as a developer, Scrum Master, Product Owner, CTO, founder, Tech Lead and Architect.

What changed from role to role was the perspective. What remained surprisingly constant was the challenge.

Business and technology often want the same outcome, but they speak different languages. Much of my work has been helping those worlds understand each other and make better decisions together.

Most software problems are not technology problems. They are communication problems.

What I Believe

Over the years I became increasingly convinced that technology should serve business goals, not the other way around.

Architecture is ultimately about understanding constraints. Simplicity scales better than complexity, and the fastest way to solve a difficult problem is often to challenge the assumptions behind it.

Technology changes faster than business problems.

Customers are usually better at describing problems than designing solutions. Perfection kills progress. And the best architecture is not the most sophisticated one - it is the one that solves the problem within the available time, budget and constraints.

Today

Today I focus on architecture, product development and technology leadership.

I enjoy helping organizations simplify complexity, modernize systems and build products that create measurable business value.

This website is a collection of stories, lessons and ideas gathered throughout that journey.