The breadth of my work is in Microsoft Azure Docs, focusing largely on CI/CD and related technologies. I've contributed to an article on Azure Pipelines in the upcoming Connect(); 2018 special edition of MSDN Magazine, where I'll be credited as a Microsoft technical expert.

I continued maintenance of the on-prem migration system, performed CRM data migrations, and built a team of data engineers for CRM migrations.I designed a new data migration system, born in Azure and cribbing from the legacy system. The modern version is being built on Databricks and Delta Lake, leaving behind traditional computing and the RDBMS. My new team is cross training on the legacy system to continue maintenance and to fully understand what the scope of the new work is. Together, we’re identifying strengths and weaknesses in the legacy system so it’s clear what should be emulated when implementing the new system and what needs to be avoided.I’ve created a set of milestones in the architecture at which there is a clear pause in the continuity and chance to demonstrate comprehensive improvements. Of course, my team and I understand how and when we’ll have every little opportunity to show a new feature or performance gain between milestones.While there is a 1.0 goal where we’ll confidently say the new system has functional parity with the old, I always say there’s an unlimited amount of work in this space. I’ve already queued up future work for automation and analysis improvements, and I encourage my team to keep track of everything they want to improve on.

In this role, I lead CRM migrations using an on-prem system built on Python, Pandas, and SQL Server. I was responsible for maintaining legacy ETL, migration, and reporting systems; and I designed and implemented automation based on real time communication with the Salesforce API.

While on contract, I was responsible for two main areas: developing an OData API to access mastered data and building a framework to validate arbitrarily large or small sets of data.My OData API was built using C# and .NET Core 3.1. The key component was a code generator built using the Code DOM libraries. At build time, an API is contacted which returns JSON describing the schema of the data. This JSON is in a well-known format so the code generator easily parses it to create models and controllers for the API every time it is rebuilt. This allows the team to define their data however they like, provided the code generator receives JSON in the expected format.My validation framework has two facets: a Python library which defines atomic validations and a PySpark layer which registers those validations as UDFs. The former can be used for quick validation responses over relatively small data sets, which you'd want when working with small data like individual records input through a web portal. The latter is intended to perform the same work but over large datasets. As with my OData API, this project relies on configuration details about the data, such as the structure, nullability, valid values, and so on.In addition to these two projects, I consulted on other projects, primarily related to their Azure assets and ETL orchestration.

My mandate is to create an infrastructure and platform for the ingestion, processing, and presentation of vet data. My work powers everything from simple web applications, to SaaS add-ons for commercial vet products and third parties which use the data for business intelligence.I lean heavily on automation using Azure DevOps CI/CD pipelines and ARM templates for a flexible deployment strategy. Azure Data Factory is vital to my work, and I've started experimenting with Azure Databricks/pyspark, Azure Data Lake Analytics/U-SQL, and Azure Cosmos DB.Aside from data engineering, my team and I are implementing best practice patterns for DevOps. Our version control, CI/CD, monitoring, and maintenance strategies will set the gold standard for DevOps in other areas of the organization

I've worked on updating a legacy data platform in a private cloud. The system focuses on the ingestion of vet data for use by a commercial web application.The technologies I used include the following:- C#- NuGet- VSTS, including CI/CD pipelines and NuGet feeds- REST APIs- Windows Services

I'm a Software Engineer I at Patterson Veterinary on IntraVet. I work in C# to develop features, implement performance optimizations, and fix bugs through every layer of the application. I also frequently work with DevExpress and WinForms on the frontend and MS SQL Server on the backend.I'm also the "Agile Champion" for my team as we transition to an Agile process. Basically, as one of the team members with the most practical Agile experience, I get to advocate for refinements to our process in order to become more Agile and I get to be a sounding board for anybody with questions or concerns about Agile.

I continued my previous work as an associate software engineer for BigMachines by taking the lead engineer position on projects during this time. I expanded my responsibilities by further standardizing coding standards documentation and unit testing procedures.I assisted less experienced engineers by providing regular lectures on certain best practices and I acted as an itinerant mentor for those less familiar with the industry, company, or engineering in general.

As lead developer on several projects over the past year, it has been my responsibility to design solutions and delegate work to other engineers as well as implement the designs for those projects. I work on the BigMachines webapp developing primarily server code written in Java. Depending on the needs of my projects, I'll branch out to work on the JSPs, utilizing HTML, CSS, Javascript, and other front-end technologies; the database layer, using Oracle PL/SQL; and miscellaneous other technologies used throughout the application including Spring, DWR, and Maven.I am also responsible for maintaining documentation on JUnit best practices in our application and training new engineers in the use of JUnit, JMock, and Hamcrest libraries.I've also branched out as the primary engineer responsible for merging since we migrated to Microsoft's TFS in the Fall of 2012.

I am currently developing a web application for Media Services in Visual Web Developer 2010 to inventory our DVD archive and circulating equipment. At later stages in development, I am planning on creating an automated scheduling app for our workers and an equipment circulation system for our AV equipment.

Helped to pilot a student supervisor program with the Media staff. Supervised and trained a group of up to 15 student workers. Maintained, repaired, and replaced computer and A/V equipment on campus. Designed web applications for use in-house to streamline portions of the workload, including an archiving application for video recordings and an application for scheduling the department's workers.

Worked on a strike team to test a specific portion of a video game being developed by the studio. Assisted in developing and carrying out test plans. Worked with other strike teams to coordinate our test plans when their test areas overlapped. Worked frequently with development staff to pinpoint and eliminate software bugs. Stress tested the network capabilities of the software and debugged game audio.

I was responsible for selling digital cameras, camcorders, and accessories for same. I helped develop sales strategies, attended supervisors meetings, and assisted in the day-to-day operations of the Digital Imaging department.