this post was submitted on 27 Jul 2023
82 points (100.0% liked)
Asklemmy
43917 readers
1166 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The Phoenix Project
This book is sitting in our office. Is it actually a good read? Its very dusty so I always wrote it off as just another corporate book.
It basically created "Devops" as a mindset. You decide if thats a good or bad thing.
Id personally call it a good book. The first half will hurt you if youve ever worked as a sysadmin, as it basically recreates all the worst parts of the job at once to setup the story, but the second half explains how devops as a thought process can solve the issues it creates. It does not going into tools, just methods and concepts.
It can help you fix your orgs bullshit. It is heavy on "you need management buyin" angle though, so if you cant get that at your job, continue to abandon all hope.
I enjoyed it.