Comments on: Developing vs Programming http://wojodesign.com/developing-vs-programming/ Web Design and Development Blog Fri, 03 Feb 2012 10:57:00 +0000 hourly 1 http://wordpress.org/?v= By: Ryan Miller http://wojodesign.com/developing-vs-programming/#comment-544 Ryan Miller Tue, 31 Mar 2009 18:16:42 +0000 http://www.thewojogroup.com/?p=442#comment-544 A home builder will not (or should not) break ground without a (signed off) detailed blue print. As developers of software applications, we should have the same approach. If this means that we spend 1/3 (or more) of the time on planning, or making the blueprint, so be it. For those of you (us) who spend more than 1/3 on coding, I wonder how many spent that time redesigning, retro-fitting, and restarting during the development phase simply because the blueprint was not sufficient. It's easy to want to get hand's on "banging on the keyboard" without knowing if the customer wants 30" or 42" cabinets. I like to call this approach "cowboy coding", not sure why. Another laborical metaphor - "measure twice, cut once". With this, we spend 2x on planning, 1x on execution, and hopefully 1x on implementing. At a high-level, I couldn't agree more with this article. A home builder will not (or should not) break ground without a (signed off) detailed blue print. As developers of software applications, we should have the same approach. If this means that we spend 1/3 (or more) of the time on planning, or making the blueprint, so be it.

For those of you (us) who spend more than 1/3 on coding, I wonder how many spent that time redesigning, retro-fitting, and restarting during the development phase simply because the blueprint was not sufficient. It’s easy to want to get hand’s on “banging on the keyboard” without knowing if the customer wants 30″ or 42″ cabinets. I like to call this approach “cowboy coding”, not sure why.

Another laborical metaphor – “measure twice, cut once”. With this, we spend 2x on planning, 1x on execution, and hopefully 1x on implementing.

At a high-level, I couldn’t agree more with this article.

]]> By: evodanh http://wojodesign.com/developing-vs-programming/#comment-543 evodanh Tue, 31 Mar 2009 06:50:37 +0000 http://www.thewojogroup.com/?p=442#comment-543 I agree with spending 1/3 time for testing but I disagree with spending 1/3 of your time on planning. Why does we spend a lot of time for planning??? I agree with spending 1/3 time for testing but
I disagree with spending 1/3 of your time on planning. Why does we spend a lot of time for planning???

]]> By: Dennis Sellinger http://wojodesign.com/developing-vs-programming/#comment-542 Dennis Sellinger Mon, 30 Mar 2009 18:30:57 +0000 http://www.thewojogroup.com/?p=442#comment-542 I disagree with 1/3 rule also, but for different reasons. I think there is rarely a clear separation between planning, coding and testing. I remember about 10 years ago when we were asked to separate these in tasks in the time tracking application and it typically resulted in a bunch of made-up numbers. I think most modern processes talk about planning a bit, coding a bit and testing a bit (not necessarily in that order). I don't think that it is useful to artificially try to separate the three tasks. I disagree with 1/3 rule also, but for different reasons. I think there is rarely a clear separation between planning, coding and testing.

I remember about 10 years ago when we were asked to separate these in tasks in the time tracking application and it typically resulted in a bunch of made-up numbers.

I think most modern processes talk about planning a bit, coding a bit and testing a bit (not necessarily in that order). I don’t think that it is useful to artificially try to separate the three tasks.

]]> By: Jason Williams http://wojodesign.com/developing-vs-programming/#comment-541 Jason Williams Sat, 28 Mar 2009 00:39:37 +0000 http://www.thewojogroup.com/?p=442#comment-541 I disagree with Evan on this one, not saying you are completely incorrect, from my experience heavy planning tends to decrease the amount of time needed for coding. (Not necessarily the amount of coding.) Really I believe planning and testing are the 2 things you should spend the most time on. 1/3 works well as a good guideline though. I disagree with Evan on this one, not saying you are completely incorrect, from my experience heavy planning tends to decrease the amount of time needed for coding. (Not necessarily the amount of coding.)

Really I believe planning and testing are the 2 things you should spend the most time on. 1/3 works well as a good guideline though.

]]> By: Evan http://wojodesign.com/developing-vs-programming/#comment-540 Evan Thu, 26 Mar 2009 17:05:40 +0000 http://www.thewojogroup.com/?p=442#comment-540 I disagree with the 1/3 rule. After spending large amounts of time programming large web systems it is obvious that most of my time is spent coding. I disagree with the 1/3 rule. After spending large amounts of time programming large web systems it is obvious that most of my time is spent coding.

]]>