Today I found myself taking the code download from a book I’m reading (Dependency Injection in .NET) and restructuring the solutions and sample projects that it contained according to my employer’s project structure standards and guidelines (which, incidentally, I helped to create and currently maintain).
Then I found myself wondering “Why am I doing this?” and “What value is added by this extra effort?”. This code will never be part of an official project or effort that I’m working on. I don’t intend to use this for anything other than my own self-education. Then it finally dawned on me…
There is unimaginable value in consistency and discoverability – repeatedly achievable results. What does a McDouble taste like if you get it from your local McDonald’s…or a Big Mac? How is it dressed? I’m betting that it is probably consistent with the same orders from my own local McDonald’s and that these locations have similar, if not identical, menu options…and therein lies a good portion of their value and appeal to such a wide consumer market.
In the code download, I wasn’t so much interested in the samples themselves (those are covered in the book), but in the accompanying unit tests (something that I still sometimes struggle with). Placing these projects and solutions into a common structure allowed me to easily identify the tests accompanying the code and their relationship to the samples.
No comments:
Post a Comment