Re:Technical Debt 101
by sheepmullet on Thursday June 26, 2014 @07:04PM
(#7951990)
I think a lot of it comes down to developers focusing on their own personal learning and development and not what is best for the current project.
Very few workplaces will let you work hard for 5 hours solving problems in the most time effective way and then spend the next 3 hours on your personal development.
On the other hand you can always spread the work over 8 hours and "experiment" with "on the job learning" leaving all sorts of sub-optimal solutions in the project. Then the next guy goes "Why on earth did Jim use X here?" and the truthful answer is because Jim wanted to learn more about X.
Re:Technical Debt 101
by silverbax88 on Thursday June 26, 2014 @10:18PM
(#7952481)
Yeah, I've heard several devs say something like 'Why did Jim do this...oh, crap, he was geeking out on this new thing.'
Developers tend to want to generalise everything because it makes it more interesting and has the appearance of good design. But generalising in one direction reduces flexibility in other directions. Better to copy and paste a bit at first and wait a bit before adding that extra extraction layer that generalises Foo.