· method· team
Kanban without limits is just a list with columns
Teams adopt the ceremonies quickly and almost never the constraint that makes them work. What changes when you limit work in progress.
Read more →
Software Architect & Development Lead
MatteoFabrizi
I turn ideas into digital solutions that create value and help people grow.
I design software architectures that last, and lead the teams that build them.
01 /
How I work
01
Strategy and vision
Before writing code I define the problem. I translate business goals into explicit architectural choices, with constraints and trade-offs written down, so that every decision still makes sense years later.
02
Innovation and impact
Technology matters for what it changes. I choose tools to fit the problem rather than the trend, and judge the outcome by how much easier a system becomes to evolve for whoever inherits it.
03
Leadership and collaboration
An architecture lives through the people who maintain it. As a technical lead I own the decisions, distribute work along real priorities, and give the team the context it needs to decide on its own.
02 /
Work
Software I designed and took all the way to public distribution. The code and the artefacts are verifiable by anyone.
An Android application published on the store and two open source libraries distributed on the official Java and npm registries. The rest of my work is on company systems covered by confidentiality: what you find here is the part you can open and check yourself.
All projects