Thanh Tu Do

• Structural engineering

  Designing real buildings: high-rise and long-span systems.

  This is where the constraints come from: stiffness, load paths, boundary conditions, and how a numerical assumption propagates into a design decision. Nothing on this site documents a specific building — the practice is the source of the problems, not a portfolio.

• Engineering software

  Building automation and analysis tools for that work.

  ETABSharp wraps the ETABS API in typed C#, and the browser tools run the same kind of calculation with nothing to install. Both came out of workflows that were slow and error-prone to repeat by hand.

  • C#
  • .NET
  • ETABS API
  • MCP
  • NuGet
  Published projectsBrowser tools

• Technical writing

  Publishing derivations worked through in full, not summarised.

  Derivations from first principles, and implementation notes from the software above. The site publishes the working, not just the result.

  Articles

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.

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.

Automation with engineering judgment

I automate repetitive ETABS and post-processing workflows, while keeping assumptions visible and reviewable. Speed only matters when trust is preserved.

Build for real project pressure

My tools are shaped by deadlines, coordination loops, and iteration cycles from building design work. Practical use in production is the benchmark.

Share the method, not just results

I publish derivations, implementation notes, and failures. Explaining the method makes the work reusable for other engineers and future projects.