The Phoenix Project

The Phoenix Project.

> Did you think just the audiobook wasn't better or in general it wasn't as good as The Phoenix Project? I listened to both audiobooks. Something about the paperbacks I couldn’t get in to. Now that I think about it, I don’t want to read a novel about work when I’m not at work. Also, audiobooks lend themselves really well to a commute. At any rate, the narrator of The Phoenix Project is male and the narrator of the audiobook for The Unicorn Project is female. But that’s not why I liked The Phoenix Project more. The male narrator _really_ got into the voices of the different characters, which I appreciated.

I read The Phoenix Project a while back and really liked it, have been intending to pick up the The Unicorn Project for some time now. Did you think just the audiobook wasn't better or in general it wasn't as good as The Phoenix Project?

I agree on your review of both books. Phoenix project was excellent. After years of banging my head trying to change a large org, I'm not sure you can do it head on. I found either you need incentives to change, then the org changes. e.g. Rather than encourage goal X, pay or promote teams that do X and it will happen (subject to some level of faking). Or more usually use the current org structure to affect change. i.e. play their game, then use the parts you can to make change. Trying to change an org head on never worked for me and just caused myself and otehrs great unhappiness :).

I started listening to "The Unicorn Project" on audiobook. It is not as good as "The Phoenix Project" audiobook, but it does a decent job of describing problems from the software engineer's perspective. The problem is I need a version of these books from Sarah Molton/Steve Master's point of view (a novel about being a product manager or CEO?) to better understand what motivates that side of the org. I have been mired in "The Core Chronic Conflict" for years, paying down tech debt, and turns out changing an org to learn/understand/care about DevOps is Hard.

The Phoenix Project.

That's the opposite of dry and long. Not exactly a page-turner but I think I read it in 3 or 4 sessions.

Similar theme, not great literature but still a good, quick read for people who work in tech: The Phoenix Project: https://itrevolution.com/product/the-phoenix-project/

I listened to 40 hours of Moby Dick on a series of long road trips and couldn't wait to start each one, just me and Melville for a few hours every day. On a business level, Critical Chain (Goldratt) and the Phoenix Project (Kim, Spafford, Behr) were necessary eye-openers once I got into top management.

An absolute must from a "how to think" and cultural perspective is The Phoenix Project, many years on I still think back to this frequently.

Hiya, I'd consider these books/articles/podcasts: * Secrets of Consulting by Gerald Weinberg: http://geraldmweinberg.com/Site/Consulting_Secrets.html Every problem is a people problem. * Refactoring by Martin Fowler et. al: https://martinfowler.com/books/refactoring.html talks about how and why to refactor, as well as providing a nomenclature for the process. * Code Complete by Steve McConnell. https://stevemcconnell.com/books/ A bit dated (the last version I could find was from 2004) but a great overview of the entire software process, from requirements to maintenance. * The Mythical Man-Month by Fred Brookes: https://www.oreilly.com/library/view/mythical-man-month-the/... (https://www.oreilly.com/library/view/mythical-man-month-the/0201835959/) best practices about software development, written about a project from the 1960 and 1970s. * The Joel On Software Strategy Letters: https://www.joelonsoftware.com/2000/05/12/strategy-letter-i-... (https://www.joelonsoftware.com/2000/05/12/strategy-letter-i-ben-and-jerrys-vs-amazon/) is the first one. All of them (I think there are five) are great.…

A few things come to mind along with what's already been mentioned: Assorted Non-Book Readings: - https://randsinrepose.com/dont-skip-this/ - http://www.stilldrinking.org/programming-sucks - https://sysadvent.blogspot.com/2019/12/day-21-being-kind-to-... (https://sysadvent.blogspot.com/2019/12/day-21-being-kind-to-3am-you.html) - https://donellameadows.org/archives/leverage-points-places-t... (https://donellameadows.org/archives/leverage-points-places-to-intervene-in-a-system/) - https://grugbrain.dev/ - https://changelog.com/posts/rich-hickeys-greatest-hits - https://github.com/papers-we-love/papers-we-love/blob/master... (https://github.com/papers-we-love/papers-we-love/blob/master/design/out-of-the-tar-pit.pdf) - http://www.cs.unc.edu/techreports/86-020.pdf Books: - The Phoenix Project: Gene Kim, Kevin Behr, George Spafford - Deep Work: Cal Newport - The Art of Leadership: Michael Lopp (Rands) - Extreme Ownership: Jocko Willink and Leif Babin (once you get through the ho-rah stuff it's a fantastic read) - Time Management for System Administrators: O'Reilly (fantastic for interrupt driven work) - Elements of Clojure: Zachary Tellman (not just for Clojure devs)

The Phoenix Project is a fiction novel about an IT department for a large car company that experiences management dysfunction and battles frequent technical debt, but ultimately overcomes it by adopting the best practices of DevOps. I first read its non-fiction companion book, the DevOps Handbook, which got me drinking the Kool-Aid, but this is also a wonderful, breezy read (no small feat for such a technical topic) that is an even more gentle introduction. Not only did these two books make me come to appreciate DevOps, they also taught me about Kaizen and Toyota Production Model, which DevOps began as a software translation of. Subsequently, I have also applied these principles to the field of screenwriting.

Another vote for "The Phoenix Project" and "The Unicorn Project". Both of those books are technically fiction but they are incredibly insightful into what goes all around coding and how to optimize those processes. The characters are very engaging and I found myself relating and taking ideas to improve my work/organization!

I read Phoenix Project first and then The Goal. I enjoyed both and I think that's the best order.

The Phoenix Project

Not specifically about programming, but "Every Tool's a Hammer" by Adam Savage was really good. Tons of good information in here, and it tickles the Mythbusters itch. Are you looking for books about a programming language? or about methodologies, patters, best practices, etc. As far as about specific programming languages, personally I think the internet is a far better resource. Books are better for the "Soft"er skills (communication, design, etc) Here are a few I've enjoyed: * The Phoenix Project * Accelerate * Deep Work: Rules for Focused Success in a Distracted World * Rework Finally, if you've never read "How to win Friends & Influence people", do it now! I'm 34 and for whatever reason put off reading this until last month. I wish I had read that book 10 years ago. I'll definitely be adding it to my re-read list as there is a TON of good advice for building relationships, which is arguably more important than many technical things.

The DevOps Handbook and The Phoenix Project

The Pheonix Project and The Unicorn Project are two good audiobooks centred around Devops and Software Development.

I had a really good time myself reading: The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business( https://www.amazon.com/Phoenix-Project-DevOps-Helping-Busine... (https://www.amazon.com/Phoenix-Project-DevOps-Helping-Business/dp/0988262592) )

The Phoenix Project

When managing people in tech, I think it is equally as important to know how to organize as it is to know how to lead. I would recommend "The Phoenix Project" and "The Unicorn Project" and "The Goal" to all tech managers. No matter how good your communication/leadership skills are, your team will be severely handicapped if they are working in an inefficient/limiting environment. Coming at the same lessons from a different perspective, I have also found "Turn The Ship Around!" to be a very good resource.

The Phoenix project. Everyone should read, IMO. I actually started with The Goal first. Then Phoenix project and then the Google SRE book.

In a sense, I agree with you, but TPP is specific to a software organization and I find it "translates" better, especially to the inexperienced.

Another vote for The Phoenix Project. It really helps to set the right mindset for identifying and addressing the multitude of non-technical challenges that quickly become the focus of many (I'd venture most) developers' careers.

I've read most of the recommended books, but as far as what I think has delivered immediate real value, I'm going to go with: 1) Clean Code 2) The Phoenix Project 3) UNIX and Linux System Administration Handbook I'm sure #2 will be something folks want to fight over shrug. If you want to sidestep years of headache it's a must-read though.

If you want to embrace DevOp culture, where it comes from, why is it important and the reality of medium big businnesses, then you definitely want to read the Phoenix project

It's certainly an interesting read. But very oriented towards big, conservative organisations. To me, the message was just how operations-focussed and, above all, anti-individualistic big chunks of our field have become.

Just finished it. It is a good book. I expected it to be more from sw dev point. But I was not disappointed.

The Phoenix Project. It's terrifying the parallels.

oddly enough...The Phoenix Project and Don't Make Me Think

Nobody recommended The Phoenix Project yet by Gene Kim? Unless you have some understanding of your system's architecture, how it's run in production, and why a production environment is Really Different and a Big Freaking Deal, and how operations is supposed to look like, you'll never be an effective programmer, no matter whether you run your own operations in a small start-up or work for a large enterprise with dedicated operations teams.

I didn't love this book, it was OK. It's heavily based off The Goal, and I thought that book was a bit better. I think if you have a certain dysfunction in your team AND the mandate to fix it, then The Phoenix Project is a must read. For everyone else it's kind of a waste.

The Phoenix Project by Gene Kim, Kevin Behr, George Spafford - https://www.amazon.com/Phoenix-Project-DevOps-Helping-Busine... (https://www.amazon.com/Phoenix-Project-DevOps-Helping-Business/dp/0988262592)

"The Phoenix Project" and an earlier one, "The Goal" by Goldratt https://en.wikipedia.org/wiki/The_Goal_%28novel%29

"The Phoenix Project" http://itrevolution.com/books/phoenix-project-devops-book/ is good for understanding Devops and constant refocus on business objectives.

The Phoenix Project - Gene Kim Necronomicon - Neil Stephenson