4. The mobile hotspot you're paying for so you can leave your house while you're oncall only works at home and in the office. 5. The only other person who knows how this works is also on vacation.
-
-
23. Serverless isn't. 24. Y38K is already here, it's just not evenly distributed. 25. If you determine "human error" as the root cause, then you're doing it wrong.
Prikaži ovu nit -
26. Your network team has a way into the network that your security team doesn't know about. 27. And don't even as much as mention the serial console and IPMI networks, but boy are you glad you have 'em.
Prikaži ovu nit -
28. Blocking TCP port 53 traffic leads to very strange failures. Don't. 29. Somewhere in your infrastructure a service you didn't know uses DNS for endpoint discovery in a very surprising way. 30. Do
Not
Monkey
Around
With
/etc/hosts.Prikaži ovu nit -
31. If you break it, you own it - for now; if you fix it, you own it - forever. 32. Turning it off and on again is actually quite a reasonable way to fix many things. 33. A http://README.md in git is no substitute for a manual page that's shipped with your tool.
Prikaži ovu nit -
34. A search for a document you know exists will only turn up links to documents referencing but not actually linking to the one you're looking for.
Prikaži ovu nit -
35. The document you're looking for was marked as obsolete and not migrated to the new content management solution. 36. Sure, your current content management system sucks, but it's still better than the one you're moving to.
Prikaži ovu nit -
37. Nobody knows how git works; everybody simply rm -fr && git checkout's periodically.
Prikaži ovu nit -
38. There are very few network restrictions creative and determined use of ssh(1) port forwarding can't overcome. 39. This is both incredibly useful and concerning.
Prikaži ovu nit -
40. It is tempting to jump right into implementing a solution when the right thing may well be to not do the thing that requires the solution in the first place. 41. Turning things off permanently is surprisingly difficult.
Prikaži ovu nit -
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.
Prikaži ovu nit -
44. The sets of systems online before and after a data center power outage only intersect. Some of the old systems coming online will immediately cause a different outage.
Prikaži ovu nit -
45. Some of your most critical services are kept alive by a handful of people whose job description does not mention those services at all.
Prikaži ovu nit -
46. After the initial "down for everybody or just me ermahgehrd Slack is down" drop, productivity increases linearly throughout the the duration of the outage.
Prikaži ovu nit -
47. You're bound by the CAP theorem much more often than you may think. Halting Problem's a bitch, too. 48. Eventual consistency doesn't help when the system you're debugging hasn't converged yet.
Prikaži ovu nit -
49. The source you're looking at is not the code running in production. 50. strace(1)/ktrace(1) doesn't lie. 51. Unless somebody's been playing LD_PRELOAD games.
Prikaži ovu nit -
52. Schrödinger's Backup -- "The condition of any backup is unknown until a restore is attempted." -- is overly optimistic. 53. There's an xkcd for the precise situation you find yourself in. (There's also one for at least half of these.)
Prikaži ovu nit -
54. At some point in your career you will implement half of kerberos. Poorly.
Prikaži ovu nit -
55. Any sufficiently successful product launch is indistinguishable from a DDoS; any sufficiently advanced user indistinguishable from an attacker. 56. Debugging any sufficiently complex open source product is indistinguishable from reverse engineering a black box.
Prikaži ovu nit -
57. "We've always done it this way." is not a good reason by itself, but there's bound to be one for why. 58. That reason may or may not be valid any longer, however.
Prikaži ovu nit -
59. A junior engineer asking "why" and pointing out the docs don't reflect reality is at least as valuable as the senior engineer working blindly off tribal knowledge.
Prikaži ovu nit -
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.
Prikaži ovu nit -
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".
Prikaži ovu nit -
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.
Prikaži ovu nit -
66. CAPEX budget always increases, OPEX budget always decreases. 67. CAPEX costs can be reasonably estimated, OPEX costs can only be ballparked.
Prikaži ovu nit -
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.
Prikaži ovu nit -
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.
Prikaži ovu nit -
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.
Prikaži ovu nit -
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.
Prikaži ovu nit -
75. In any organization practicing continuous integration, half of all commits are to fake out CI tests.
Prikaži ovu nit -
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.
Prikaži ovu nit - Još 8 drugih odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.