ResumeLet's talk

I'm Mattia Peiretti.

Entrepreneur, Engineer, Nerd, Espresso lover ☕️
But at the end of the day, I'm just a guy with a macbook

Engineer at day, Entrepreneur at night 🚀

12. Varese, Italy. Picture this. I was 12 years old and I got to play flipper on an old tower pc running ubuntu 8.10. That was my first introduction to this magic things we call computers.

I have always been a tinkerer, I have vague memories of when I was three and building my first circuit with my Father.

Well, you're not here to read my life's story, so I'll cut to the chase. I have always been a Nerd, so soon enough, after discovering programming. I started making all kinds of things.

Until I landed my first web development gig. After I moved to Amsterdam. Don't get me wrong, I still do all sorts of things with tech. But that is when I started focussing more on web development.

I also then discovered my passion for design 🎨

Web design, illustrations, infographics, you name it. I have done it. It wasn't my main focus, but I liked making pretty things.

But backend or system engineering, is what fills my days ⚙️

I like numbers, schemas, queues, system architecture. I like solving complex problems. Which is mostly done in backend engineering, so that is where I specialised.

I learned a lot about backend engineering and PHP, when I started working at TreeHouse, the company behind the biggest rental real estate market places in The Netherlands: Pararius and Huurwoningen

At TreeHouse, as well as with my agency, PhobosMedia, I learned a lot about project management and team management, SCRUM, DORA and so on. Which is where I came up with my engineering principles:



Deployment speed to be precise. A healthy engineering team can deploy multiple times a day with an automated CI/CD pipeline.



There needs to be trust in the team. Team members should be trusted and allowed to fail. We need to make team members feel heard.



Every piece of code is a model. You can choose to model your domain (business) properly or make a mess. Code is modelled around the business via DDD.



Purism makes progress slower at times. As engineers, we must put the business first. If we're validating an idea, we can start by making it work, and then making it pretty.



It's important for us engineers to seek to understand the business. We need to understand the use case deeply, and code it with the same terms that domain experts use.



There are always stakeholders. Be it the CEO, or the customers. We need to manage, listen and deeply understand our stakeholders, to do our job properly.

Being an entrepreneur is also pretty cool 🚀️

With code you solve problems, you create systems, and scale your solutions to achieve great impact. Does that sound familiar? To me it does. Entrepreneurship has the same points, just a bit less nerdy.

I think that is why I have always been entrepreneurial. It started with my first client, and it then evolved to all sorts of businesses on the web. Many of them failed, and many lessons were learned!

I learned the importance of having a long term vision, as well as having a concrete, plan of attack list, that can be achieved tomorrow. I learned how to work in a team and lead a team, how to make people feel heard, and to help them grow, and participate in the team.

Nowadays I'm mostly busy with these ventures:

Or see my full CV here