As a Pixel Federation employee, I led the payment infrastructure team. We delivered the payment systems together.
Build systems.
Keep your
judgment.
I’m Tomáš Mihalicka, software architect and founder of Monadial. I work with distributed systems, Domain-Driven Design and AI-assisted engineering. Here I share my experience, projects and the ideas behind my work.
Distributed systems / Domain-Driven Design / Sane AI
How I work
Connected systems.
Considered decisions.
Good architecture connects business intent, clear domain boundaries and the people making decisions. Explore how I approach each layer.
Explicit boundaries, reliable messages, and systems your team can operate.
A few teams I’ve worked with
Experience,
in production.
Optimized 3D packaging algorithms and contributed to the direct-to-consumer (D2C) module as part of the development team.
Provided Domain-Driven Design consulting for the CRM domain and supported AI adoption.
Developed backend systems and provided consulting on Domain-Driven Design and distributed systems.
production systems
distributed platform
payment infrastructure
01 / What I do
Clarity at every
layer of the system.
Hands-on architecture, domain modeling, and practical AI adoption. From the first whiteboard to production.
01 / Architecture
Build for what
comes next.
Resilient distributed systems with explicit contracts, reliable messaging, and observability from the start.
Distributed systems02 / Domain-Driven Design
Make complexity
understandable.
Find the right boundaries. Build a shared language. Make the software reflect how the business actually works.
Domain modeling03 / AI-assisted engineering
Move faster.
Keep your judgment.
Practical guardrails, thoughtful reviews, and workflows that keep your engineers in control of what ships.
Sane AI adoptionAlso: modernization, architecture reviews, and team enablement.
Explore all expertise02 / Selected work
Ideas, made real.
Two current projects and three open-source projects, born from problems I couldn’t leave alone.
Human decisions. AI-written specs.
I’m working on Aktum, a beta product for decisions and sign-off around AI-written specifications. Open questions get named owners, with decisions committed to the repository as readable YAML.
Understand the code you ship.
I’m building a Rust CLI for understanding AI-assisted code and strengthening engineering judgment: reasoning about decisions, recognising trade-offs, and knowing what you ship.
Built with Rust and Ratatui; currently private. An open-source CLI release, deliberate practice, guided learning, knowledge retention and a future company portal are planned.
Concurrent PHP, done right.
Erlang/OTP and Akka patterns in the PHP you already know. Typed messages, supervision trees, event sourcing, and OpenTelemetry built in.
Also building Waygrid and ASH.
Explore all five projects
03 / The person behind the systems
Still curious.
Still asking why.
I’ve been taking systems apart since Turbo Pascal. Since then: banking, payments, gaming, and distributed platforms that make you care deeply about what happens at 3 a.m.
My approach starts with the domain, honest boundaries, and the people doing the work. Boring technology, chosen on purpose.
More about me04 / Field notes
Thinking out loud.
Essay / Software Architecture
When Expertise Puts You Behind
AI has made shipping easier. Experienced engineers can waste that advantage by building the architecture they admire instead of the product people asked for.
Read the essay