So I spotted this in the TWs blog feed. What annoys me about posts like this is this quote:
“If your organization’s senior developers write static methods for everything, then you might want to question the capability and desire of your technology leaders to learn, grow, improve and expand their understanding of their chosen profession.”
This is such a blanket, vacuum based statement that it’s pretty useless and almost dangerous. What the author is discounting is the VAST amount of applications and needs that are out there. What is valid and correct in one context could be entirely wrong and detrimental in another. This is akin to saying something like “You should never use stored procedures”.
The real dangerous part is that as more and more people make these kinds of statements, younger & newer developers take this as gospel and don’t think critically about whether is applies to their given situation or not. Thinking like this is becoming more and more in vogue and I’m not sure the cause. Maybe it’s because many more developers have blogs / outlets in which their voices can be heard, so they’re making grand, booming statements. Whatever the catalyst, I’d like to see it make the ability to think critically just as in vogue.
Our ability to adapt and come up with creative solutions, often working within a given set of constraints, is what makes us developers / engineers / etc.. Constraining our thinking and maintaining a narrow view of what we want to do, despite empirical evidence otherwise, will lead to irrelevance, at best, and obsolescence at worst.