Software engineer in the Bay Area. Writing about software craft, working with AI, and what I'm trying to make sense of.
Most of my work has been about systems that need to coordinate — API integrations and data reconciliation across automotive services, then scheduling and instrument orchestration in lab automation. I studied computer science at UC Irvine and am working on an M.S. through Georgia Tech's OMSCS. Each move has taken me into a new industry, and I've gotten used to picking up domain context quickly and figuring out what actually matters.
A lot of what I write here is me thinking out loud about my own work — how AI tools fit in, what graduate school feels like the second time around, what I'm figuring out as I go. I don't claim to have answers; I'm mostly sharing the questions as they come up.
Now
- Doing an M.S. through Georgia Tech's OMSCS.
- Working on backend systems that coordinate across services and devices.
- Figuring out how to actually use AI tools well in my own work.
Selected Writing
- A Few Months Into Team-Wide AI: What I'm Still Figuring Out A few months into team-wide AI use, here are the patterns I'm seeing — and the question that keeps coming back about what should stay consistent across the team.
- How AI Changed My Development Workflow After Switching Jobs Moving from a Copilot-only environment to a team that actively uses Claude Code — what changed and what I'm still figuring out
- Understanding How Claude Code Works Under the Hood A walkthrough of Claude Code's execution lifecycle — from the moment you type a prompt to the final response
- Building a Windows Installer for Offline Field Deployment How I introduced a WiX-based Windows installer for deploying field software to air-gapped environments, and the unexpected challenges along the way.