Dead Programs Tell No Lies
Bugs happen. Something goes wrong, there’s absolutely no way it could have happened, it’s a problem with the compiler… Until you fix it and everything is fine.
The book makes an interesting assertion: catch and release is only for fish. If an error has occurred, terminate the program and figure out what went wrong. Don’t release it back into the wild, corrupting data and files on your system.
This is best summarised with the following passage about crash, don’t trash:
“One of the benefits of detecting problems as soon as you can is that you can crash earlier, and crashing is often the best thing you can do. The alternative may be to continue, writing corrupted data to some vital database or commanding the washing machine into its twentieth consecutive spin cycle.”
As tempting as it may be, from personal experience, to ignore a bug and move on, that small amount of effort at the start will pay huge dividends further on in the project.
Thank you for reading, see you tomorrow!
#PathToSWE
