Comments on: Why False Starts Hurt Your Project http://www.codesqueeze.com/why-false-starts-hurt-your-project/ Ideas for building efficient developers and software Fri, 10 Sep 2010 02:43:25 -0400 hourly 1 By: James Barlow http://www.codesqueeze.com/why-false-starts-hurt-your-project/#comment-124 James Barlow Wed, 01 Aug 2007 22:47:19 +0000 http://www.codesqueeze.com/why-false-starts-hurt-your-project/#comment-124 A good article, but my critique of this analysis is that the difference between "a false start" and "working toward an early prototype" is often only clear with the benefit of hindsight. One always has to be careful not to end up trapped in the metaphor. Software development is not wood chopping, nor is it carpentry, nor is it a marathon. But there's no argument on the need for design - it's enormously frustrating to realise that a client doesn't know what they want, and downright irritating if they won't accept that this is a problem. A good article, but my critique of this analysis is that the difference between “a false start” and “working toward an early prototype” is often only clear with the benefit of hindsight.

One always has to be careful not to end up trapped in the metaphor. Software development is not wood chopping, nor is it carpentry, nor is it a marathon.

But there’s no argument on the need for design – it’s enormously frustrating to realise that a client doesn’t know what they want, and downright irritating if they won’t accept that this is a problem.

]]> By: Justin B http://www.codesqueeze.com/why-false-starts-hurt-your-project/#comment-114 Justin B Tue, 31 Jul 2007 01:03:24 +0000 http://www.codesqueeze.com/why-false-starts-hurt-your-project/#comment-114 Max, Good article. I had a discussion with Gibb about this topic recently. I think that what you are saying is especially true when less-experienced developers are involved. Max,

Good article. I had a discussion with Gibb about this topic recently. I think that what you are saying is especially true when less-experienced developers are involved.

]]> By: Max Pool http://www.codesqueeze.com/why-false-starts-hurt-your-project/#comment-113 Max Pool Tue, 31 Jul 2007 00:27:39 +0000 http://www.codesqueeze.com/why-false-starts-hurt-your-project/#comment-113 Jason, I am going to slightly clarify your developer reminder as if read wrong might be a loaded and dangerous message. I would tell developers to use your gut instincts when overriding a manager's decision. Some of their decisions are completely absurd, but if you override them all you will appear insubordinate. Pick your battles and you will win the war. Jason, I am going to slightly clarify your developer reminder as if read wrong might be a loaded and dangerous message.

I would tell developers to use your gut instincts when overriding a manager’s decision. Some of their decisions are completely absurd, but if you override them all you will appear insubordinate. Pick your battles and you will win the war.

]]> By: Jason Gibb http://www.codesqueeze.com/why-false-starts-hurt-your-project/#comment-112 Jason Gibb Mon, 30 Jul 2007 21:56:47 +0000 http://www.codesqueeze.com/why-false-starts-hurt-your-project/#comment-112 This is a very good analysis of the different influences on false starts. One thing I like to remind developers is never assume you have to start coding just because your manager (or your client) thinks you should. Better to sit down and start sketching out the system design before touching the keyboard. BTW, I love the graphics you chose for each role. This is a very good analysis of the different influences on false starts. One thing I like to remind developers is never assume you have to start coding just because your manager (or your client) thinks you should. Better to sit down and start sketching out the system design before touching the keyboard. BTW, I love the graphics you chose for each role.

]]>