Derivations worked through in full, and implementation notes from the software I build around them.
Static Astro, Svelte islands that have to justify themselves, and quality gates that read the built output rather than the source. Why the architecture is shaped that way, and what it caught the site claiming about itself.
Where the element stiffness matrix comes from, in full: virtual work, shape functions, the strain-displacement matrix, and the 12×12 frame element, with every step derived rather than quoted.
The ETABSharp repository carries an MCP server, so an assistant can call the ETABS wrapper instead of being pasted screenshots of the model. What MCP is, what the server is today, and how to run it.
Saola is the Grasshopper plugin built on ETABSharp: three layers, a model connection that passes through every component, and typed results instead of try/catch. Why each part is shaped that way.
ETABSharp is a typed C# wrapper over the ETABS COM API: session lifecycle handled, return codes turned into typed results, the full surface still reachable, and a shape an LLM can write against.