Onsite at Intel Ronler Acres, automating manual tasks for their top group for first-of-kind Architecture & Engineering procedures. Executive dashboard with interactive visualizations of capacity forecasts. Microservices, scripts, and client UI to extract and transform data from legacy systems. [Angular 7, Material 2, Node, React, Vega; C# for .NET Core 2.1 via Docker, on Linux, in a private cloud.]

I had an idea for improving close-of-iteration software demos, by helping non-technical stakeholders understand and approve automated tests. I pursued it as a startup and learned several lessons, such as the answer to the question, "Do I enjoy being an entrepreneur more than a coder?" The answer was no.

Basically the chief software expert for the class-action division of an international legal services company that provides administrative infrastructure to large settlements, occasionally reaching billions of dollars (e.g., Deepwater Horizon). Responsible to senior management for advice on all aspects of software development, including security and regulatory compliance (defining policies, auditing systems, advising team leads) and internal adoption of modern techniques. Extensive technical… Show more Basically the chief software expert for the class-action division of an international legal services company that provides administrative infrastructure to large settlements, occasionally reaching billions of dollars (e.g., Deepwater Horizon). Responsible to senior management for advice on all aspects of software development, including security and regulatory compliance (defining policies, auditing systems, advising team leads) and internal adoption of modern techniques. Extensive technical writing of policy recommendations, technical audits, standardized development practices, technical sales support, and training materials. On-call for all max-escalation support incidents. In practice, the official person for devs to turn to if googling doesn’t help. Show less

Lead developer of a new single-page application front-ending a mapping and routing service for the freight-matching industry, using HTML5 and all the latest goodies. Also lead developer for updates to a legacy web application to reflect recent service improvements. Both projects shipped on budget and on schedule.

Propter was a rewrite of NJamb, prompted by feedback from talks I’d given and by Martin Fowler’s 2011 book on domain specific languages. Also, NJamb was a terrible name. Propter is Latin for “because,” as in "post hoc ergo propter hoc"—in classical logic, the fallacy of assuming that when one event follows another, it happens because of the earlier event. Propter tests can sample a system both before and after you invoke the action under test. It doesn't utterly eliminate post-hoc errors, but… Show more Propter was a rewrite of NJamb, prompted by feedback from talks I’d given and by Martin Fowler’s 2011 book on domain specific languages. Also, NJamb was a terrible name. Propter is Latin for “because,” as in "post hoc ergo propter hoc"—in classical logic, the fallacy of assuming that when one event follows another, it happens because of the earlier event. Propter tests can sample a system both before and after you invoke the action under test. It doesn't utterly eliminate post-hoc errors, but it makes them quite rare.The other main reason for Propter was my interest in "Given-When-Then" tests as practiced in BDD. I loved that it helps stakeholders communicate requirements, but I disliked the amount of work necessary to turn Gherkin scripts into an "executable specification" at anything like scale (say, 1000 tests). So, Propter’s roadmap (never fully released) inverted the Cucumber approach. Instead of inferring automated tests from Gherkin scripts, Propter started with the source code, added metadata and explicit C# tests, then emitted Gherkin scripts as deterministic, read-only artifacts. Show less

Web, database, and test-infrastructure development in a greenfield pilot project attached to a larger ecosystem of 4 million lines of code.

In 2009, Silverlight was still a thing. I wanted better assertions in my C# tests, so that test failures were as informative as possible. No more "Expected 'true' but was 'false'" garbage for me, thanks. I wrote NJamb to do for assertions what Linq had done for queries. Like Linq (and using many language features added to C# specifically to make Linq possible), it was an “embedded DSL" with a “fluent syntax” to let you chain together executable statements that had a secret superpower… Show more In 2009, Silverlight was still a thing. I wanted better assertions in my C# tests, so that test failures were as informative as possible. No more "Expected 'true' but was 'false'" garbage for me, thanks. I wrote NJamb to do for assertions what Linq had done for queries. Like Linq (and using many language features added to C# specifically to make Linq possible), it was an “embedded DSL" with a “fluent syntax” to let you chain together executable statements that had a secret superpower. On the outside, they were first-class citizens of C#, editable and refactorable and analyzable with all the powerful tools that static typing allows. On the inside, they each could translate themselves into a different language. For Linq statements, that language was SQL; for NJamb, it was English. Show less

Contractor to Digital Heatlh Group project in .NET, soup to nuts: Silverlight, WPF, WCF, SQL Server, IIS.

Technical lead for a team rewriting an outdated client/server application for the ready-mix concrete industry. I ran scrums. I mentored developers toward modern Agile practices. I wrote most of the foundational code for database access, MVVM architecture, and UI validation. I introduced the team to unit and integration tests, metaprogramming, and the repository pattern, among other topics.

Joined a project after a major pivot, including a turn to Silverlight from JS, as both scrum master and senior developer. (I was ambitious.) I introduced practices such as open workspace (no cubicles), continuous integration, and velocity metrics, I streamlined their estimation process to reclaim more than 10% of each person’s week with no sacrifice in measured accuracy. I reduced the iteration length from two weeks to one, which the team unanimously voted to retain. Despite a 40% personnel… Show more Joined a project after a major pivot, including a turn to Silverlight from JS, as both scrum master and senior developer. (I was ambitious.) I introduced practices such as open workspace (no cubicles), continuous integration, and velocity metrics, I streamlined their estimation process to reclaim more than 10% of each person’s week with no sacrifice in measured accuracy. I reduced the iteration length from two weeks to one, which the team unanimously voted to retain. Despite a 40% personnel turnover in 5 months, we shortened release cycles, improved test coverage, reduced average bug incidence, and established working prototypes of all major features. Show less

Small, egalitarian, highly engaged dev team producing software solutions that span web, desktop, and mobile platforms. We practiced Extreme Programming (XP) in the extreme. Microsoft and web technologies predominate, with lots of open source and proprietary tools salted in. I focused on architecture, usability, and process improvement.

Patent agent, writing and defending patent application in process before the U.S. Patent and Trademark Office. Responsibilities included broad technical expertise, fostering client relationships, oral and written communication, time management, docket management, professional development, and billing time in fastidious increments at mildly obscene rates.