|
@Katsunami: to support you with a very simple example: back when I was a kid and storage was precious I wrote (with Pascal) a simple equivalent to 'du -h <drive>' for DOS for my own use, just for not to have to juggle with bytes when I crammed my stuff in as little floppies as possible.
But I wanted to do it RIGHT. Thus I thought about all the "what ifs" a user could pass as command line argument. Gave them exit codes and proper error descriptions. The code to do the task was 3 lines. The code to catch all the shit which might hit the fan - the rest of an A4 page. It was a little shitty prog. But I was damn proud of it because I did it error proof. Is this somehow along with what you had in mind? If so then you might like the following answer when a user asks what the fuss is all about: To tell the computer what to do is just the beginning; the real fun starts when you are telling what to do if shit hits the fan. Because you have to anticipate every direction and angle it might come from.
|