Under the hood and working with .Net, TDD, Software Design, and Agile Stuff
Two lessons relearned/reinforced. One in the positive and one in the negative.
1.) When working in a strange codebase, make no assumptions about the way that it works internally. I got burned a little bit yesterday because I had made a false assumption about the way the existing code performed the aggregation of financial numbers. I should have done a little more research on the inner workings of the existing code. No big deal because...
2.) All two dozen places that I used aggregated data used the same 3-4 classes. One 20 minute coding change later and all of the numbers on my report suddenly look much better.
About Jeremy D. Miller
Jeremy began his IT career writing "Shadow IT" applications to automate his engineering documentation, then wandered into software development because it looked like more fun. Jeremy previously worked as a systems architect building mission critical supply chain software for a Fortune 100 company and learned agile development practices as a .Net consultant at ThoughtWorks, one of the pioneers of agile development. Jeremy is the author of the open source StructureMap (http://structuremap.sourceforge.net) tool for Dependency Injection with .Net and the forthcoming StoryTeller (http://storyteller.tigris.org) tool for supercharged FIT testing in .Net. Jeremy's thoughts on just about everything software related can be found on his weblog "The Shade Tree Developer" at http://codebetter.com/blogs/jeremy.miller, part of the popular CodeBetter site. Jeremy is a Microsoft MVP for C#.
