The boredom is an interesting risk factor, and I'm wondering what could be done to address it.
For software, I'm familiar with a process of intentionally designing and executing a safe breakage as a sort of drill to keep people's heads in the game---no better way to find where you accidentally didn't have redundancy than by turning off a system that should have a fallback and seeing what else breaks. Is that practical for CIC, or is there insufficient redundancy in CIC to do something like that safely?
For software, I'm familiar with a process of intentionally designing and executing a safe breakage as a sort of drill to keep people's heads in the game---no better way to find where you accidentally didn't have redundancy than by turning off a system that should have a fallback and seeing what else breaks. Is that practical for CIC, or is there insufficient redundancy in CIC to do something like that safely?