ABOUTENGINEERING

I build systems by understanding what they actually need.

I'm a Backend Engineer specialized in C#/.NET. I care about understanding the problem, the system, and the context behind a technical decision before deciding how to implement it.

01WHO I AM

A backend engineer who likes to understand the whole system.

My main experience is in backend development, particularly with C# and .NET. Over time, my work has taken me beyond implementing individual features and into architecture, data, distributed systems, performance, and the evolution of existing software.

I enjoy working on problems where the answer is not immediately obvious. Understanding how a system works, why a decision was made, what constraints exist, and what could happen next is part of the work I find most valuable.

I can work with technologies beyond my main stack when the problem requires it. I don't expect every system to use the technology I already know best; I care more about understanding the problem well enough to make a sound technical decision.

02HOW I THINK

I try to solve the right problem, not just the requested one.

A technical requirement is usually only part of the problem. Before implementing it, I want to understand the context around it.

Understand the context

What is the system trying to achieve? Who depends on it? What already exists? Understanding these questions helps reveal constraints that are not always visible in the initial requirement.

Question the obvious solution

The first solution is not necessarily the best one. When there are meaningful alternatives, I prefer to understand their trade-offs before deciding how to proceed.

Keep complexity intentional

Complexity should solve a real problem. I prefer simple designs when they are enough, and introduce additional mechanisms only when the system actually needs them.

Think beyond the change

A solution should not only work today. I also consider how it will affect future changes, performance, maintenance, and the evolution of the system.

ENGINEERING PRINCIPLEUnderstand first. Decide deliberately. Build for what comes next.

03HOW I WORK

I prefer to understand, investigate, and then build.

My approach changes depending on the problem, but I usually follow a simple process: understand what exists, identify what actually needs to change, and make the smallest sound change that moves the system forward.

Understand

I first try to understand the system, the business context, the existing behavior, and the constraints around the problem.

Investigate

When something is unclear or broken, I trace the behavior through the relevant code, data, and interactions instead of assuming where the problem is.

Design

I consider the available options, their trade-offs, and how the change fits into the existing system before choosing an implementation.

Validate

After making a change, I verify that the original problem was actually solved and that the change did not introduce problems elsewhere.

ENGINEERING PRINCIPLE