Rich Gwilliam's digital shed
CI/CD stands for Continuous Integration / Continuous Deployment. It stands counter to the old-fashioned "waterfall" model of project management in which each phase of development was done subsequently, and ostensibly, once. This made sense when your software was sold on floppy disks, and so updates were a failure condition, if possible at all.
In CI/CD, support and expansion of the deliverable is regarded as part of the process - which is much more accurate to the life cycle of a modern application.
Patches and new features are created as reaction to vulnerabilities and consumer interaction with the product; work doesn't stop at launch - in some ways, it's just getting started.
I'm very at home in a CI/CD environment - they've been the usual way to run a project for the last decade.
I'm also comfortable planning a project for a CI/CD lifecycle and setting up devops requirements.
I've been using CICD since May 2012 (13 years).
Senior PHP Developer
For ASL I developed several long-lived and high volume telemetry systems. These processed large amounts of data and delivered it for rendering in charts and tables on a daily basis.
Senior Web Developer
At Vivedia I worked on high-volume API systems providing on-demand streaming video to customers. As a personal project, I updated internal systems to greatly improve the efficiency of services supporting the vital ops team.
Contract Senior Full-stack Developer
Maintenance and upgrade of a legacy native PHP 5.6 API with massive data sets to provide new functionality for clients both inside and outside the company.
Full-stack Developer / Devops Engineer
At Hidden, I filled the role of an API Developer as well as a Devops Engineer. I updated and expanded existing legacy code to run on AWS Lambda functions for increased efficiency, and created Jenkins build servers for the Unity development team.
Senior Web Developer