It was quite by accident that I found myself working as a build and SCM engineer early in my career. A few years later I started working for a client project built on .net (3.5) and hosted on IIS using TFS 2008 (at that time Azure DevOps was still TFS) as a source code repo, continuous integration, and continuous deployment tool. Since then, I have been fortunate to have worked extensively on each of the versions of TFS to Azure DevOps 2019 Update 1 in my professional career.
Over the years I have dabbled with writing small productivity (.net) utilities to help me with my day to day job – auto-merge of branches, automated check-in, automated linking of work items with changesets, and such. Currently, I am working as a Sr. DevOps Engineer at edmentum on maturing and stabilizing our DevOps process. I heavily rely on automation, infrastructure-as-code, and Azure DevOps on achieving these objectively.
My newest trial is -how to use Azure DevOps as an infrastructure automation tool that may be used to auto-provision environments. I know that Azure DevOps was not originally meant for that purpose but so far it’s been fun trying to extend the tool’s capabilities.