The use of metadata classes:
[Credit goes to Mike’s post for inspiring this bit of hatred; I’m not blaming Mike for the hate, of course, just for reminding me that I hate it. 🙂 ]
I don’t understand why MS is using this approach. Why not a fluent approach like, maybe something like this:
The advantages of the fluent approach should be obvious: I’m not violating DRY, I have compile-time checking that my constraints are valid (somewhat), and I don’t have to create a new public class just to house a single constraint.
I like Twitter, and I’ve actually gotten some real value out of it, but the signal-to-noise ratio is terrible, even for guys I really respect and that have a lot of valuable things to say. I’m not going to name names, but I’m appalled at how much time some people are apparently spending doing useless activities on Twitter, such as retweeting retweets and telling me about their breakfast. I DO NOT CARE. I follow you on Twitter to get useful information. Maybe Twitter should allow people to categorize their tweets or something. That would let me turn off the “walking the dog” category. Of course, I seem to be in the minority here. Maybe I should start tweeting every time I walk to the fridge to grab a water?
People hating on ‘#regions’:
I am very sick of posts like this. I 100% disagree with this post. I do indeed use regions to group my code in the standard way (fields, properties, constructors, methods, sometimes breaking things up further if I think it makes the code easier to navigate). I do not want to use the file structure window; I don’t want to ever look away from the code window at all (and yes, I use Resharper). Regions make things look saner, even for small classes, and really make large classes easier to navigate. In the end, the use of regions is a matter of opinion, and I’m sick of people ranting about it. If you don’t like #region, fine, don’t use it, but stop talking about it. It isn’t even original at this point.