Designed and tested the backbone of our service, a complex synchronization protocol between webserver database and remote filesystem. I mathematically proved the complete set of testable scenarios for this component to guarantee stability.Built automated code deployment pipeline in Bash. Takes care of proper sequencing of deployment steps. Automatically able to roll back if deployment failed. Enabled builds to run on any of our servers instead of being built per target.Built inter-process communication protocol for efficient server re-configuration.Migrated codebase from Python 2 to Python 3.Migrated cloud provider from Rackspace to AWS, updated web app architecture of our service.Built tools to ease management of servers, improve system inspection, and handle deployment.Completely rewrote and expanded existing API exposed by backend.Created flexible, secure, re-useable code for interpreting url query parameters in our API.Built server monitoring/alerting system and dashboards using Prometheus and Grafana.Containerized legacy software with Docker in order to migrate other components to newer versions/OSes.

Spent twelve weeks at the Curtis R&D facility in Livermore, CA. I mostly worked on the Curtis Software Suite, a tool for programming motor controllers over CAN bus. I learned how a project of over 200,000 lines of code is organized, how development is controlled via branching in the repository, and how real-life coding standards are developed and enforced via code review. The software suite has a client-server architecture built using Windows Communication Foundation, and is written in C# using mostly Windows Forms but transistioning to Windows Presentation Foundation (WPF). I became much more proficient with C# and the .NET framework by debugging and adding features to their Windows Forms and WPF software. In addition, for the Automated Testing Suite that Curtis uses to verify controllers I wrote driver software for their new programmable load.