The Practice

Twenty-seven years in software engineering sit behind this practice, starting with a BMath from the University of Waterloo in 1997 and an MMath in Symbolic Computation in 1998, and continuing through an MEng in Software Engineering from Concordia in 2016. In between: an architect role at ThoughtWorks, a CFA Level 2 candidacy, and a body of SR&ED-approved engineering work — the same rigor applied to the numbers a client cares about as to the code they're paying for.

The earlier engagements were airline booking built in front of a mainframe reservation system, national pipeline capacity allocation on a J2EE stack, and real-time telematics insurance priced off live vehicle activity across three countries — each one a system that had to be correct in production, not just convincing in a demo.

The decade that followed sat inside energy-sector systems specifically: crude blending economics, pipeline capacity allocation, and tariff and equalization settlement, running from one model integrated with SAP across the enterprise — the kind of system that stays live for years and has to converge correctly inside a working planning session, not just pass a test suite.

There is no bench behind any of it. Engagements are staffed from a curated network of senior engineers, assembled to the specific shape of the work in front of them, never padded to fill a schedule. Every engagement, whatever its size, is led personally, start to finish, by the person who founded the practice.