Okay. This may be somewhat a rant...so, you have been warned.
I've noticed a lot of people get obsessed with performance. This is kind of okay, provided your code is working. I know people (we won't name names!) that will just fret on performance before the method they want to write even exists. Perhaps this is just my point-of-view, but isn't it better to get X piece of code taking the proper input(s) and delivering the proper output(s), first? You can get hung up on performance and refactor to your heart's content - but get it working first, please.
Second. Don't go crazy typing before you think about anything. Comment the process first, don't type any code. When you're done, make sure the logic makes sense. Why spend time coding something only to realize it doesn't even make sense after you just typed 30 lines of code?
Perhaps I've bene a bit more on-edge about this stuff since I've been reading the pragmatic programmer lately.
Have a nice day :)
Print | posted on Wednesday, July 12, 2006 5:25 PM