Guru Meditation
    ____  ____   __   ____ ___ _____ ___  ____   ____ 
   |___ \| ___| / /_ | __ )_ _|_   _/ _ \|  _ \ / ___|
     __) |___ \| '_ \|  _ \| |  | || | | | |_) | |  _ 
    / __/ ___) | (_) | |_) | |  | || |_| |  _ <| |_| |
   |_____|____/ \___/|____/___| |_(_)___/|_| \_\\____|

  1. Absence of a signal is itself a signal
  2. Nobody wants backups, everybody wants restores.
  3. The severity of an incident is measured by the number of rules broken in resolving it.
  4. The only other person who knows how this works is also on vacation.
  5. Turning things off permanently is surprisingly difficult.
  6. Big data is much bigger than you think. Think carefully before using Big Data solutions for solving your problems.
  7. Using cloud infractructure is in an very high number of situations a expensive an inflexible approach.
    If you are serious about the non functional attributes of your system, it has a huge impact on your software- and system-architecture.
  8. Without having a strong IT governance/strategy, the technology hipsters and product owners will efficently implement a cloud platform vendor lockin.
  9. Do not run your GIT services on the same cloud, you are running your production system.
  10. If your corporate IT is slow or horrible, the cloud can save your ass.
  11. strace(1)/ktrace(1) doesn't lie. Unless somebody's been playing LD_PRELOAD games.
  12. If they promise you to implement and rollout the "security things" after project launch, accept that it's not gonna be good anymore.
  13. You're bound by the CAP theorem much more often than you may think.
  14. The hardest problem in sre is fighting the urge to solve a different, more interesting problem than the one at hand.

THE SRE WISDOM   [github scoopex]