I am a senior compsci major at ASU. I treat models like powerful but unreliable components. They can move fast, and they can also hallucinate, drift, or fail silently. So I build the surrounding machinery: evaluation, guardrails, structured outputs, and monitoring that catches “confident wrong” before users do.

I build software like it’s going to crash one day, because it will. So I design it with a black box: structured logs, tight schemas, sanity checks, and traces that tell the story without guesswork.

I’m obsessed with the gap between “cool output” and “correct output.” Closing that gap is mostly engineering discipline: contracts, validation, and hard failure modes.

I don’t want systems that just impress. I want systems that hold. If a system can’t explain itself under pressure, it doesn’t belong in production.