General notes — how Lawrence Yee works
Working notes from someone who still thinks in plans, sections, and massing studies — even when the medium is software.
G1
Draw it before you build it. I came through architecture — plans, sections, and massing studies still shape how I scope software.
G2
Interfaces for people doing precise work: legal teams, architects, operators who need the tool to match the job, not the other way around.
G3
Prefer small, legible surfaces over clever abstractions. Code should read like a set of working drawings.
G4
3D and geometry are strengths, not detours — spatial problems get spatial tools.
G5
Ship, measure, refine. Campaigns, load times, and ticket throughput matter as much as the initial design.