“If you plan for the worst, all surprises are pleasant.”
Gaul in “The Wheel of Time” by Robert Jordan
I read an interesting article that was just published in the “Communications of the ACM” by Ariel Tseitlin. It’s titled “The antifragile organization”. He talks how they deliberately induce failure in the infrastructure to test whether the system is resilient enough (due to redundancy and fault tolerance) to deal with it. It’s an interesting text in it’s own right — the idea of running programs that deliberately but reversibly damage the infrastructure is impressive, e.g., terminates virtual instances, connections to data centers, or (in the future) even entire regions. They put their infrastructure under stress to see whether it is resilient when real failures occur. And in case something goes wrong(er than expected), they can terminate these programs anytime (in contrast to real failures).
I think this approach is applicable to one’s own personal infrastructure — everything from an accidentally deleted files, selective or full loss of network connectivity, forgotten/lost display adapters in presentations, hard-disk crash, theft, or the apartment burning down.
These things are (usually) pretty rare, giving us few ‘opportunities‘ to test our resilience. Of course, at times we think about worst cases (and probably do backups or that second check if the video adapter is really in the bag), but it’s not introduced randomly. And sure, if you try to prepare for everything you won’t have time for anything else (e.g., work) and probably become pretty paranoid. But a few things should be prepared against.
It would be nice if there was an App which would run in the background and give you — at times — a simulated scenario (e.g., “the file you are working on at the moment was not saved correctly and is corrupted — it is beyond repair”) and let’s you deal with it for a moment. If you don’t have the time in the moment, you can ask for it to occur later, but if you take the time you can ask the right questions: Now what? Is that a problem for me? Do I have prior versions saved? How much work is lost since I last created a prior version? Would I be able to finish my work on time if it had really happened? You could then tell the app that you would have dealt with it/would be a non-problem (that problem would occur less frequently) or that it would have been a serious problem (which would create a todo task to find a solution in the future). Hmm, I’ll probably include such a function in my Task Manager App (if I ever come to programming it, the planning stage is almost finished).
Even if that event never happens, chances are, over time you become better in solving problems and are more relaxed and competent when real problems arrive.
Until then, you can do the following. Take a book, any book that has page numbers. Close your eyes and flip through the pages. Depending on the last number select one of the areas (that should reduce Benford’s Law). Then do it again to check the concrete case (due to the numbering style, 10 = zero here).
- Interrupted Morning Routine
- Your cellphone/smartphone is empty (e.g., did not charge over night).
- Your deodorant is empty (no reserves).
- There is no hot water.
- There is no water at all (pipes did break somewhere else).
- There is too much water (pipes did break somewhere near, very near).
- You are delayed 15 minutes (e.g., spilled something that has to be cleaned).
- You are delayed an hour (e.g., overslept).
- You can’t find your keys.
- You can’t find unwashed clothes.
- Your bootlace breaks.
- Your car does not start./Your usual means of transportation are delayed for an hour.
- Your car stops working on the road (or the train breaks down).
- Your car is gone./Your usual means of transportation is unavailable for the day.
- Your car has a smashed in window (and everything valuable was stolen).
- There is a serious traffic jam (or all trains are delayed for an hour).
- You get into a car/train crash.
- You arrive at your destination, your luggage took the long road (delayed for a day).
- You arrive at your destination, your luggage vanished on the way.
- You hand-luggage is gone (e.g., stolen, or lost due to an accident).
- You arrive in the wrong city (e.g., overslept in train, plane had to be re-routed).
- Physical/Virtual Access
- The office door won’t open.
- The building cannot be entered for an hour/day (fire alarm).
- The building is gone (e.g., fire).
- There was a break-in, everything valuable in your office was stolen.
- Another room you use is not available for the day.
- A whole section of the building and its technology is not available for the day (including servers).
- Intranet does not work for an hour.
- Intranet does not work for the day.
- Internet does not work.
- All cloud data is gone/corrupted (data center burned down, hacking, etc.).
- Personal Access
- Your boss is unexpectedly unavailable for a few hours (despite his/her promises that s/he would be there) and you need his/her signature.
- See 1, but for the day. Can be reached virtually (phone, eMail).
- See 2, but cannot be reached virtually (e.g., was involved in accident).
- Your boss died. [might come across wrong, but it happened to a PhD I know of, her supervisor died during her PhD]
- Someone who works for you is unexpectedly unavailable for a few hours and you need this person’s input.
- See 5, but for the day. Can be reached virtually (phone, eMail).
- See 6 but cannot be reached virtually (e.g., was involved in accident).
- The person who works for you died. [again, might come off wrong, but accidents happen, that’s the point]
- A collaboration partner quits suddenly and irrevocably (e.g. fraud case, bankruptcy, etc.).
- The one person who knows the workings of the office inside out (usually, the secretary) cannot be reached for the day/week/month or is completely unavailable.
- Your battery is suddenly empty during the day.
- Your cellphone/smartphone gets misplaced for an hour.
- You lose your cellphone (and it will never come back).
- Your cellphone is stolen by someone with evil intent.
- The data on your cellphone is wiped.
- You have no cellphone connection.
- You have no Internet connection.
- Your Internet connection is excruciatingly slow.
- You battery will be empty in 10 minutes.
- The last used App is gone/deleted/corrupted.
- Your notebook battery dies (no power cable/plug).
- You do not have access for an hour (important systems check/virus scan).
- You do not have access for the day (non-memory related technical issue).
- The hard disc crashed (all data lost on the device).
- Your notebook is stolen (and won’t come back).
- Your notebook is stolen by someone with evil intent [any personal photos or “inappropriate” diary entries? Or data that could help the competition if given/sold to them?].
- Your writing software does not work.
- Your data is corrupted (and was for the last three backups).
- The file you are working on at the moment is suddenly broken.
- The notebook switches off suddenly (all unsaved information is lost).
- Someone breaks into your home and steals all valuables.
- Someone breaks into you home (with evil intent).
- Your home is gone (e.g., fire).
- Your home is suddenly inaccessible for a day (e.g., environmental issue/natural disaster without time prior to evacuation).
- Your home will not be accessible again for a day in 30 minutes (e.g., environmental issue/natural disaster).
- Your home is suddenly not accessible for a week or month (e.g., environmental issue/natural disaster without time prior to evacuation).
- Your home will not be accessible again for a week or month in 30 minutes (e.g., environmental issue/natural disaster that gives you 30 minutes prior to evacuation).
- Your house is on fire — you have 2 minutes [fire detector anyone? most people die due to the smoke that kills you while you sleep — you can get them on Amazon — with a magnetic holder to glue it to the ceiling and allow removal, worth a thought].
- Your house is on fire — you have only access to the room you are in for 2 minutes.
- Your house has to be sold/you lose your apartment.
- You have sore muscles and move at half speed.
- You have a problem with your back and cannot bend or sit down.
- You break your right arm.
- You break your left arm.
- You break both arms.
- You break your leg(s).
- You have a splitting headache/migraine.
- You are confined to the hospital for the day (telephone, no cellphones allowed).
- You are confined to the hospital for a month (telephone only, no cellphones allowed, you might get your/a laptop, if someone can bring it to you).
- You have a serious accident and are unconscious for a week/month (or even die).
- You lose your wallet.
- You lose half of your savings.
- You lose all of your savings (e.g., due to bank fraud).
- You lose access to your credit card.
- You lose access to your credit card (while being in another city/abroad).
- You lose access to money that is dependent on banks (e.g., due to an accounting error you suddenly have a very bad credit rating).
- You need money for an important medical procedure (what would be a problem: $500, $1000, $2000?).
- and higher: redo
- Public Issues (you have a presentation/important meeting soon)
- You have/Someone spilled coffee over your clothes.
- You have a migraine.
- The video adapter cable is missing.
- You will be late for 15 minutes.
- You will not be able to attend [could someone else do it for you?]
- Someone you depend on is absent.
- Someone you depend on is hostile (person or audience).
- You have a bladder infection/stomach irritability/etc. [drugs available? scheduling?]
- You have no Internet connection (despite being promised).
- You cannot use your slides (projector is broken and cannot be repaired).
Note that I didn’t do any research, these are just things that came to me while writing (yup, I’m a ‘let’s plan for the worst’ kind of guy — and then enjoys the situation, mostly, something is always running in the back of my mind … anyway). Given the topic, I also did go broader and include work-related issues. After all, many creative projects happen in organizations, for example, a PhD in a department.
If a category is not relevant, simply limit it the the relevant categories. If there are multiple possible cases (e.g., more than one person works for you, simply write down their names and flip again through the book to chose one — or more). You can also chose more than one accident/problem. After all, there are not always independent of each other.
You could also use this list as a checklist (without any warranty, e.g., that everything important is covered, likely not) — if that does not make you paranoid. And sometimes the right reaction is probably that it can happen, but that you can deal with it.
BTW, if you know of cases that can happen, drop me a comment or an eMail. I’m happy to hear about them (what they were, not that they happened to you ;-)).
The next list will probably consist of useful items and strategies that cover most of these issues. I can think of a few — but many require some thinking and have to be implemented in advance.
Literature that inspired this posting (about technical infrastructure):