In my early years of programming, performance was everything. These days, since I don't do system-level programming anymore, code maintainability is more important. Of course that doesn't mean to say that it's OK for my code to suck so many CPU cycles doing trivial things. It just means that it pays off better in the long run to have code that is easy to maintain/improve with good/average performance than to have blazing-fast software whose code is hard to understand (and is possibly buggy or will eventually have bugs).
Jeremy Miller weighs in on putting code where you would expect to find it. This particular quote here caught my attention:
I wouldn't want to live without ReSharper's CTRL-N shortcut to find any class in the solution (with wild cards too!). Then again, finding code with ReSharper will be a whole lot easier if you employ good naming practices and put code where you would expect to find it.
That sounds just like the situation I had with a project in my previous company. The C# class files were stored in directories that did not match their namespaces. Good thing ReSharper was there, then again it's still much better to have predictable code and ReSharper at the same time.
06-12-2007 7:55 AM