The Engineering of Wood

A parallel discipline that sharpens the way I build software.

Armin Mehran

When I’m not architecting mobile and AI systems, you’ll usually find me in the workshop—because for me, woodworking is the purest form of engineering.

In software, we define constraints, design structures, and solve problems with precision. In woodworking, the same principles apply—but with higher stakes. There’s no Ctrl+Z, no rollback, no safe sandbox. A wrong cut is a production bug, and a merge conflict means you’ve just turned a $200 piece of walnut into expensive scrap.

That pressure forces a different level of critical thinking, anticipation, and disciplined execution—the exact soft skills that drive my career as a mobile engineer and AI developer.

Woodworking has become my off-screen training ground. It sharpens my ability to:

For me, it’s more than a hobby—it’s a complementary engineering discipline. It keeps my mind sharp, keeps me solving problems in new ways, and keeps me connected to why I love building systems in the first place.

📐 The “Architecture” Phase (Planning & CAD)

Just as I wouldn’t write a line of code without a sequence diagram, I don’t make a single cut without a blueprint.

🪵 Material Constraints (Runtime Environment)

Wood, like a mobile operating system, has opinionated constraints.

🐛 Debugging the Physical World

Mistakes happen. A chisel slips; a measurement is off.

Recent woodworking projects