[HN Gopher] The DevOps Engineer's Handbook
       ___________________________________________________________________
        
       The DevOps Engineer's Handbook
        
       Author : MrBuddyCasino
       Score  : 111 points
       Date   : 2025-01-13 12:17 UTC (1 days ago)
        
 (HTM) web link (octopus.com)
 (TXT) w3m dump (octopus.com)
        
       | readthenotes1 wrote:
       | Sad to see test coming only after build
        
         | drewcoo wrote:
         | And only before packaging.
         | 
         | It's as if when cooking there is only one good time to taste
         | the soup.
        
       | JohnMakin wrote:
       | Glancing through this looks like a good starting point. Their
       | reading list seems solid:
       | 
       | https://octopus.com/devops/reading-list/
       | 
       | Google's SRE book changed my career, although I know it's a
       | little out of date now, it's well worth reading for the concepts
       | involved, IMO.
       | 
       | This though:
       | 
       | > With DevOps, if you can automate it, you should automate it.
       | 
       | Everyone at some level in this field understands this. I would
       | even go farther and say that _almost_ everything is automatable
       | depending on how much effort you 're willing to put into it.
       | However, lots of bad or overwhelmed devops shops I've consulted
       | seem to be stuck in this insane hell-loop of manual processes not
       | ever giving them "time" or "priority" to automate some of these
       | processes and get them off the treadmill. Usually it takes a fair
       | amount of heroics to get out of that, but I have specific
       | approach to such situations that I've been using successfully for
       | a few years now.
       | 
       | it's always important to remember "devops" is a completely loaded
       | term that can mean drastically different things depending on
       | organization.
        
         | bittermandel wrote:
         | > With DevOps, if you can automate it, you should automate it.
         | 
         | I couldn't agree less with this. At this point the whole
         | "DevOps" industry is fueled by consultancies who make a great
         | living from convincing business leaders that this is true.
         | Focusing on defining clear processes for recurring events and
         | building the fundamental building blocks that allows you to
         | automate when it's absolutely needed should be the method, not
         | spending more time writing Terraform.
        
           | alas44 wrote:
           | I completely agree, not every task deserves to be automated
        
         | roblh wrote:
         | I'm really curious, can you share even the broad strokes of how
         | you approach that? I feel stuck in that loop all the time.
        
       ___________________________________________________________________
       (page generated 2025-01-14 23:01 UTC)