“Friends don’t let friends ORM”
“ORM is a pattern, not a framework”
“I like typed datasets, and I cannot lie”
It’s not that I’m anti-ORM, or believe popular ones like NHibernate, Linq2Sql, and EF are useless (okay, maybe EF is). It’s the mindset that you need an ORM Framework bloating your app from the start. It’s the common:
“Hey, new project!” “Awesome, which ORM should we use!” – WTF!?!
While I’m busy loosing friends and respect, I’ll state this is an “anti-agile pattern” – if you were truly agile and doing iterative development, there isn’t a whole bunch of plumbing to write at once. SQL isn’t hard, and is too important to performance to let a tool codegen it for you. ORM frameworks encourage data-driven design, leading to a database friendly UX.
Last night I read The Duct Tape Programmer by Joel Spolsky and added Coders at Work to my Amazon queue (no Kindle edition, so they missed an impulse sale). I love this post and the description of a Duct Tape Programmer. I hate the term pragmatic – the word itself sounds academic, and I don’t think a pragmatist (another suspicious term) came up with it. I think the academics made up the word cause saying short sighted made them look bad. That’s really what many mean when they say “pragmatic” – Oh sure, he got the app out, but his code is awful, and he has tons of technical debt, and it will all have to be rewritten, and how far do you think an app like that can scale without an Enterprise Service Bus?, and I bet there isn’t even an Inversion of Control framework, and I know he doesn’t have good test coverage and any tests he does have are only integration tests, and…
The Duct Tape Programmer is driven by a different force than the Academic. The Duct Tape Programmer is looking at the release date, and only values stuff that gets the app working on that date. She would rather have 10 meetings with users than one meeting with a Systems Architect. She would tell you KISS when you asked if you should extract an interface for a single widget. She lives Agile and Lean on a subconscious level, because to her it’s just common sense.
Joel ended his post saying you can’t just be a Duct Tape Programmer. I’ll add to this – you can become one. Move your focus off the code to the app, and more importantly, the user. Expand your knowledge base horizontally – learn multiple languages, frameworks, systems. Do some raw socket programming, and write a graphics shader. Install Linux on a Sparc 10. Make an app for your mobile phone. Question the accepted wisdom, and be an old school hacker.
I’m off now to convince Cicelie (DragonTee.com) to design a “Duct Tape Programmer” t-shirt, in the meantime you can tell me why I’m wrong below. Don’t be shy, I’m used to it!