I led various teams at Fountain over my tenure, including some of the Hire Product Engineering teams, Cloud Platform, Developer Experience, Strategic Engineering, Release Engineering, and Data. The common themes were maturing our practices, driving for consistency across teams, and reducing the length of feedback loops. Key initiatives:- Increased the product release rate from 3/month to 4/week- Centralized and standardized our engineering interview process, improving the impact of new hires- Introduced iterative product planning and execution to the Data team

I recharged while writing about my career experience (see link to blog, above), optimizing our home meal planning, and improving our household operations to accommodate working and schooling from home. I have helped a few companies in my network. I have aided architecture, design, and development for Curious Duck (https://curiosduck.io) and advised about web content application development for Bigger Bolder Baking (https://biggerbolderbaking.com - 2.6M+ YouTube subscribers).

PKS (now known as TKGI) is a jointly-developed Kubernetes distribution from Pivotal & VMware that was a service for Pivotal Cloud Foundry (now known as Tanzu Application Service). Pivotal was acquired by VMware in late 2019.I was the Engineering Lead on the PKS Release Engineering team. I defined, prioritized, and accepted the work for this team of 10 developers from Pivotal and VMware. We optimized the configuration, build, and CI runs for hundreds of pipelines, doubling the number of concurrently supported releases from 2 to 4 while reducing the elapsed-time-per-change of hundreds of pipelines by 75% - from 4 days to 1.As a member of the leadership team — three managers reporting to our VP of Engineering — we restaffed the Pivotal team from Ireland to Palo Alto, dealt with regular joint-venture management style clashes, and managed our freshly-hired staff through the ambiguity of acquisition. I continued to run the summer intern roundtable, incorporating the Palo Alto interns from the PKS and Greenplum teams.

Pivotal was the primary sponsor of the Cloud Foundry project, a multi-cloud Platform-as-a-Service (PaaS) for deployment of web apps and services. Pivotal sold its own version of CF, now known as Tanzu Application Service.I was an engineer on the Open Source CF Cloud API team and managed 4 engineers on other teams. I facilitated working sessions to improve managers' skills across the San Francisco office. I rebuilt the summer intern experience, starting a weekly "intern roundtable," where Pivotal leaders from around the company came for an AMA-style chat with our developer, product manager, and designer interns.

I created this team out of a need to improve the development & maintenance of our business-critical, internal software projects. I grew this team from nothing to 16 developers, product managers, and designers across two sites - San Francisco and Toronto. I drove budgeting and prioritization exercises with executive staff for our work. I also coached other IT teams regarding Pivotal's agile practices.

I managed a staff of 40 developers and 5 managers, about one-third of the the San Francisco consulting practice. I scoped projects, wrote proposals, and managed the business relationship for clients. I scheduled “beach” time for 8 Pivotal Labs open source projects across multiple offices. I continued to present at conferences, meetups, and clients about Pivotal, Extreme Programming, and testing JavaScript.

I was a member of the first manager cohort when Pivotal grew to need managers. I managed 10 individual developers. I continued to lead consulting projects for clients. I also presented at conferences, meetups, and clients about Pivotal, Extreme Programming, and testing JavaScript.

I was a engineer on dozens of consulting projects, all Ruby on Rails or JavaScript web-mobile applications. Co-authored Jasmine, a BDD framework for JavaScript testing.

I joined this web startup to work on their Ruby on Rails application that powered the online women's magazine Divine Caroline. After attempting various agile practices at previous jobs, I was test-driving, pair-programming, and releasing new production code all the time with a team that actually wanted to do the same. Even when this fledgling site was down when a story made the front page of Yahoo!, we learned to keep the backlog moving. Among my favorite parts of this job was interacting with RGM's writing team - a group of smart, witty, in-house customers for the features we developed every day.

I taught myself Ruby, Rails, and modern web development at a local Peet's Coffee, "borrowing" the WiFi from the adjacent Apple store. I explored developing mobile-specific web products including an RSS reader.

I designed and managed implementation of software that updated the OS and applied carrier customization for every Treo phone at the end of the manufacturing line. This reduced the elapsed time to manufacture a phone from hours to minutes. I managed the implementation of the installation development for every Treo in-box CD.

I led prioritization and implementation for the Messaging and Photos applications for several releases for the Treo 600 and Treo 650. I managed remote partners for libraries for these apps.

I managed the team of 5 developers that produced daily builds of new internal SDKs for application developers. I inherited, re-prioritized work, and shipped a new bug database web app, based on Bugzilla (https://bugzill.org), for internal use.

I was the architect for image processing, signal processing, and JPEG compression libraries. They were hand-tuned, per-processor assembly code for high performance. I managed the remote development team in Sarov, Russia, who were were employed as part of the Clinton/Yeltsin Nuclear Cities Initiative (https://en.wikipedia.org/wiki/Nuclear_Cities_Initiative).

I was one of the original team, developing an object oriented web graphics editor for Microsoft Windows. I designed and developed several of the image filters and large chunks of style application code.

I maintained and enhanced a custom animation codec used in several games. I combined the separate Win16 and Win32 codebases in order to halve the time it took to fix a bug. I added this codec to games like "Where in the World is Carmen Sandiego." I wrote MMX assembly routines for games like "Riven: The Sequel to Myst"?

I was a developer on the DCI project, which proved that direct-to-frame-buffer and accelerated graphics was viable on Windows. This technology was shipped with Windows 95. It led to three patents and became the inspiration and basis for DirectX 1.0 and the XBox.

I spent two Christmas and one summer break setting up IBM PS/2's, supporting corporate demos, and a little programming in OS/2 multimedia authoring systems.