Thursday, November 5, 2009

Improve after, not before!!

In programming, you try to make a good code, even before writing anything! Although this is good, it normally takes time and effort you could be using in the implementation of that ugly alternative you presented or imagined the first time you thought about a problem.

If you can do something useful in your life, try to start doing it as soon as possible, and then, if what you did needs some improvements, they will be wittily apparent.

But then again, you will be tempted to think in a better way to make those improvements. Remember: do something, then improve later.

In order to save time and effort, improve after you do anything. Sometimes improvements are not really needed.

This seems recursive: To improve, do. To do, improve.

No comments:

Post a Comment