Reusability to the Rescue!

Over the years, I've accumulated a large volume of code from various projects. I am not very organized though and I always have the bad habit of starting from scratch every time. It wasn't until recent years that I have started doing code reuse and forcing myself to create modularity. Even with that though, I still have trouble with book keeping, since many times I have different versions of the same code present in different projects.

In the E-Day crunch time like now, I am suddenly glad that of all the code I've written, the most useful has been a Vector class that supports three componets, assignments, basic operations including normalization, cross products, etc. I was going to try and build a e-day demo without them, but alas, its just way too much work, considering all the stuff I will have to code and the time constraint I'm under. So, I pulled out my old vector class, and modified it. Yes, I added a method to overload the [] operator. Maybe not such a good idea in the long run, but sure solves many problems now.

*sigh*

The neverending conflict between good software practices and time constraints.