Stack

Tools are a means, not an identity, but here's what I reach for first and why.

Golanguage

The default for anything that needs to be fast and simple to reason about — no hidden magic, no runtime surprises.

My go-to for scripting, data work, and gluing systems together fast.

Where I learned to think in objects and interfaces — still my baseline for statically-typed OOP.

Production feature work on a .NET financial platform at Re: Members — strongly typed and easy to trust.

Every real system eventually needs a query an ORM can't fake.

Systems and algorithms coursework — the language that makes you understand what's actually happening under the abstraction.

Migrated CI/CD for 500+ repos onto shared reusable workflows at Tekvortex · InvisiRisk — my default for anything that has to run on every push.

If a change can't ship itself, I don't trust it to ship.

The same container in dev, staging and prod — one less category of bug to debug.

The OS almost everything I build actually runs on, so it's the one I've bothered to actually learn.

My default database — relational, boring, and it just works.

Postgres plus auth and an API, without standing up my own backend for a side project.

The simplest contract two systems can agree on.

Version control isn't optional — it's how you undo the mistake you haven't found yet.

Closed 30 tickets in 50 days on Re: Members' production .NET platform — the highest of any intern that summer.

Batteries-included Python, which is exactly what a dues-and-ledger dashboard like Palamedes needed.

Fast, typed, and quick to wire an API around — my pick when Django is more than the job needs.

What this site is built with — a good excuse to take the frontend seriously.