cat about.md
About
I like problems that come with no map. Most of what I have worked on arrived as something already broken, already running, and written by people who left years ago.
I started at an agency, where the job was whatever the client needed that week and the infrastructure was whoever was free. Now I am at Trilogy, on enterprise products old enough that the code predates everyone currently touching it. Both pages have the detail.
What I work across
I have never been much use as a specialist. The jobs I have had rewarded being the person who would take the thing nobody else wanted to own, and that tends to mean the problem sits somewhere between the disciplines rather than inside one.
In practice that is four areas. Infrastructure: build systems, CI pipelines, runner fleets, and the servers underneath, at work and at home. Backend: Rails, Python, Scala and .NET in multi-tenant SaaS, plus the database work that comes with it, from keyset pagination to concurrent migrations. AI: the harnesses, context and verification that make agents useful on systems they cannot otherwise reach. Product: things shipped to actual people, from schema through interface and out to an app store.
The homepage lists what each of those is backed by, because the claim is worth nothing without it.
There is also a homelab that has grown well past what it needed to be: self-hosted GitLab, Appwrite, photo and camera stacks doing real inference on the box, behind nginx on an internal domain. Nobody pays me for it. It is where I hold the pager for my own decisions, and it is the reason I am comfortable owning infrastructure at work.
How I work
- Reproduce first. A fix for a bug you have not seen is a guess.
- Fix it once, where every caller routes through. Patching the one path a ticket names leaves every sibling caller broken.
- Watch the test fail before you trust it. A test that has never failed proves nothing, and that holds whether a person or an agent wrote it.
- Small diffs. Reformatting unrelated code makes review harder for no gain.
- Operate what you build. You do not really understand a system until something has gone wrong with it at an inconvenient hour.
Where I have worked
- Software Engineer IITrilogy (ESW Capital)June 2024 — present
- Full-Stack DeveloperAuribises TechnologiesJanuary 2023 — June 2024
Full detail, education and certifications are on the experience page.