Tuesday, October 15, 2013

For Best Results, Don't Initialize Variables (codinghorror.com)

I noticed on a few projects I'm currently working on that the developers are maniacal about initializing variables. That is, either they initialize them when they're declared or they initialize them in the constructor. Well, this all struck me as unnecessary work in the .NET world. Sure, maybe that's the convention in the wild and wooly world of buffer overruns C++, but this is managed code. Do we really want to play the I'm smarter than the runtime game again? Read more...