2 ms·

I read The Phoenix Project a while ago, and it was pretty good to understand what DevSecOps is supposed to mean. It also convinced me that simpler processes are

by ok_dad 5y ago

I read The Phoenix Project a while ago, and it was pretty good to understand what DevSecOps is supposed to mean. It also convinced me that simpler processes are better and you add layers to those simple processes only if they are necessary. Sometimes you should accept that a more complex process might help track metrics better or might be logically better, but the simpler process is easier for everyone to grok and in that way easier to communicate about. It's been a few years since I read it but it was also entertaining to read in more of a story form than in the usual technical or managerial language.

Sebguer 5y ago
I honestly found the writing in the Phoenix Project painful, but I'm surprised you're the only one to mention it since I've heard it come up a fair bit elsewhere. I think it's probably more popular in the more traditional IT world than HN's typical audience.
- ok_dad 5y ago
  I'm not very particular about reading so I'll just steam ahead on even the crappiest books. For nonfiction books I mostly put myself in the mindset of learning or conceptualizing the content in a more abstract way, like building a mind map. For fiction, I picture the story like a movie, which distracts me from bad writing, so this book hit that sweet spot for me, personally, where I could imagine the world and the events but also conceptualize the abstract content. I actually wish I could read more technical books that have fiction and technical concepts mixed like that! Edit: Also, for as much as people complain about DevOps here, I'm amazed so few people have read this book. It's literally the book that invented DevOps as a term, right?
  - Sebguer 5y ago
    It didn't invent the term. John Allspaw and Paul Hammond maybe did, in this talk: https://www.youtube.com/watch?v=LdOe18KhtT4 https://www.youtube.com/watch?v=LdOe18KhtT4 (from the comments, I guess this talk is actually referenced in the book?) Other places credit Patrick Debois who ran the first devopsday in the same year: https://newrelic.com/devops/what-is-devops https://newrelic.com/devops/what-is-devops
    - ok_dad 5y ago
      Thanks, my memory gets a bit fuzzy after a while.

by ok_dad 5y ago

Sebguer 5y ago

I honestly found the writing in the Phoenix Project painful, but I'm surprised you're the only one to mention it since I've heard it come up a fair bit elsewhere. I think it's probably more popular in the more traditional IT world than HN's typical audience.

ok_dad 5y ago
I'm not very particular about reading so I'll just steam ahead on even the crappiest books. For nonfiction books I mostly put myself in the mindset of learning or conceptualizing the content in a more abstract way, like building a mind map. For fiction, I picture the story like a movie, which distracts me from bad writing, so this book hit that sweet spot for me, personally, where I could imagine the world and the events but also conceptualize the abstract content. I actually wish I could read more technical books that have fiction and technical concepts mixed like that! Edit: Also, for as much as people complain about DevOps here, I'm amazed so few people have read this book. It's literally the book that invented DevOps as a term, right?
- Sebguer 5y ago
  It didn't invent the term. John Allspaw and Paul Hammond maybe did, in this talk: https://www.youtube.com/watch?v=LdOe18KhtT4 https://www.youtube.com/watch?v=LdOe18KhtT4 (from the comments, I guess this talk is actually referenced in the book?) Other places credit Patrick Debois who ran the first devopsday in the same year: https://newrelic.com/devops/what-is-devops https://newrelic.com/devops/what-is-devops
  - ok_dad 5y ago
    Thanks, my memory gets a bit fuzzy after a while.