About me
Software engineer in Sibiu, Romania. 4+ years building cloud accounting products for the Nordic market, and a standing habit of rebuilding things myself to find out how they actually work.
My degrees are in computer science and electrical engineering, and the work I do for myself sits where they meet: compilers, an 8086 emulator, the gap between a line of source and a register changing value.
Away from the keyboard
Sibiu, Romaniaopen to remote work
By day: 4+ years of .NET, Angular, React and Azure on cloud accounting products for the Nordic market. The four projects below nobody ordered. I built them to find out how a compiler reads code, and what a processor does between two instructions.
The work
Not code samples: a compiler with an emulator, a full web application, a desktop CPU simulator and this site, each building clean with its own test suite.
A browser IDE that compiles nine languages down to 8086 assembly, then runs the result on an emulator you can single-step.
Compilation runs on the server, where each language is checked by its own toolchain. Execution runs in your browser, one instruction at a time, with registers, flags, stack and memory on screen.
Project and issue tracking with a Kanban board, epics, time tracking, reporting and real-time notifications, on .NET 10 and Angular 22.
A CQRS backend where controllers only dispatch, a domain that refuses silent overwrites, and a board that updates live over SignalR.
A desktop CPU simulator that assembles a 47-instruction set and executes it one microcode step at a time, with the datapath drawn and lit as it goes.
A .NET MAUI app whose simulator core knows nothing about the screen. It reports what each microcode step touched, and the schematic decides how to light it.
The site you are reading, prerendered to static HTML in English, German and Romanian, with a first-party analytics API that hears only from readers who consent.
Every address is a real file in its own language, so a crawler, a reader without scripting and a deep link all get the page itself. Angular then hydrates the markup it was sent instead of drawing it again.
How I think
Held loosely enough to argue about, firmly enough that they show in how I work.
The part of a system that holds the rules should not depend on what surrounds it. Then changing the screen or the storage never puts the rules at risk.
A passing suite tells me the logic works, not that the screen is usable. I answer the second question by looking.
I use AI tooling every day and it makes me faster. It has not lowered the bar a change has to clear before it ships.
About
For 4+ years I have built cloud accounting SaaS for the Nordic market: four .NET and Angular microservices talking over Azure Service Bus with Rebus sagas and CQRS, each with its own multi-tenant SQL Server.
Lately: moving a .NET Framework 4.8 monolith to .NET 8 piece by piece and its Knockout.js frontend to React 19, every step behind a feature flag.
I grew up between two languages and now work in three. I like real constraints, code someone can still read in a year, and finding out early when I am wrong.