The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win

Category: Industries
Author: Gene Kim, Kevin Behr, George Spafford
This Month Hacker News 1


by teachrdan   2019-08-12
This is a great companion to "The Goal" and "The Phoenix Project," both of which use fictional narratives to illustrate best engineering practices in the context of saving a (fictional) business.

by franzwong   2019-01-14
No matter you want to become a manager or architect, you need to know how to run a project.

The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win

by dr_stardis   2018-11-10

[BOOK] The Pheonix Project

by dr_stardis   2018-11-10

Podcasts have been a great way for me to keep up. I mess around in my home lab too, but work and family growth eats more and more into that time (not a bad thing!). Finding ways to fill in the gaps like podcasts on commutes/exercise, reading a book instead of binge watching a whole season of Doctor Who, or using a good RSS reader to effectively follow blogs will help you prioritize what you want to play with in the lab.

As far as retention, I find I retain information the best if it is learned from breaking something or by teaching someone something new.

by dr_stardis   2018-11-10

I actually found Gartner's article .

Per the norm, this hit development and operation's technologies first with "CI/CD", "Infrastructure as Code", and "Software Defined Networks." Gartner is pointing out that the ability to automate setting up security technologies and get the configuration scripts/templates in source control is an obvious next step in full software and environment automation.

tl;dr "Software Defined Security is the solution to getting your security tools in your organizations DevOps CI/CD pipeline" is probably going to be at the top of every sales slidedeck in 2019.

by joshmarlow   2018-11-10
You may be interested in "The Phoenix Project" [0] which tries to apply some lessons from factory management to IT organizations.

My biggest take-away (and it's served me well as a team lead) is minimize work in progress (WIP). In practice, that meant encouraging contributors to focus on getting opened PRs reviewed/merged/deployed rather than opening new ones - which has cascading benefits.

A related takeaway is that when resources (engineers, key machines) are planned to be at capacity, they have no slack for dealing with unplanned work, so it's good to plan for resources to be under-utilized at certain times so that they can be more agile.

I've never seen "The Profit" but I'm looking forward to watching it now!

[0] -

EDIT: for link to book