The original post was on "The Phoenix Project" Must Read For Developers - Reading Time: 4 Mins and cover image by Lenny Kuhne on Unsplash
...
For further actions, you may consider blocking this person and/or reporting abuse
The follow up, The Unicorn Project is a great addition to this. It gives a new insight into Parts Unlimited and the politics of the time.
😂 I'm still going through the book "Phoenix Project". I might take a while for me to complete reading it.
Its the same story but from the point of view of one developer when she is transferred over to the Phoenix Project to serve as temporary scape goat for the latest systems failure. I read both books. Would recomend for any devs out there. If you have to choose which to read, as a dev read The Unicorn Project.
Nice alright I'll look at it. Looks like my number of backlog of books is increasing.
Tell me about it!
Also The Toyota Way is next on my list!
Awesome i really like it as they the poster child which inspired the agile movement for us due to their lean manufacturing concepts.
You should check out Accelerate then. It's a less fun read than the Phoenix Project, but it explains the methods the State of DevOps reports use to determine best practices. It's the kind of book that will help you determine what the next, best practices are when the DevOps Handbook falls out of date.
Yup I subscribe to the Puppet's state of DevOps. It's good. I have not heard about that "Accelerate" book, is it by the same author or someone else?
Two of the authors of the DevOps handbook partnered with Nicole Forsgren to write the book - it's available here amazon.com/dp/B07B9F83WM/ref=dp-ki...
Nice it was not in my purview I will take a look that.
He is one of the authors of the book.
I work "in DevOps" and The Phoenix Project is required reading for anyone who wants to be a DevOps Engineer. It's super fun and you get to work with a lot of cool tools, but everything you do has to bring some value.
In fact, when disagreeing with another DE about something, the easiest question to ask is "what value does this provide?" If they can articulate why, the we'll go with it. If they can't, then they understand why the solution wasn't the right choice at the time. This also provides opportunities for collaborative development of best practices and is overall a positive for the team, IMHO.
The best part of working in DevOps is that you not only get to improve the lives of developers with efficient pipelines and self-service tools, but you can actually improve the entire company.
Anything that makes the business run more efficiently, faster with less labor, or eliminates toil will ultimately allow the collective efforts of the teams to produce better software faster.
DEV user @pirxdanford does a great job of explaining the CALMS model (previously CAMS) which is the guiding principle of DevOps, IMHO.
dev.to/pirxdanford/calms-a-holisti...
Yes that's great!! Cause sometimes I wish there were more developers or DevOps engineers who reads it. Like for example of my ex co-worker, he literally took whatever my senior software engineer says. As words from God but did not think about it. To make it easier to work on deploying it into our testing and production server but choose to do everything manually without scripts to automate it to reduce the time taken.