skip to content
open to remote rolesget in touch →

skills

Grouped by purpose. Not ranked.

A star rating would tell you less than the case studies do. The depth is in the backend column: C# and .NET 8 with ASP.NET Core and Entity Framework Core, against SQL Server schemas designed rather than inherited, plus Kafka for events, Redis for cache and SignalR for the paths that have to arrive in real time. Around that sits what it takes to get the work out of the door and keep it there — Azure App Services and Blob Storage, Docker, code review, and enough React to build the interfaces on top, including this one.

Languages

what the work is written in.

C#SQLTypeScript

Frameworks

where most of the backend work happens.

.NET 6.NET 8ASP.NET CoreEntity Framework Core

Frontend

the interfaces on top, including this site.

ReactVite

Architecture

how the services are put together.

RESTful API designUnit of WorkRepository PatternRole-Based Access Control

Messaging & cache

moving events around, and not recomputing what has not changed.

Apache KafkaRedisSignalRFirebase Cloud Messaging

Cloud & services

getting it out the door and keeping it there.

Microsoft AzureAzure Blob StorageAzure App ServicesDocker

Database

modelling it, storing it, keeping it fast.

SQL ServerDatabase schema designCode-FirstDatabase-FirstQuery optimization

Practices

how the work actually gets done.

Agile / ScrumCode reviewsPerformance optimization

None of this is ranked, because the projects say more than a rating would. The Digital Austrian case study is where the .NET, Kafka and SQL Server end of it is load-bearing; the Budgetick case study is the same person shipping a product end to end.