3 ms·
> 1. In your code should know what the edge cases, loop condition issues, etc. Perhaps, but: > It ain’t what you don’t know that gets you into trouble. It’s w
by throw0101a 3y ago
> 1. In your code should know what the edge cases, loop condition issues, etc.
Perhaps, but:
> It ain’t what you don’t know that gets you into trouble. It’s what you know for sure that just ain’t so.
* https://quoteinvestigator.com/2018/11/18/know-trouble/ https://quoteinvestigator.com/2018/11/18/know-trouble/
Sometimes you want to go to 'first principles' and reassess your assumptions. As a sysadmin I sometimes I resort to making sure the thing is actually physically plugged in (OSI Layer 1), the move up the stack with regards to how the bits flow.