I like systems that are easy to explain, hard to misuse and boring to operate.
Professionally I lead delivery. Here I build the products, tools and infrastructure myself.
|
|
|
|
|
|
|
|
|
Click a card for the engineering showcase. Private-source projects expose architecture and product boundaries without publishing production internals.
| Domain clarity Different facts stay different. Estimate is not commitment; forecast is not baseline; unknown is not zero. |
Clear boundaries Clients stay thin. Services own behaviour. Trust, data and runtime ownership are explicit. |
Boring operations Health, migrations, backups, logs and failure modes should be visible and repeatable. |
Automation first If the same boring work happens twice, it is probably trying to become code. |
| Languages / runtimes C# / .NET · Python · TypeScript · Node.js · Lua |
Data / backend PostgreSQL · SQLite · D1 · REST / OpenAPI · webhooks |
UI / delivery Avalonia · React · Next.js · WebAssembly · Telegram Mini Apps |
Infrastructure Docker · Linux · Cloudflare · GitHub Actions · packaging / release automation |
Build things. Ship things. Make the boring parts disappear.



