So I've been slowly reading The Phoenix Project because I understand it's important to the history of devops. It's the most testosterone-drenched book I've read since my Tom Clancy era. It's distracting.
-
Show this thread
-
THE MAN WAS MANLY AND SAID ANGRY MAN WORDS. I SAID BURLY MAN WORDS BACK. HE BLINKED. THEN WE SAID MILITARY THINGS. WE BONDED. ANOTHER MAN ORDERED A GIRL DRINK. IT CONFUSED ME. A WOMAN WAS POWER-HUNGRY AND BAD. ANOTHER WOMAN ACTED IN A SUPPORTING ROLE TO ME. SHE WAS GOOD.
1 reply 2 retweets 17 likesShow this thread -
I've been trying to ignore it for a while but it's genuinely distracting and (as far as I can tell) serves no narrative purpose. Unless at the end they all learn a valuable lesson about how browbeating and dick-waving aren't the most effective way to run an organization.
2 replies 1 retweet 7 likesShow this thread -
Like, the organization portrayed is 100% toxic at the C-level and I'm wondering how a software delivery transformation is going to make a dent in that.
5 replies 1 retweet 13 likesShow this thread -
Have either of you read the original, the Goal? It's also all men, unfortunately, but I don't remember it having any toxicity.
1 reply 0 retweets 0 likes -
Replying to @ngauthier @avdi
I have not. People have told me it’s actually worse, so I haven’t even considered it
2 replies 0 retweets 0 likes
All three have their virtues thematically and don't really substitute for one another well. If you'd like a more serious substitute for "Phoenix" the best I've seen is Mary & Tom Poppendieck's "Implementing Lean Software Development". Highest recommendation.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
chatbots,
hearing aids.