Building great software that is pragmatic, not over-engineered, but is well-scalable when the need arises: That is what I love to do.

I started my professional developer career in 2004. But, as every good engineer does, my actual developer experience started way before that. At around the age 9 I started copying over a moonlander game on a ZX spectrum from a book. I tried to change some of the code, to change the game. I failed, but something was born: A passion to create things that work and look good.

Tech stacks and engineering vision

Starting from classic ASP, I have been working with the Microsoft stack for a long time. I have worked with .net MVC, .net core, Azure, CosmosDB, SQL server, MySql, Angular, Vue and React. From the beginning I have valued pragmatic solutions over over-engineered solutions. That does not mean I love good architectured software. I strive to look for frameworks that provide an opionated set of defaults and tools that can be easily extended when needed. I see this in frameworks like Vue, .net core and Astro for example.

Vision of engineering management

I believe that every engineer is a professional. They know what they are doing and they know how to do it. I will not mingle in day-to-day decisions, or how to code. I do want to support engineers to do their job the best way they can. By providing things they need. By coaching them in soft-skills. By making sure there is a clear vision of the product we are building.