About me
Software Engineer, Tech Business Operations (Enterprise Data & Analytics) at Sargent & Lundy.
I build internal engineering software at Sargent & Lundy, a power and nuclear engineering firm founded in 1891. The work sits where heavy engineering documents meet distributed systems: image registration and computer vision over drawing sets, queue-backed workers that process thousands of sheets asynchronously, and the pipelines that make the output searchable.
Most of what I ship is Python and TypeScript on Azure Container Apps, with the infrastructure defined in Terraform and deployed through GitHub Actions. I started as a part-time intern and converted to a full-time developer role, and I am now the primary developer on a production internal application and on a document enrichment and search pipeline, and the author of the firm's Python coding standards.
I work iteratively and prefer small, well-tested pull requests over large speculative rewrites. I care about grounding decisions in real production telemetry rather than assumptions, and about writing code that the next person can maintain.
How I work
- Ship small and verify
- Incremental pull requests with tests over large refactors, especially in code I do not own.
- Measure before optimizing
- Production telemetry and memory profiles drive my performance decisions, not intuition.
- Fail loudly
- When a hard limit is exceeded, I return a clear user-facing error rather than degrading silently.
- Build durable, not clever
- I default to the standard platform pattern that will still make sense in a year over the quick patch that gets past today's problem.
- Write for the next reader
- Standards, briefs, and documentation are part of shipping, not overhead after it.