Sometimes in our attempt to avoid error we surround software development with so much paperwork that it overwhelms the software. No one will ever notice. This is a good one to use when you want to cut corners. Unfortunately, we seldom know which features will be important to the users. To won't hurt much.
Good programmers use structured programming as easily as they breathe.
We'll just reuse this data item. A program is written once, but read many times, so make it easy to read by following the Laws of Naming . Accept the fact that your programs will include many more lines of code to handle failure than to handle success. Grandiose schemes usually lead to white elephants with pretentious objectives, high costs, fantastic claims, neglect of other projects, fanatical denial of failure, and a sudden, total write-off. Automated testing is the answer.