Supported the Haskell programming language ecosystem as a member of the GHC compiler team and infrastructure working group. Bridged disconnected teams with direct participation and weekly public reports. Built and operated a service that drastically improved CI for the compiler by mitigating spurious failures. Built and operated deployment workflows for ecosystem services such as Stackage. Indepedently planned and executed service migrations for various critical services. Improved ecosystem resiliency and improved service continuity with better documentation and processes.

Leading a (Fullstack/DevOps/All of the above) team that provides a range of custom solutions to other teams within RELEX. Like the company as a whole, we increase the bottom line by reducing "spoilage" (i.e. accidents in production operations) and improving our colleagues' efficiency!

Currently building an internal deployment service and mentoring other Haskellers, Nixers, and functional programmers. Learning Dhall by osmosis.

A member of Team Mordor, using pure functional software in the DevOps department. Currently leading development of a Nix-based deployment tool as the company reinvests in its very custom, very practical operational environment.

Initialized unit test framework for Databrary's web service, allowing test coverage to grow from 0 to 20% (and counting). Rewrote Haskell, SQL, and Nix components to allow a simpler build process and easier integration into CI and deploy systems. Authored the backend priority list and initiated conversations on vision with other stakeholders, contributing to an ongoing team realignment.

Slashed lines of code by 71% to focus team and volunteer effort. Collaborated with team leadership on developing governance and structure to maximize openness and effectiveness. Implemented (with Haskell) a new system architecture, new funding mechanism, and new website as the project iterated on its mission.

Turn research prototypes into marketable products, encompassing testing, refactoring, and developing new features.Involved in an early-stage project to create a quality/reliability pipeline for third-party research prototypes.

As the first full-time dedicated programmer, I contributed to the development and progress of the company's roadmap. Authored one Javascript library, three web apps, and one cross-platform Haskell executable; contributed to a wireless robot-control network. Contributed significantly to the architecture, development, and deployment of Linkbot Labs, the flagship platform for robot-centered math and science curricula.

Learned Javascript, joined the Haskell community, and met and collaborated with open-source programmers while on the road. Returned to Thomson Reuters (below) for a short contract in spring 2012. Researched and prototyped a number of tools with technologies new to the team such as Boost::Build. Relieved numerous small but substantial burdens to the understaffed team in a time of transition. Visited 20 countries, half via bicycle.

- Rewrote a critical monthly financial data generator. Over the course of a year, I studied the entire tool, made the case for rewriting it, and did so. The new system allows a markedly shorter and more consistent QA experience, and generates an end product in days rather than weeks.- Untangled a cryptic equation-definition system inherited by our team. While immersed in foreign tools and languages, I explored how functionality in our existing system could be mirrored in the new one. Laid the groundwork for a future conversion project.- Contributed knowledge and expertise. A passion for tools, technologies, and documentation made me a recognized source of information on Vim, Perl, shell scripting, and Free Software solutions.

- Contributed to all technological aspects of this early-stage startup, including Linux administration, developer collaboration, system automation, and web development.- Constantly learned new material to achieve company goals. E.g. with zero foreknowledge of PHP or SQL, I inherited—and completed—a stalled MySQL/PHP project that represented a node in the business plan's critical path.