42. "Ancient" is a very relative term when it comes to software and protocols. 43. "Obsolete" doesn't mean it's not in use and relied on.
-
-
60. Your herculean efforts to upgrade the OS across your entire fleet completed just in time for the EOL announcement of the version you upgraded to. 61. This phenomenon was first described in Dante's Inferno as the Ninth Circle of Hell, Ring Four, aka RedHat Canto XXXIV.
Show this thread -
62. Containers create at least as many problems as they solve. 63. The most ninja move the expert you hired for that third party black box product you rely on is to say "Let me ping the support team".
Show this thread -
64. Somewhere, somebody ran into this exact problem, but they never bothered to post a solution. 65. That completely automated solution you set up requires at least three manual steps you didn't document.
Show this thread -
66. CAPEX budget always increases, OPEX budget always decreases. 67. CAPEX costs can be reasonably estimated, OPEX costs can only be ballparked.
Show this thread -
68. Doubling your time estimate in the hopes of beating expectations won't work because your manager takes your estimate, has a hardy laugh, and then resets it back to what they already promised upchain.
Show this thread -
69. Your quarterly planning means bubkes when the next re-org rolls around. 70. Most of your actual work is not covered by your OKRs.
Show this thread -
71. Recursively applying the Pareto Principle is a surprisingly accurate way to gauge your low hanging fruit, determine your high impact objectives, and ballpark your required effort. 72. Although, to be honest, it only works in about 80% of cases.
Show this thread -
73. Management will always happily spend $$$ on outside consultants to tell them what you've been saying for years. 74. Management will much rather invest in inventing a new, square wheel than fixing an old round one.
Show this thread -
75. In any organization practicing continuous integration, half of all commits are to fake out CI tests.
Show this thread -
76. Good software development practices do not always translate well to ops and friends. 77. Mandatory code reviews do not automatically improve code quality nor reduce the frequency of incidents.
Show this thread -
78. Every new paradigm tends to mostly add layers of abstractions; cutting through them and identifying what basic principles continue to apply is half the battle.
Show this thread -
-
80. "Prod" is just another name for "staging". 81. Your source of truth lies. 82. Also: it's incomplete.
Show this thread -
-
-
85. Multithreading is rarely worth the added complexity. 86. Parallelism is not Concurrency. 87. Simplicity is King.
Show this thread -
...and finally... 88. Nobody knows what exactly it is you do.
Show this thread -
This thread as a single HTML page: https://www.netmeister.org/blog/ops-lessons.html … Peace out, nerds!
Show this thread
End of conversation
New conversation -
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.