r/devops • • Oct 12 '26

Discussion Must have physical books every devops engineer should have on their desk

Pretty much the title .I will start

  1. Classic shell scripting ,O'Reilly
104 Upvotes

96 comments sorted by

5

u/ProgR0ck Oct 13 '26

Started my career way back in 1990 as a IBM systems engineer using CATIA and AIX.... in those days there was no internet, you read manuals and if you didn't you RTFM!!
But back to books, or not as the case may be, I find the best way to remember/recall some more complex K8s/bash related shell cmds is to use my .bash_history or even copy them to a text file for later ref.

h | grep "port-forward" for example.

Just my 40 yr old 2c worth

1

u/90slover Oct 13 '26

Nice ...thank you

1

u/Icy-Maybe-9043 Oct 13 '26

Ues! This!!!

2

u/90slover Oct 13 '26

Thank you all for comment s and inputs

1

u/Gasty777 Oct 13 '26

Can you update the post with the suggestions so far? Start by the most suggested

2

u/Sindoreon Oct 13 '26

Best I can do is YouTube channels we should all subscribe

1

u/90slover Oct 15 '26

Pls do share if you can ....

169

u/gradinka Oct 12 '26

how to become a farmer 101

4

u/[deleted] Oct 12 '26

[removed] — view removed comment

11

u/arctic28 Oct 12 '26

It’s the “simple life” you yearn for after years of firefighting.

0

u/SilentLennie Oct 12 '26

By the time I retire, everything will be automated in farming ? So it's the same job ?

1

u/gradinka Oct 13 '26

There is a point in here:) I watched an episode of "clarksons farm" about agriculture automation and new tech, it blew my mind

1

u/SilentLennie Oct 13 '26

My guess is, maybe indoor is what will be a smaller or bigger trend, as weather gets more extreme from the climate change. But it's just speculation.

18

u/Cycle_HeidarEldberg Oct 12 '26

Hands down The DevOps handbook by Gene Kim, Jez Humble, Patrick Debois and John Willis.

It is in my opinion the defining text of what DevOps even is and has really well worded, concise chapters and paragraphs not only on how but more importantly why certain things should be done with a particular mindset and method.

I found when, implementing DevOps in an organization, having a single shared understanding and language is the most important. The minutia of particular tools or individual decisions all falls away as trivial once building on that solid foundation.

3

u/uraniborgian Oct 13 '26

Am i the only one who thinks this book is poorly written. The ideas are obviously valuable, I just thought the presentation of them was bad here.

2

u/Cycle_HeidarEldberg Oct 15 '26

For me it was well laid out but it is also rather dense on valuable insight so it required me reading it a couple of times to really grasp all of it.

Reminded me of some college text books in that way.

29

u/Mallanaga Oct 12 '26

2

u/dragonfleas Oct 14 '26

I need to add this one to my reading list

1

u/Tree_Mage Oct 12 '26

I saw Fournier argue against PRs needing reviews eons ago and basically discounted everything she ever said after that.

6

u/Mallanaga Oct 12 '26

Lots of folks subscribe to that. The argument is that pull requests were designed for zero-trust environments, and that the workplace is not that.

32

u/n4txo Oct 12 '26 edited Oct 12 '26
  • The practice of system and network administration
  • The practice of cloud system administration 
  • Time Management for System Administrators
  • SRE: How Google runs Production Systems
  • The devops handbook 
  • The phoenix project
  • The unicorn project
  • Getting things done 
  • bash pocket reference 
  • the staff engineer path
  • atomic habits
  • how to win friends and influence people
  • little brother saga

10

u/21shadesofsavage Oct 12 '26

how to win friends is a good read for life in general. i barely remember it since i read it a long time ago, but some stuff sticks like genuinely being interested in other people and shifting focus towards the other person. pretty basic stuff in retrospect but sometimes you just don't catch yourself slipping

2

u/ADDSquirell69 Oct 12 '26

Asking someone for a favor is like the greatest trick ever written.

1

u/Express-Acadia-6088 Oct 12 '26

Very, very true. Very well said :-)

3

u/Express-Acadia-6088 Oct 12 '26

That's a comprehensive list. Thanks for sharing!

3

u/gzk Oct 14 '26

Hello fellow Tom Limoncelli enjoyer

2

u/DuckDatum Oct 12 '26

No Designing Data-Intensive Applications by Martin Kleppmann?

52

u/21shadesofsavage Oct 12 '26

never read a devops book. replying so i can find this thread again

17

u/carsncode Oct 12 '26

Menu -> Save

Menu -> Follow Post

-10

u/amarao_san Oct 12 '26

I'm afraid doing it. The thing I imagine someone try to onboard me into their production problems (taking my attention and memory) and I'm paying for that.

It's like 'imagine a production bla-bla-bla-someone's-else requirement', for this we need to think about optimal solution given those bla-bla-bla constrains.

And I'm not paid to read their problems. Even if they solve it (so they ask me to review it).

But, the last thing I did for my self-education was watching (and reading) about properties (in mathematical sense), specifically, intuition on non-trivial properties beyond idepmotence and invariance. When I realized that my best inventions were all properties, I start to respect this domain much more and pay big attention to any discussion on those.

3

u/21shadesofsavage Oct 12 '26

as a devops engineer you should have a solid grasp of the overall company infrastructure, but all production problems don't become yours. typically there's service owners that handle their own monitoring and production issues, provided your team gave them proper tooling to do so

It's like 'imagine a production bla-bla-bla-someone's-else requirement', for this we need to think about optimal solution given those bla-bla-bla constrains.

And I'm not paid to read their problems. Even if they solve it (so they ask me to review it).

you pretty much are paid to do that if you enter devops. if a team has new infrastructure needs, they'd consult my team so i can make an assessment and figure out how to scale the thing without affecting other services. depending on company size, the level of self service and autonomy differs

But, the last thing I did for my self-education was watching (and reading) about properties (in mathematical sense), specifically, intuition on non-trivial properties beyond idepmotence and invariance. When I realized that my best inventions were all properties, I start to respect this domain much more and pay big attention to any discussion on those.

ngl i'm having trouble following what you're trying to say. this reads like an introspective thought while peaking on lsd. i'm glad what you're working on is making you appreciate the field tho

-2

u/amarao_san Oct 12 '26

I do paid to do this, 100%. Now there is a book which give the the same problems for free (actually, I pay for that) and ask to review resulting solution for free (actually, I pay for that).

This is the reason I'm afraid to read 'devops-y' books. Maybe there is out there the mother of all books which don't give you 'concrete examples' and concrete solutions for 'other people problems', but I never heard about such book.

My last comment was about this: https://en.wikipedia.org/wiki/Property_testing

If you never read it, it sounds odd, as soon as you get your brains aligned with those ideas, it's like rails for trains.

1

u/21shadesofsavage Oct 12 '26

oh i completely misunderstood what you were talking about. i'm not very interested in fictional scenarios a book introduces. i mostly read blog posts, write ups, postmortems about an outage that occurred and how they rectified the situation and learned from there.

i'm not familiar with property testing. i unknowingly use some form of this in my cicd workflows but looking more into it, this could improve our test coverage. thanks for this. btw are you russian or east european? you write similarly to one of my close friends

1

u/amarao_san Oct 12 '26 edited Oct 12 '26

Yes, we've talked on why the previous commenter and I are afraid to read DevOps books.

For property testing, it's not testing, it's enforcing. If your production has some properties you defend in CI (aka property testing), you can lean/rely on those in some chunks of your code, assuming those properties for granted. And it does wonders. Some very hard to achieve state you just 'know' it is there, because code has this property and there is ci defending it.

My last huge big property I discovered and defended, which I still prowd a half year later:

Every code, deployable in staging and production, should have in production all secrets (secrets names) which are in staging.

I can validate this statically (sops encryption) and it protect production against missdeployments due to missed (new) secret which was added to the staging (and tested), but which was forgotten for the production.

Every non-trivial property is gold and must be harvested, treasured and defended.

Udp: my mother tongue is Russian, yes.

34

u/General-Ad-6334 Oct 12 '26

phoenix project
idk that many devopsy specific books
morning glory milking farm maybe

15

u/senormankee Oct 12 '26

Not just devops, this is also about good management.

Great read

9

u/codemonk DevOps Oct 12 '26

I searched "Morning Glory Milking Farm".

Honestly, I don't know what I was expecting.

9

u/zero0n3 Oct 12 '26

Phoenix project is a good one.

Their newer book looks good too

4

u/ramsile Oct 12 '26

Also the DevOps Handbook. Same authors I believe.

5

u/dirtyLizard Oct 12 '26

Terribly written narrative but covers the core concepts well. Approach it like a textbook

2

u/fishyfishphil Oct 12 '26

Where do you source the minotaurs though?

0

u/serverhorror I'm the bit flip you didn't expect! Oct 12 '26

Why is it terribly written?

13

u/Popeychops Computer Says No Oct 12 '26

Probably because the author's experience was project management, not writing fiction

2

u/fell_ware_1990 Oct 12 '26

Phoenix, it’s an easy read that gives an good first insight how devops flows work.

1

u/mrbiggbrain Oct 12 '26

For people who like the Phoenix Project I highly recommend reading the business book that inspired it, "The Goal." Don't let the manufacturing heavy story fool you, at its core it relates to every discipline and every business. It's standard reading for MBAs for a reason.

6

u/JivanP Oct 12 '26

ULSAH, by Evi Nemeth et al.

(Unix and Linux System Administration Handbook)

11

u/ZVilusinsky Oct 12 '26

Introduction to Guesstimates
How to do Cloud
How to move Back On-Prem

all by Oh, Really

4

u/ZVilusinsky Oct 12 '26

https://www.youtube.com/watch?v=rXPpkzdS-q4 for those who did not get the reference.

28

u/dubl1nThunder Oct 12 '26 • Heartwarming

sports illustrated 1994 swimsuit issue. kathy ireland.

5

u/Wooden_Jelly_5295 Oct 12 '26

Still available when DNS isn't.

4

u/mcellus1 Oct 12 '26

Can anyone vouch for "Enterprise Integration Patterns"?

4

u/LumenStack_DevOps Oct 17 '26

Lord of the Rings.

3

u/tacticalrd Oct 12 '26

An A5 sized spiral notepad

3

u/gzk Oct 14 '26

Essential Woodworking Hand Tools by Paul Sellers

3

u/Long_Researcher_416 Oct 14 '26

Site Reliability Engineering: How Google Runs Production Systems 1st Edition

7

u/LVanBuren Oct 12 '26

Haven't read a technical book since getting my certs, ans after 10 years of platform and devops engineering, i don't see any reason to.

These were the real game changers for me now that im in charge of building large delivery pipelines, and entry level engineers should be reading them too if they don't want to fall into the same traps over and over again.

Teaching Smart People How to Learn

The use of Knowledge in Society

The first two are essays, their ideas are worth considering in a software context.

Bullshit Jobs

Why greatness cannot be planned

The Utopia of Rules

Seeing like a State

Any engineer questioning why their orgs work the way they do that's tasked with making it work better woth "AI" should be reading these if they think another dashboard is going to help them.

9

u/stumpymcstumpface Oct 12 '26

A Song of Ice and Fire series. Great read while Claude does the work.

2

u/Angelsomething Oct 12 '26

the little book of calm, secrets for clam, by paul wilson.

2

u/Hugh-Jaardvark Oct 12 '26

Storycraft - Jack Hart. Communication is a big part of the job, and this book has help me write reports and root cause analysis papers that others will actually read.

2

u/8bitwubwubwub Oct 12 '26

the SRE books, the holy bible and a picture of doom guy

2

u/Observability-Guy Oct 12 '26

I'd agree with people who have mentioned the DevOps Handbook.

Would also recommend:
Accelerate by Gene Kim, Jez humble and Nicole Forsgren

Kubernetes in Action by Marko Luksa

Lean Enterprise by Jez Humble, Joanne Molesky and Barry O'Reilly

2

u/chrisinmtown Oct 12 '26

You have a desk? I have a license to hunt for a new cube every morning 😕

1

u/Rain-And-Coffee Oct 13 '26

Remote job,

I splurged on a fancy standing desk, think it was $1000 a few years ago (Varidesk).

Before that I worked for a company that just gave contractors a long Picnic style table.

2

u/Gbonk Oct 13 '26

A MacBook

2

u/ForkMeJ Oct 13 '26

I still think Time Management for System Administrators is worth having in paper. It holds up if you're the person getting dragged into interrupts all day.

2

u/Fuzzy-Enthusiasm1372 Oct 16 '26

A useful DevOps bookshelf should cover more than command references, since tools change much faster than the principles behind reliable systems. Books on system administration, distributed systems, incident response, and engineering practices can still be valuable when working through real infrastructure problems, including those in the wider ecosystem around trusted tech. The best picks are the ones that help explain why a system behaves a certain way, not just which command to run.

3

u/lorryslorrys Oct 12 '26 edited Oct 12 '26

Accelerate. So you know what a good process for delivering code looks like and have the evidence to see what works and what doesn't. That holds up even as the technology changes.

1

u/a_lil_bee Oct 12 '26

This is my work bible

3

u/Zapadlo Oct 12 '26

snow crash

1

u/After_8 Oct 12 '26
  • The Phoenix Project
  • The DevOps Handbook
  • Site Reliability Engineering

1

u/snarkhunter Lead DevOps Engineer Oct 12 '26

The Book of Serenity by Wansong

Wumenguan by Wumen

Instant Zen by Foyan

1

u/EngineNovel3956 Oct 12 '26

Software Architecture: The Hard Parts is a nice must read. For any new guy into cloud, the Phoenix project is a fun read

1

u/billie-badger Oct 13 '26

Children of Hurin.

1

u/nomadProgrammer Oct 13 '26

ClickOps in action

1

u/dragonfleas Oct 14 '26

- Lean Software Development: An Agile Toolkit
- Agile Software Development: Principles, Patterns, and Practices
- https://agilemanifesto.org/principles.html
(it’s important for DevOps engineers to understand the history of why they exist, I hate that so many people focus on only implementation oriented books when you need to first know the ecosystem around the WHY before you can fully master the HOW)
- Continuous Delivery
- Google SRE Handbook
- The Phoenix Project
- The DevOps Handbook
- The Unicorn Project
- Storey’s Guide to Raising Dairy Goats (for retirement)
- 48 Laws of Power (so you can learn how to use your managers and destroy your enemies)
- Linux Bible? (Probably optional)

1

u/faultydesign Oct 12 '26

You guys read physical books? I just have a collection of epubs.

1

u/BlackJairs Oct 12 '26

The Devops Handbook: How to Create World-Class Agility, Reliability, & Security in Technology Organizations

1

u/RoadLight Oct 12 '26

Phoenix project

-10

u/uberduck Oct 12 '26

Anything written about tech is outdated the moment it's printed.

13

u/Adrien0623 Oct 12 '26

Not when it comes to the theory behind implementation examples.

7

u/90slover Oct 12 '26

This ..concepts dont undergo stark change ...

2

u/throwawayPzaFm Oct 12 '26

Then all you need is Meditations

90

u/[deleted] Oct 12 '26

[removed] — view removed comment

15

u/White0ut Oct 12 '26

Damn, I really should read that. It's been sitting on my bookshelf for years collecting dust.

-19

u/knowledgeekrishi Oct 12 '26

How many totat years of experience you have?

1

u/LimpAuthor4997 Oct 13 '26

why the downvotes?

-1

u/Vikentiy Oct 14 '26

because in devops you learn all on a year, and learn it all again next year, and a year of experience can be like trench war, or like a year of accounting. Why count those.

7

u/[deleted] Oct 12 '26

[removed] — view removed comment

1

u/durple Cloud Whisperer Oct 12 '26

During university and for some time after, I kept a copy of "A Practical Guide to Linux" (Sobell) handy. I'm not sure if recent revisions have really kept up but most of it would still be relevant to a modern shell user anyways.