Background

Why AEC Software

Through architectural training and professional work, I became increasingly aware that many design and construction challenges are not design problems, but tooling problems.

Data loss between platforms, inconsistent models, manual quality checks, and brittle workflows can introduce risk and inefficiency long before construction begins.

Learning to code (initially from scripting and gradually through software development) changed how I approached these issues. Instead of working around limitations, I began building tools to reduce friction, automate checks, and make model data more reliable.

How I Work

• Design-aware software thinking: I build tools with an understanding of how architects and engineers actually model and coordinate, not just how data is structured in an API.
• Incremental and testable development: I prefer small, composable tools with clear inputs and outputs over monolithic systems.
• Learning through building: Most of my technical growth comes from personal projects that address real workflow problems.

Education & Credentials

I hold a Bachelor of Science in Civil Engineering at National Taiwan University and a Master of Architecture at Yale School of architecture. This dual background informs how I think about constraints, systems, and implementation across design and construction.

I have passed the FE exam and am currently awaiting EIT certification.

Tools & Context

My work spans AEC production workflows and the tooling that supports them. In practice, that means a mix of 2D drafting and documentation, 3D modeling, and lightweight automation where it removes repetitive effort.

I'm most experienced with AutoCAD and Civil 3D for 2D CAD workflows, and Rhino + Grasshopper for 3D modeling and computational design. I'm also comfortable with graphics and visualization tools across the Adobe suite and rendering workflows (e.g., V-Ray).

On the software side, I build small, focused tools in C#/.NET and web interfaces with HTML/CSS/JavaScript.

Contact