It’s not about the bike: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 22: Line 22:
When the system seems on the brink of catastrophe and the most articulate question you can form about the situation is ''what the fuck is going on?'' you do ''not'' want to be unplugging, decoding, or working around non-functional safety mechanisms.
When the system seems on the brink of catastrophe and the most articulate question you can form about the situation is ''what the fuck is going on?'' you do ''not'' want to be unplugging, decoding, or working around non-functional safety mechanisms.


This is another reason for simplification of processes and documentation to be your first step.
So, fundamental system design principle: [[first, cut out the pies]].
 
All other things being equal, the optimum amount of technology to have in a given situation is ''none''. Tech necessarily adds complication, cost and confusion. Therefore your first question is: how will technology improve the situation. Ask not just in terms of reduced ''cost'' but reduced ''waste''.
 
 
{{Sa}}
{{Sa}}
*[[Why is reg tech so disappointing?]]
*[[Why is reg tech so disappointing?]]