Contact

my name is

Alessandro

Makes things
Breaks things first
Builder

Fullstack developer · Tech lead · CTO @ Matcha

I build things (with AI)*

that work without you

to do:

Done: Launch Matcha, the dating app

the next one

sleep

hi again

About

I’m the person clients call when they want to know if AI can really do what they saw in a demo. Then I make it work for real.

I started in 2019 as a freelance developer. Then I helped grow a team from 3 engineers to 18: hiring, reviews, mentoring and a lot of opinions about pull requests. Turns out the hard part is never the code. It’s the rules.

I have more ideas than hours, so I build with coding agents every day, at work and on the side projects that keep stealing my evenings. Matcha is my current project.

stuff I've built!

Case studies

2026

Matcha

A dating app for Milan that turns every match into a real date. I'm the co-founder and CTO: the database decides who has paid, and agents ship most of the code.

View project Matcha
  • Agentic engineering
  • Product launch

2025

Oh It's That Guy

A movie quiz I shipped in a week. Later I sent agents to audit it and found out what the speed had cost.

View project Oh It's That Guy
  • Serverless on AWS
  • Game design

2026

AI Training Program

Generative AI training for client teams, and the rollout of coding agents across my own engineering team at BID Company. Sometimes a training session even turns into a product.

View project AI Training Program
  • AI adoption
  • Team training

issues in, pull requests out

How I ship

Engineers and coding agents work from the same board. Every issue carries an autonomy label that says how far an agent can go without a person.

Todo2

  • Show free evenings on the profile

    autonomy:auto

  • Refund a cancelled date

    autonomy:supervised

In progress1

  • Read receipts in chat

    autonomy:auto

    agent on it

Needs human1

  • New status for paid matches

    autonomy:supervised

    plan posted, waiting for “Approved”

Done1

  • Fix time zones in booking

    autonomy:auto

    reviewed · CI green · merged

  1. 1

    The board comes first. A new project starts with its kanban board, so agents can pick up issues from day one.

  2. 2

    Autonomy belongs to the issue. Logins, payments, database changes and anything a revert can't undo stay supervised. Everything else runs on auto.

  3. 3

    People own the rules. Agents merge routine work on their own. People decide what counts as routine, and step in on everything critical.

tools I use[ daily ]

Me in Iceland

me, somewhere in Iceland

say hi

Contact

Building something and need an extra pair of hands? Architecture, AI, or a team that's growing faster than its rules.

The northern lights over Iceland

stayed up for this one