Utils anti-pattern & AutoMapper
These are more for my reference purposes - hopefully you’ll find them useful:
If you’re about to name a class **Util; think harder - there is a better name that discribes what that class is for:
Chriss Missal has some advice for you
Faced with the prospect of heaps of left hand side => right hand side code in your DTO of anti-corruption layer? Consider Jimmy Bogard’s Automapper
The Simplest thing that could Possibly work
Jay has a good discussion concerning the design dilemma we often face considering the “simplest thing that could possible work”. Is it appropriate to implement a simple half baked solution that we know we will throw away as requirements become more defined? Or should we start out with a more complex pattern that will give us more flexibility?
http://blog.jayfields.com/2008/06/simplest-thing-that-could-possibly-work.html
Jay concludes that you can’t decide which pattern will give you the right flexibility until you have more requirements. So, rather than potentially implement the wrong complex solution, just treat the temporary solution as part of the learning process.
I agree. Like optimising, you need to know the precise requirements before you can choose the right pattern.
Throw away code isn’t wasted; rather its used like scrap paper in the learning process.
Recommended reads
-
