I build for the handoff.
I document up front and build so nothing assumes I’ll always be the one running it. A project has a start and an end, and the work should transition to the people who operate it. That’s what frees me to go do the next thing.
I’m a technical program leader with the depth to read the code, design the system and write it. Every few years the tools turn over, and I go after each one, learning what it can actually do and making it fit the work in front of me. Right now that’s AI. I tend to go first into the part nobody has mapped yet, then bring people in behind me.
Three things show up in everything below
I document up front and build so nothing assumes I’ll always be the one running it. A project has a start and an end, and the work should transition to the people who operate it. That’s what frees me to go do the next thing.
AI widens what I can research, compare and flag. It doesn’t decide which of five findings matters, or where the real decision is hiding. That judgment is what turns capability into a result.
I’ve sat on several sides of the same table. The costly problems are the ones each group reasonably assumes someone else has. I’ve done enough of each job to know what each side is likely to miss.
Each one follows the same shape: the situation, what I decided, why that instead of the obvious alternative, what changed, and what I’d do differently.
Two decades in central IT at UC San Diego. A major research university with a medical center, where I worked across six different business domains and learned systems from the code up. Since then, I’ve owned compliance and run technical programs for a higher-ed SaaS company. Outside work, I volunteer the same skills for a statewide nonprofit.
The best way to reach me is a message on LinkedIn.