Secrets of Sane Programming: 1. Believe your own eyes. 2. Never design something you don't fully understand.
-
-
Replying to @sebinsua
I will unpack these thoughts since they are important but probably look like trivialities:
1 reply 0 retweets 0 likes -
Replying to @sebinsua
1. An issue when debugging is letting preconceptions blind you. e.g. Seeing what you expected to see, not what an error message tells you.
1 reply 0 retweets 0 likes -
Replying to @sebinsua
It helps to take things literally. And, it helps to systematically interrogate any discrepancy between your understanding and an occurrence.
1 reply 0 retweets 0 likes -
Replying to @sebinsua
2. Problem-solving often surfaces sub-problems. If you like problem-solving this can lead to a state in which you keep tacking on solutions.
1 reply 0 retweets 0 likes -
Replying to @sebinsua
Consequently this can expose consumers to implementation details of design decisions for solutions to problems they don't have.
1 reply 0 retweets 0 likes -
Replying to @sebinsua
Additionally if you're too readily taking opportunities to fix problems you are probably also doing so when your solutions are bad.
1 reply 0 retweets 0 likes -
Replying to @sebinsua
If you are making design decision based on the feeling that 'this will probably fix X' you are risking poor design decisions.
1 reply 0 retweets 0 likes -
Replying to @sebinsua
And often not-solving a problem is better than providing an incomplete solution or one with negative externalities.
1 reply 0 retweets 0 likes
Particularly if you are unable to articulate how it is incomplete or the choices you've made and their impact.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.