Tuesday, December 1, 2009
ORM or die!
I recently blogged about the DevExpress ORM tool - Express Persistent Objects (XPO). I have had (and continue to have) a great experience using this tool. Everytime I use it, I find something else that endears itself to me.
Having made the decision that all future projects would include a data access layer (DAL) based on XPO, I was nontheless surprised at how important some developers consider an ORM tool to be. So important in fact, that they are willing to advocate leaving an employer who does not allow the use of an ORM tool. (See link in heading for the full story).
My first reaction was, "This is a a bit extreme". After all, the GFC (Global Financial Crisis) is still affecting most of the world, and job security is not as good as it was a few years ago. Upon reflection, however, I am now inclined to agree with this sentiment, and I do so for two main reasons.
Firstly, professional development is difficult enough to stay current with, without being hampered by the lack of access to current tools. Every job, every project, every domain space provides an opportunity to increase knowledge and expertise. Being fettered with non-involvment with a specific tool or model or paradigm cannot be good for your CV, or even your sense of self-confidence.
Secondly, and maybe even more germane to a professional developer, is the responsibility to provide accurate, honest, and professional service to your employers - even if they don't understand or disagree with your advice. I don't know if there is a legal accountability to ensure your employer/client receives valid, up-to-date, best practices advice, but there is certainly a moral one.
Personally, I have few clients who are even remotely interested in the technologies I employ to provide the applications they need. They only care about the end result. But if they discovered that I ignored a major tool or model while developing their applicaton they would sack me; and they would be fully justified to do so.
Having made the decision that all future projects would include a data access layer (DAL) based on XPO, I was nontheless surprised at how important some developers consider an ORM tool to be. So important in fact, that they are willing to advocate leaving an employer who does not allow the use of an ORM tool. (See link in heading for the full story).
My first reaction was, "This is a a bit extreme". After all, the GFC (Global Financial Crisis) is still affecting most of the world, and job security is not as good as it was a few years ago. Upon reflection, however, I am now inclined to agree with this sentiment, and I do so for two main reasons.
Firstly, professional development is difficult enough to stay current with, without being hampered by the lack of access to current tools. Every job, every project, every domain space provides an opportunity to increase knowledge and expertise. Being fettered with non-involvment with a specific tool or model or paradigm cannot be good for your CV, or even your sense of self-confidence.
Secondly, and maybe even more germane to a professional developer, is the responsibility to provide accurate, honest, and professional service to your employers - even if they don't understand or disagree with your advice. I don't know if there is a legal accountability to ensure your employer/client receives valid, up-to-date, best practices advice, but there is certainly a moral one.
Personally, I have few clients who are even remotely interested in the technologies I employ to provide the applications they need. They only care about the end result. But if they discovered that I ignored a major tool or model while developing their applicaton they would sack me; and they would be fully justified to do so.
Labels: Business, Development, Technology
Subscribe to Posts [Atom]