Shared foundations
I build the project seeds and templates that teams start new apps from, so every team begins with the same structure. The first one I published was an ASP.NET MVC 5 admin template, in 2017. Others have starred and forked it.

I've spent 14 years building enterprise systems, and I make the structure that keeps a team's work consistent, whatever the stack.
I make what other people build on: project seeds, templates, written decisions and tools. The standards belong to the team. I build the ground they stand on.
I build the project seeds and templates that teams start new apps from, so every team begins with the same structure. The first one I published was an ASP.NET MVC 5 admin template, in 2017. Others have starred and forked it.
When nobody remembers why a system works the way it does, new people have to guess. I write the reasons down in the repo, as decision records, so they don't have to.
I review my teammates' code, seniors' as well as juniors', and I use the review to coach as well as to check.
When a step fails halfway, the work should not be lost or done twice. I build retries, recovery of stuck work and protection against duplicates.
Notes on building software, and on helping a team work well.
A gentle game I made for toddlers: pop bubbles, paint and mix colours. I built it to the standards I use at work, with tests first and a strict content security policy.