News for hackers. Stuff that matters.
Re:The Way We Look at Technical Debt Is Wrong by amelius on Wednesday May 13, 2015 @03:47PM (#9541493)
But a good programmer always sees a number of solutions to a particular problem. Let's say he sees 10 solutions. Solution 1 costs an hour to implement, but gives crappy code and he knows it. Solution 9 gives good quality code, but takes a week to implement, and he then has to sell this to his boss.

And then there's solution number 10, which requires the programmer to invent a new programming language, and requires at least a couple of months to develop. "You hired the best possible person for this job, so let me do the best possible job".

I just bet most people here wished they could always deliver the best possible code.

Re:The Way We Look at Technical Debt Is Wrong by crdoconnor on Wednesday May 13, 2015 @04:04PM (#9541596)
>But a good programmer always sees a number of solutions to a particular problem. Let's say he sees 10 solutions. Solution 1 costs an hour to implement, but gives crappy code and he knows it. Solution 9 gives good quality code, but takes a week to implement, and he then has to sell this to his boss.

A good programmer will try and improve code the code incrementally, and won't bother trying to sell anything.

Re:The Way We Look at Technical Debt Is Wrong by jaggederest on Wednesday May 13, 2015 @04:00PM (#9541574)
I think what you hear me saying is "never do anything less than perfect work". I'm saying "given your current constraints, don't choose a worse option when a better one is available". Those constraints include time, your skills and beliefs, the environment you work in, the project you're working on, and the problem you're trying to solve.
Re:The Way We Look at Technical Debt Is Wrong by cunac on Wednesday May 13, 2015 @04:04PM (#9541597)
I am sure that most developers want to deliver working code of reasonable quality (most likely not hacks)

I am sure that most product/project managers want feature as soon as they can think of it