Who is behind the console
I build the layer people never see, and feel every day.
- Software Engineer · Cloud & DevOps
I am a software engineer working on the unglamorous half of software: the systems that run a business every day and cannot be switched off while you improve them.
Curiosity is what pulls you into the endless space of technology, but discipline is what allows you to survive there. When you trace the hidden mechanisms of data far enough, you eventually hit the enterprise reality. You stop just looking for answers and start taking responsibility for systems that matter. For me, that transition happened in the trenches of mission-critical architecture.
At TSS Yonder, taking responsibility meant facing a five million line legacy monolith. It was a breathing, fragile system supporting hundreds of businesses, where one wrong move could halt operations across Western Europe. Maturing as an engineer meant learning how to untangle that knot while the system was still running. I led the charge to decompose that massive application into resilient cloud native microservices on AWS. The true victory was not just deploying modern React and .NET code. It was achieving the absolute silence of 23,000 daily transactions flowing flawlessly, with automated deployments that finally let everyone sleep at night.
While enterprise software taught me scale and stability, my innate curiosity still drives me to explore the edges of what code can do. Today, I gravitate toward domains that force me to be absolutely precise. Sometimes that precision looks like translating silent human intent into digital action by building a computer vision application that tracks iris movements to control a cursor. Other times, it means architecting an Ethereum voting system where double-voting is rendered mathematically impossible by the strict constraints of the smart contracts. I even apply this philosophy to physics, designing a Hamiltonian Neural Network that learns engine dynamics without hallucinating energy because the laws of thermodynamics are baked directly into the architecture itself.
Whether I am untangling millions of lines of corporate code or enforcing physics in machine learning, the core philosophy remains the same: replace hope with structural guarantees. On the evenings I want to sharpen that philosophy, I tutor candidates for the Babeș-Bolyai Computer Science admission exam. Taking my mind back to the raw fundamentals of algorithms, logic, and data structures is the most rigorous code review I have ever found. It reminds me that no matter how deep into the tech space you travel, everything still relies on that very first keystroke.
How I work
-
Structure before cleverness
Most bugs are design decisions arriving late. Get the boundaries right: domain, application, infrastructure, and the clever part usually turns out to be unnecessary.
-
If it is not automated, it is not done
A deploy that needs a person to remember something is an outage with a delay on it. Pipelines, migrations and releases belong in code, reviewed like code.
-
Prove it, do not promise it
Whether it is a Merkle proof on-chain or a conservation law in a loss function, I would rather make correctness structural than hope it holds at runtime.
-
Explaining is the real test
Three years of tutoring taught me that if I cannot walk someone through a decision, I do not understand it well enough to defend it in a design review.
Instruments I've worked with
Languages
- C#
- C++
- C
- Java
- TypeScript
- Python
- SQL
- Solidity
- x86 Assembly
- Bash
Frameworks
- .NET / .NET Core
- ASP.NET Core
- EF Core
- Spring Boot
- React
- Node.js
- Avalonia UI
Cloud & Infra
- AWS ECS / Fargate
- AWS CDK (IaC)
- AWS EventBridge
- AWS SQS
- ECR
- S3
- RDS
- VPC
- Docker
- Kubernetes
- Azure DevOps CI/CD
Data
- SQL Server
- PostgreSQL
- Redis