About

How I think about engineering problems and how I decide what “good” looks like.

I’m an electrical and biomedical engineering student focused on instrumentation, circuits, and practical systems. I care less about demos that work once and more about systems that behave predictably under real constraints.

Most of my work lives at the intersection of hardware, measurement, and environment-driven limitations — places where assumptions break and system-level thinking matters more than component choice.

My approach

Principles that guide how I design and evaluate systems.

Start with constraints

Constraints define the problem. Environment, safety, noise, integration, and verification requirements shape architecture before components ever do.

Think in systems, not parts

Many failures come from interactions between “working” subsystems. I treat cabling, grounding, and interfaces as first-class design elements.

Design for verification early

If you can’t test it meaningfully, you don’t really understand it. I favor architectures that expose failure modes early.

Document decisions

I write down why choices were made, not just what was built. Good documentation turns projects into reusable knowledge.

What I value

Robustness over elegance, clarity over cleverness, and systems that behave well outside ideal lab conditions.

What this site is

This site is a public record of how I think through engineering problems: projects I’ve built, decisions I’ve made, and lessons I’ve learned.

Some work is polished. Some is in progress. All of it is documented with the goal of making the reasoning legible — to myself and to others.