>>15
...and writing code with ordering dependencies, and when downcasting under preconditions enforced elsewhere, and when doing state machines or other fragmented code, and when writing workarounds for buggy libraries or OS calls, etc. All of which are not optimizations nor shortcuts, but whose rationale needs to be documented in the code so others don't fuck it up.