Developer Productivity is Important - Reality or Myth?

a while back, i read a post by rob conery in which he discussed both his thoughts on developer productivity in relation to the creation of a new os project (asp mvp), and how he may have thought that in some instances hiding behind webforms and not touching mvc was really just laziness or ignorance mistaken for productivity. additionally i also read another post by scott bellware in which talks about a similar subject, in that developer productivity when viewed in isolation, is really a myth.

while i think rob may have been a bit aggressive in singling out someone's pride and joy (these guys have obviously put a lot of effort into this project so if they prefer their i-snack 2.0 to their vegemite , all the more power to them), both these posts make some important points in relation to short term , long term and invisible productivity for web developers (and others, but we’re talking about web developers today).

sometimes spending less time creating a web page is not the best thing for the web page
i started web development outside of the webforms world and believe that a lot of asp.net developers need to get out more, as sometimes using a atom bomb(webforms) when a stone(html page) will do the job has a much better long term result. if this means spending a bit more coding time, don’t whinge, do the right thing. i understand business is business and fastest can sometimes mean you keep your bosses happier but making the wrong call can bring other issues into the system that will add time somewhere else (refactoring, performance tuning etc).

just because you can use a control in the designer that does what you need (as well as everything else) doesn’t mean you should use it
using a easy to use control in the search of productivity can be a mistake. learning to use the right tool for the job is usually the best thing for the task at hand. this sometimes trying/learning something new.

if taking up a new technology seems like a bad idea just because it has learning curve then maybe your priorities need readjustment
sometimes a better brand of kool-aid comes along, and you may miss it simply because you don’t have time to try it or because of any number of other reasons. if this kool-aid was a new framework that could give you a lot of cool things that solve some problems the project has, and maybe also save development time then making time may save you time, and more importantly give you a better end product.

sustainable productivity is the only productivity that matters
if you have to rewrite something later because the tool wasn’t right for the job, or any other reason that comes down to your previous attempts at gaining productivity then it may be that your shooting yourself in the foot.

productivity is about product
the main goal as a developer is to create something great. this doesn’t always mean the easy or more familiar route. sometimes it means the slow more complicated route or trying something new. deciding the right tool for the job, really comes down to whether the product in productivity has something to gain.

but some of those points contradict each other?!

this is where it gets tricky (or not so, depending on how you look at it). working as a programmer/web developer/enlightened-one means that you have decided to make a career out of being the go-to-guy when it comes to creamy web coding goodness. your work is a reflection of you .

i’m not saying that webforms or mvc or html/jquery/webservices is a better choice. every project has different needs, and sometimes using one over the other (or reinventing the wheel in mvp’s case) is the right decision. choosing based on taste/presumed productivity alone may be a simple folly.