Model first, interface second
I start with structural behavior and numerical logic, then design tooling around that model. A good interface should reveal engineering intent, not hide it.
About
Structural Engineer & App Developer
I design real buildings and build engineering software. This site is where those two lines of work meet.
I work at the intersection of structural engineering and software. In practice, that means designing high-rise and long-span systems while also building tools that reduce iteration time, improve clarity, and make technical decisions easier to communicate.
I care about the fundamentals: stiffness, load paths, boundary conditions, and how numerical assumptions propagate into design decisions. Software gives me a way to operationalize that thinking into workflows that are faster and more repeatable.
The writing here focuses on methods and implementation details. The project work focuses on practical utilities that engineers can apply immediately.
I start with structural behavior and numerical logic, then design tooling around that model. A good interface should reveal engineering intent, not hide it.
I automate repetitive ETABS and post-processing workflows, while keeping assumptions visible and reviewable. Speed only matters when trust is preserved.
My tools are shaped by deadlines, coordination loops, and iteration cycles from building design work. Practical use in production is the benchmark.
I publish derivations, implementation notes, and failures. Explaining the method makes the work reusable for other engineers and future projects.
If you are building structural engineering tooling, exploring computational design workflows, or want to discuss implementation details, reach out.