Start here25 essays in. Here is the map.
I'm Bartosz Frąckowiak — solution architect, currently leading an AI transformation across several hundred engineers. Every week I publish one field note about systems, the people around them, and the corporate machine they form together. This page is the shortest path to the good stuff.
Solution Architect in global SaaSPhD research, University of WarsawTop 3% on Toptal25 essays and counting
Then pick your door
Three threads run through all 25 essays. Each path below tells you exactly what it covers and where to start.
People problems, dressed as technical ones
Ownership gaps, decision rights, and the org chart hiding inside your architecture. For architects and tech leads who keep fixing the same "technical" issue that never was one.
Start reading- 01
Nobody Owns the SumEvery squad owns its piece. The customer buys the whole. Guess which one has no owner.5 min - 02
Decisions Have an Architecture TooWe design our systems obsessively, then let the decisions about them happen by loudest voice.5 min - 03
The Anti-Corruption Layer Is for People TooMy favorite pattern from Domain-Driven Design protects codebases from foreign models. I keep prescribing it to departments.5 min
Running AI adoption at real scale
Fifteen squads, several hundred developers, one transformation: the tech radar that drives it, the metrics that survive contact with reality, and the architecture practice that grew out of both.
Start reading- 01
From Signals to BlipsHow a tech radar became my favorite tool for driving an AI transformation across several hundred developers.5 min - 02
Probabilistic MetricsWhy the most useful numbers in our AI transformation were never in a database.5 min - 03
Prompt-Driven ArchitecturePart three of the "tools that scale" series: what happens when the daily practice of a Solution Architect starts running on AI.5 min
One person, three products, AI agents
Field reports from shipping my own products solo, with AI doing the typing: what actually changes, what breaks, and the receipts to prove it.
Start reading- 01
A Company of One, Staffed by AgentsFour shipping products, one person, and a field report on what AI actually changes about building software.5 min - 02
The Diagram That Cannot LieWhy I'm building an architecture modeling tool where the diagram is physically incapable of drifting from the code.5 min - 03
Edge Cases Written by ParliamentWhat integrating with mandatory government systems taught me about specs you cannot refactor.5 min
If this is the kind of thinking you want inside your organization — architecture consulting and AI training are what I do in daylight. Work with me →