Many developers would love to work on brand-new, cutting-edge, greenfield projects, never having to deal with the mess of unintelligible code someone else left behind. But most of us spend most of our time maintaining existing code, and it is often spaghetti code with no unit tests, no documentation, and, if we are lucky, a comment that says, “Not sure how this works, but it does so don’t touch it.” We need to make changes, but we can’t even figure out what the code is supposed to do. You know your changes are just going to pile on and make it worse. You can’t change the code safely...
Gene Gotimer
DevSecOps Senior Engineer
Steampunk
Gene Gotimer is a DevSecOps engineer at Steampunk, often working with federal government clients. He considers himself a developer, but he usually focuses on DevSecOps practices such as continuous integration, repeatable builds, unit testing, automated testing, security tools, and automated deployments. Gene feels strongly that repeatability, quality, and security are all strongly intertwined; each of them is dependent on the other two, which just makes agile and DevSecOps that much more crucial to software development.