ASP.NET Core and C# development

What we build

• REST APIs on ASP.NET Core and Azure Functions with an OpenAPI document that the front end is generated from, so the contract cannot drift.
• Background processing: scheduled jobs, queue-triggered workers and integrations with third-party APIs, each with retries, dead-lettering and alerts.
• Data on SQL Server and Azure SQL through EF Core migrations, with row-level security and Always Encrypted columns where the data is personal or financial.
• Integrations with Microsoft Graph, Teams, Telegram, Upwork, Hubstaff, bank and payment APIs, written as adapters so vendor SDK types stop at the boundary.

How we work on .NET

• Vertical slices with CQRS. One folder per feature, one handler per command or query, cross-cutting concerns as pipeline behaviours. A reader finds a feature in one place.
• Compile time over run time. Strong types instead of strings, source generators instead of reflection, exhaustive switches, strict analyzers with warnings as errors in the deploy gate.
• Fail fast, hide nothing. Configuration is validated at startup, every error is observable, no bare catch blocks, no silent defaults.
• Async end to end with a cancellation token on every I/O call, and the database is never mocked in tests.

Take-overs of existing code

Nine of the systems our engineers have worked on were inherited from other teams, the oldest written in 2008. A take-over starts with a read-only review and a written list of risks, then fixes in order of production impact. Across those systems we have found the root cause of more than 60 production issues nobody could reproduce, three of them open for over a year.