I was scrolling through the net and came across this interesting topic on "Technical Debt". It is a strange name.. but I am sure everyone of us has been a part of it..
Either the culprit :P or victim :(.
It is basically the technical things that we say "WE WILL DO IT LATER".. Or in a simple terms the pending "TODOs" ..
> It could be a misspell of variable name in various source files.
> It could be unorganized imports in a java source.
> No unit test cases => most common one.
> No proper documentation, sometimes not even comments..
The reasons could be anything starting from carelessness to project pressure :)..
Some of them are unintentionally , some intentional, former is fine we cannot track[only reviews can help], latter is something interesting to be discussed.
I came across this interesting article
http://blogs.construx.com/blogs/stevemcc/archive/2007/11/01/technical-debt-2.aspx
Enjoy reading
Monday, March 5, 2012
Subscribe to:
Posts (Atom)
-
Java Unit Testing: 1. Tool: JUnit. 2. Process: a. Sources has the new folder structure added for this NGRP->UnitTesting....
-
People name it "Learning Curve", I would say its very very zig-zagged in my case. Yes I just went through various little interesti...
-
Dears, For past few days I was exploring the tool selenium it is very popular in the agile world for testing web applications. To descri...
