On my team at Bison, we worked hard to make the lives of water haulers easier. We build an electronic ticketing system tailored specifically to their unique needs.

Worked to help modernize the technology at R1RCM, pioneering into Kafka, MongoDB, and working on a transition into the wonderful world of DDD bounded contexts.

We're working on modernizing the tech stack at R1, using .net, MongoDB, MS SQL, and other tools. During this time I was able to dig deeply into several technologies to uncover some interesting performance problems related to caching. See my Projects for more details.

My team works on OpenTrack, a SOAP-based API consumed by third parties. Our stack involves DB2 and C#.

I worked to ease some communication challenges between our DBAs and our software engineers. The main technical task I worked on during this time was creating a way to manage our database schemas in source control. The main non-technical task I worked on was helping people to talk about concerns in ways that didn't polarize, and to overcome polarization that had already happened.

This was a great opportunity for me to build a team that started as 3 people and grew to over 20. I had opportunities to work as a member of the executive team, as Principal Engineer and as Director of Software Engineering, influencing the highest-level discussions about the company and department strategy. Highlights:* Overhauled Software Development Lifecycle * Changed from XP-based process to Kanban process. Prior to this change, delivery was roughly once a month and consistently about 3 weeks late; after the change, we delivered and released multiple times per day * Experimented with various levels of self-directed teams. One experiment involved not specifying teams at all, allowing mobs to form on-demand* Mentored team on best-practices such as TDD, SOLID, continuous delivery, pair programming, and knowledge sharing * These practices allowed us to eliminate QA from our release process, immensely reducing cycle time* Implemented remote-pairing/mobbing methodologies to enable remote teams to collaborate more meaningfully * Remote workers often suffer from isolation. We successfully overcame this, creating highly productive and collaborative virtual spaces* Moved single-page application from Angular.js 1.3 to React.js.* Designed event-driven system using .Net Core, Golang, Node.js and RabbitMQ to replace older Flash-based auction/bid management system* Migrated services from monolithic PHP app to Golang and Node.js services* Served as mentor and coordinator for Neumont Enterprise program.

At Pluralsight, I got to dive head-first into culture. They believe that culture is their number one competitive differentiator. I love this philosophy. As a Software Craftsman in a very flat organization, I had opportunities to discuss and help make a lot of the big decisions for our department.Highlights:* Helped grow the team from just over 10 craftsmen to over 40. * Participated in open-space conferences to discover and resolve departmental challenges * Served as peer-coach, providing one-on-ones to my peers, providing feedback to management * Helped create and use event-driven (RabbitMQ) system enabling different teams to own their own codebases* Participated in the continuous technological evolution * Helped to introduce Javascript to the back-end technology stack * Migrated from performance-challenged RavenDB to Cassandra * Built auditing system for RabbitMQ* Served as mentor and coordinator for Neumont Enterprise program.

My first exploration into "formal" leadership, this position was a delightful challenge for me. I had considerable programming experience at this point, and lots of ideas about leadership, but no actual leadership experience or training. I sought direction from trusted associates and mentors and followed my instincts on how to manage people. Highlights:* Built automated functional and performance testing tools using C# and Node.js, D3.js and MongoDB* Built back-end task distribution system for virtual 3d glasses try-on technology, using OpenCV, Node.js, C++ and GPU computing* Ran team using XP-style sprints

1-800 Contacts introduced me to full-time pairing and test-driven development. I was fortunate to be a part of a team that took professionalism (especially from the Bob Martin perspective in Clean Code) very seriously. Highlights:* Facilitated discussions about coding standards * Full-time pair programming * Test-Driven Development* Ran agile retrospectives * Read and discussed influential books together, like "Clean Code" and "The Pragmatic Programmer"* Built and maintained systems using C#, MS SQL Server, ASP.Net and Silverlight

With a fairly well-established scrum-type process in place, SeamlessWeb helped me to learn the benefits of these processes first-hand. I learned about things like code reviews, customer demos, and periodic releases. We had regular discussions about our system architecture, from which I learned I really enjoy thinking about systems. I made many lasting friendships at this job and had good opportunities to think about how behavior affects culture and vice versa.Highlights:* Created and maintained systems using C#, MS SQL Server, Maverick.Net* Learned about unit testing, explored Test Driven Development* Learned about pair programming

This was my first introduction to the idea of Agile. The company was certainly using waterfall, though, of course, they didn't know it by name. They handed me and the other engineer copies of a few books on agile (the pink XP book, for one) and said: "read these and let's do some agile". We read about pair programming and story cards and iterations and tried our best to implement them. In addition to the waterfall process, we embarked on a Grand Rewrite (also unaware that this was a common antipattern) of an application from VB6 into C#. As we worked to get our customer (the owner of the company) to give us bite-sized stories, he was consistently confused that we needed more direction than "make the new app do everything the old app does, just in a better technology".I learned lots about collaboration, pairing and story creation at this job. I would have benefitted from knowing that agile methodologies work best when understood by more people involved in the process.