tag:blogger.com,1999:blog-5169492046430026000.post5639254196634379083..comments2023-09-06T15:56:14.483+01:00Comments on IT Code Monkey: It's all in the specificationsOblivionSYhttp://www.blogger.com/profile/16204406573195689720noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5169492046430026000.post-72253989972005094232009-05-27T09:45:40.676+01:002009-05-27T09:45:40.676+01:00The other option is moving the deadline. While thi...The other option is moving the deadline. While this is not always possible, with an arbitary deadline (as it was in this case) it would be better to up the quality, especially as it is not just for this one customer. The maintenance headache of poor code should be reason enough, but actually producing what is specified (ie Oracle!) is essential.OblivionSYhttps://www.blogger.com/profile/16204406573195689720noreply@blogger.comtag:blogger.com,1999:blog-5169492046430026000.post-41879077616772356282009-05-27T08:48:54.919+01:002009-05-27T08:48:54.919+01:00One of the best things I ever read - in 'MMM&#...One of the best things I ever read - in 'MMM'; namely, "plan to throw one away, you will anyway".<br /><br />One of the big[ger] problems here is that unless you're working on a T&M basis, you're on 'fixed' budget, function, and delivery-date - and, in that case, when the deadline approaches, and you're not done, what will suffer? Function *has* to be delivered, and so it has to be quality?peetmhttp://www.peetm.comnoreply@blogger.com