I think every dev should read Gene Kim's The Phoenix Project. Not just "bc devops", but to understand their work's release pipeline as a system that can be optimized in various ways in order to deliver a better product, faster. Getting the bigger picture of how the code we write actually gets to the customer helps us understand the true importance of practices like TDD and automation (test/process/review) etc. Our nature is to reduce waste and duplication in our own processes (tool building, scripting repetitive things) and I personally experienced an A-HA moment reading that book and expanding that idea outside of my personal zone of control.
Also, its a great story and helped me realize that the incompetence and waste I saw everywhere in my org wasn't unique ;)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think every dev should read Gene Kim's The Phoenix Project. Not just "bc devops", but to understand their work's release pipeline as a system that can be optimized in various ways in order to deliver a better product, faster. Getting the bigger picture of how the code we write actually gets to the customer helps us understand the true importance of practices like TDD and automation (test/process/review) etc. Our nature is to reduce waste and duplication in our own processes (tool building, scripting repetitive things) and I personally experienced an A-HA moment reading that book and expanding that idea outside of my personal zone of control.
Also, its a great story and helped me realize that the incompetence and waste I saw everywhere in my org wasn't unique ;)