WHY IBUILD

Most problems worth solving are physical in the end. Someone has to move the weight, hold the load, make the part, ship the vehicle. Software is leverage on that world, not a replacement for it.

I want to work where the two meet: where code has to survive contact with a moving, worn, real object, and where a clever idea is worth nothing until it holds up under load.

Robotics is the discipline that refuses to let you fake it. The math either moves the arm or it does not. I came to it through a wearable exoskeleton and stayed because it forces every skill I have, mechanical design, control, ergonomics, manufacturing, into the same problem at the same time.

That pressure is where I do my best thinking. A constraint is not a limit on good design. It is most of what good design is.

AI is the largest lever engineers have ever been handed. I use it as a second engineer, not a novelty: to move faster from question to working code, to explore more designs than I could reach by hand, to automate the parts of building that were never the point.

Used well, it does not replace craft. It buys back the time to spend on it.

A company is the vehicle that takes a good build to the people who need it. Running a clothing brand taught me that a product is only half finished when it works; the other half is getting it into someone's hands.

Startups are how ambitious hardware actually reaches the world. I intend to build them, not just admire them.

Five things I hold to. Stay curious enough to keep learning in the open. Take ownership: if it needs to exist, build it. Treat quality as a requirement, not a finishing pass. Assume v1 is wrong and iterate toward right. And aim past what looks immediately possible, because the interesting problems live just beyond it.

Human augmentation, robotics that do real work, and the companies that make them ordinary. I am early, and I know it.

This page is a direction, not a summary. The work is the argument. Everything here is just me saying, out loud, what I am walking toward.