Have you ever designed a program where you have designed to the best to your ability of the problem at hand, but there were some details that you knew might be tricky but you just didn't bother to explore it more because as I said before, it's been designed according to the problem being solved, changing the design didn't seem like a good idea. So you chose to tackle the problem later when you arrived at it.
So you implemented it and when you arrived at the problem, you realized that it's actually easier than you thought and due to the nature of the language or library or whatever (in my case, it's Ruby's duck typing), it's actually helping me solve another problem that I tried to tackle differently, the results of which, the code becomes simpler and cleaner.
AHA! Didn't even know that.
So you implemented it and when you arrived at the problem, you realized that it's actually easier than you thought and due to the nature of the language or library or whatever (in my case, it's Ruby's duck typing), it's actually helping me solve another problem that I tried to tackle differently, the results of which, the code becomes simpler and cleaner.
AHA! Didn't even know that.
0 comments:
Post a Comment