By alashcraft
via codethinked.com
Published: Jul 10 2008 / 15:03
There is an acronym that has been thrown about quite a bit in most agile development circles (and elsewhere) and that phrase is YAGNI. In case you don't know, it means "You Ain't Gonna Need It". The idea is that any time you spend implementing something that you don't end up needing is wasted time, so don't do it, because "You Ain't Gonna Need It"! Now, while this phrase doesn't quite jibe with what I am talking about, I want to introduce a new and related phrase.
Comments
paul_houle replied ago:
Hell yeah.
The primary principle in error handling should be to minimize the amount of (i) coding, and (ii) thinking that goes into error handling. The reason for that is that every decision made in developing error handling logic is another opportunity to make a mistake that can affect both the program's mainline (introduce an error when there wasn't any) and error paths (make an error have worse consequences than it should.)
Programmers should decide ahead of time on some generic safe, sane and largely correct error handling practices that can be implemented with minimum code and reuse.
Voters For This Link (17)
Voters Against This Link (1)