BACKEND / IDENTITY / AZURE
I’m a software engineer working with .NET, identity and Microsoft Azure. I build backends, work on secure sign-in and automate deployments. I also care about what happens once the code is in production.
WHO’S BEHIND THE SIGNAL
Software engineer — .NET, identity and Microsoft Azure.
Edgarus is the name I publish my work under. My experience, roles and recommendations are on LinkedIn, and the code speaks for itself on GitHub.
Have a system to build or fix? The contact form at the bottom of this page reaches me directly.
PUBLIC WORK
A small selection of projects I maintain publicly. The repositories are the source of truth: inspect the code, issues and releases there.
FOUR SIGNALS / ONE SYSTEM
Most of my work connects these areas: backend development, access management and deployment. The homelab gives me room to explore the ideas I want to understand better.
I work on identity and access management (IAM and CIAM): signing users in, managing permissions and connecting applications. I use Microsoft Entra ID and External ID, OAuth 2.0 and OpenID Connect, with SSO and MFA where they fit.
I build backends in C# and ASP.NET Core: REST APIs, business logic and integrations with other systems. I care about code that the next person can understand, test and change without guessing how it works.
I work with Microsoft Azure, containers and CI/CD pipelines to make deployments repeatable. Infrastructure as Code keeps configuration in version control. Logs, metrics and traces help me understand what happens after a release.
My homelab is where I try things out: network configurations, security settings and automation. I can break something, find out why and try again. It is a personal learning space, not a hosting service.
QUALITY / BY DESIGN
TEST COVERAGE TARGET
~99%
A target, not a score to chase.
I aim for around 99% test coverage, but the percentage alone is not enough. I want tests to catch broken behaviour, including edge cases and errors. A test that stays green when the code is wrong is not doing its job.
~99% is a goal, not a current project measurement or a promise of zero defects.
I check business rules, calculations and edge cases in isolation.
I check how the API, database and sign-in flow work together.
I test key user journeys from start to finish, including what happens when something fails.
OPERATING PRINCIPLES
Before choosing a tool, I ask what needs to work, who will use it and who will maintain it.
I prefer changes that are easy to review and test. Smaller releases also make problems easier to trace.
Clear code, useful logs and documented decisions help the next person work on the system. That next person might be me.
OPEN CHANNEL / 2026
Prefer LinkedIn? Message me there ↗