"Software is best written by the people who have to live with it."
Most AEC software is written by engineers solving the generic case — people who never hand-renamed two hundred sheets at midnight, or waited on a grading tool that was never going to exist. These tools were written by someone who has, and does. That's the whole edge: they land on the real pain because they were written from inside it.
From site to code
Design school leaves one durable habit: read a messy site as relationships, run one organising move through the whole thing, resolve it into something buildable. A tangled workflow turns out to want the exact same treatment.
That's why the tools feel designed, not just coded — the same judgment runs from the planting plan down into the class diagram.
What the practice brings
On the landscape side: design thinking, spatial strategy, buildable method — the part that travels, never a project's copyright to claim. Reading a site as point, line and plane; turning opaque code into decisions a team can act on.
On the software side: tools written for the front line — the RevSphere Revit suite and the DocSphere desktop tools, both in daily use, plus ProSphere for studio project management, in build toward release. Each one started as a gap that had to be worked around on a real project.