http://blog.bryanbibat.net/2009/06/17/technical-debt/ With kindness comes naïveté. Courage becomes foolhardiness. And dedication has no reward. Wed, 16 May 2012 06:37:09 +0000 hourly 1 http://wordpress.org/?v=3.3.2 http://blog.bryanbibat.net/2009/06/17/technical-debt/#comment-176 Constant Random Change » Basic Software Estimation Graphs Mon, 24 Aug 2009 09:31:52 +0000 http://blog.bryanbibat.com/?p=387#comment-176 [...] By rushing the project, you create a lot more defects on the way, not to mention that you unnecessarily stress out your team. It is quite common to see the scenario above end up taking 4 or 5 months to finish because of the extra effort needed to deal with the problems caused by rushing. In other words, a bad case of Technical Debt. [...] [...] By rushing the project, you create a lot more defects on the way, not to mention that you unnecessarily stress out your team. It is quite common to see the scenario above end up taking 4 or 5 months to finish because of the extra effort needed to deal with the problems caused by rushing. In other words, a bad case of Technical Debt. [...]

]]> http://blog.bryanbibat.net/2009/06/17/technical-debt/#comment-459 Constant Random Change » Basic Software Estimation Graphs Mon, 24 Aug 2009 09:31:52 +0000 http://blog.bryanbibat.com/?p=387#comment-459 [...] By rushing the project, you create a lot more defects on the way, not to mention that you unnecessarily stress out your team. It is quite common to see the scenario above end up taking 4 or 5 months to finish because of the extra effort needed to deal with the problems caused by rushing. In other words, a bad case of Technical Debt. [...] [...] By rushing the project, you create a lot more defects on the way, not to mention that you unnecessarily stress out your team. It is quite common to see the scenario above end up taking 4 or 5 months to finish because of the extra effort needed to deal with the problems caused by rushing. In other words, a bad case of Technical Debt. [...]

]]>