174 reputation
5
bio website fundynamic.com
location Netherlands
age 31
visits member for 2 years, 9 months
seen May 10 at 7:55
Developer of RealBot, Dune II The Maker. Experience in Java, C, C++. Currently developing mostly in Java.

Dec
10
awarded  Popular Question
Feb
9
comment Is it significantly costlier to fix a bug at the end of the project?
+1 for reference indeed, +1 for the visualisation (too bad I can only give one point.) Great answer, thanks!
Feb
8
awarded  Nice Question
Feb
7
comment Is it significantly costlier to fix a bug at the end of the project?
@ZekeHansell , its exactly that chart I'm looking for with data backed up by it. Its a famous chart, we all know. Even if we don't know the chart itself, it surely matches our experience/gut feeling. However, I don't think it can be generalized for all issues/bugs. In fact, perhaps our own inability to write super flexible code makes changes in the later fases expensive?
Feb
7
comment Is it significantly costlier to fix a bug at the end of the project?
@Andrea I believe the impact of CSS is less than a change in some subsystem integrated with other systems. Yes, it has impact on the visuals, but it will certainly not be as complex as 'backend' bugs can be. (otoh backend issues can be as complex as css issues).
Feb
7
comment Is it significantly costlier to fix a bug at the end of the project?
@AaronMcIver my intention is to have more people get to know about this. Like spreading the word and increasing chances of getting real data out. I do not search for a real discussion; great ones are being held at the article (as you also have found out :)).
Feb
7
comment Is it significantly costlier to fix a bug at the end of the project?
Yes that all makes sense. Although, I do wonder if this is significantly different from fixing later. Yes, you need to re-learn stuff a bit. However, perhaps by not releasing earlier you have lost more money than the cost it would be of fixing this issue. Would that make this issue cheap or expensive to fix? Even when it is less work because it was at the beginning?
Feb
7
comment Is it significantly costlier to fix a bug at the end of the project?
So basically we're talking about the amount of effort it takes to fix a bug later (or earlier). I can think of other factors that make bugs more expensive if fixed later. But that depends on your definition of bug. Perhaps thats something to be agreed upon first. In my book it is also a 'not matching expectation in this release'. Like, a missing functionality. This could cost real money, so its more obvious then. Some features though might not cost more (like for websites, CSS changes?) now than early. Or, not that significantly more. Still, I don't have data.
Feb
7
awarded  Student
Feb
7
asked Is it significantly costlier to fix a bug at the end of the project?
Jan
20
awarded  Supporter
Oct
18
awarded  Autobiographer