News for hackers. Stuff that matters.
Re:Solving the Wrong Problem (2011) by ukj on Wednesday October 02, 2019 @01:34AM (#21133655)
That depends on whether you see technical debt accrual as a 'meta problem'.

The faster you iterate without thinking long-term - the faster it accrues.

20/20 hindsight and all that.

Re:Solving the Wrong Problem (2011) by swatcoder on Wednesday October 02, 2019 @01:51AM (#21133719)
Technical debt is not any sort of problem in and of itself.

It can be accrued naively, which is an antipattern, but when that isn’t the case technical debt is a vehicle for leverage. You get more value from less work.

With all development efforts having a finite lifetime, and many having a particularly short one, wise exercise of technical debt becomes an essential skill for both project managers and developers.

Vilifying technical debt, and even prematurely mitigating it, are just as naive as inadvertently introducing it.

Re:Solving the Wrong Problem (2011) by ukj on Wednesday October 02, 2019 @02:03AM (#21133757)
Nothing ever is a problem 'in and of it self'. This kind of vacuous 'thinking' is not what I am talking about.

Holistically, if your system is meant to endure the test of time (think Google-scale), more technical debt is worse than less technical debt.

Re:Solving the Wrong Problem (2011) by swatcoder on Wednesday October 02, 2019 @02:51AM (#21133943)
> if your system is meant to endure the test of time (think Google-scale)

While some exceedingly few products have that destiny, it’s precisely the naive bias towards thinking that your project does that leads to wasteful over-engineering.

Products and projects are not the same thing. Most of the Google-scale products that you see leveraged tons of technical debt on projects along the way, some critically valuable and some certainly wasteful.

If you’re adding a feature to one of these products that are already at that scale, then your attitude toward technical debt will be different.

But effectively nobody reading this thread is doing that, and the few that are know who they are.

Most readers here are working on projects with near-term deadlines and development lifetimes measured in a few months or years. As much as judicious exercise of technical debt enables those projects to deliver on their requirements more quickly and for less cost, more is better.

Many of us come into the industry thinking otherwise because we’re drawn to the intellectual purity of clean systems, but that purity just isn’t what actually matters most of the time. It can take a while to accept and internalize that.

Re:Solving the Wrong Problem (2011) by s188 on Wednesday October 02, 2019 @04:17AM (#21134324)
Wow, that last paragraph is spot on. I found both your comments to not only be accurate and clear but also rather eloquent.

I've always felt we've misunderstood technical debt. It seems to be regarded as a problem with a lot of negativity surrounding it. Developers seem to fear being accused of introducing technical debt - like it's the worst kind of developer crime. But in reality, there is value in embracing it in early stage projects. As thinkingkong mentions below; 'Its only debt if it sticks around long enough to need to be dealt with.'

Re:Solving the Wrong Problem (2011) by ukj on Wednesday October 02, 2019 @03:58AM (#21134234)
>Nobody reading this thread is doing that, and the few that are know who they are.

That's the false dichotomy which earned me my stripes.

I used to think I am the former guy, then I realised I am the latter guy. The only thing that changed is that some time passed.

The hind-sight of my mistaken identity is that the systems I have been working on for 15 years became less, not more maintainable as a result of tolerating technical debt.

They also became Google-scale (which is what we were hoping for, but didn't believe at first).

I am the furthest thing from a purist. I am a filthy rich pragmatist who regrets having low-quality standards.

Re:Solving the Wrong Problem (2011) by s188 on Wednesday October 02, 2019 @04:32AM (#21134403)
Perhaps it's the fact that you tolerated the technical debt that got you to google scale. I've seen a few projects where developers aim for (as swatcoder so eloquently put it above) the intellectual purity of clean systems and then watch these projects fail to be delivered.

We'd all like to be a filthy rich pragmatist but I wonder just how much the 'low-quality standards' enabled you to achieve that. Seriously, I would love to be a millionaire with regrets about low quality code instead of being broke with junior developers pointing out my code smells and technical debt.

Re:Solving the Wrong Problem (2011) by ukj on Wednesday October 02, 2019 @04:38AM (#21134431)
Perhaps, but you can't determine whether a system is over or under-engineered a priori. Certainly not when you are racing a clock.

These kind of assertions are always after the fact. And in hind-sight I think we could've done a tad better.

I might be less-rich, but that's not even close to being broke. And the people I hire to clean up my technical debt would hate working here less.

Re:Solving the Wrong Problem (2011) by username90 on Wednesday October 02, 2019 @07:01AM (#21135102)
> If you’re adding a feature to one of these products that are already at that scale, then your attitude toward technical debt will be different.

> But effectively nobody reading this thread is doing that, and the few that are know who they are.

Aren't a large fraction of HN readers working at Google or similar companies?

Re:Solving the Wrong Problem (2011) by collyw on Thursday October 03, 2019 @03:35AM (#21144593)
This article rings very true for me at my current company, the tech lead is always off to add more fancy new tech to the stack, and we still manage to accumulate a ton of tech debt.

Adding a load of automated tests is the first thing we need to do start being able to iterate more quickly. (I view this as both paying down technical debt and solving the right problem). Thankfully that was discussed just the other day in our tech debt meeting (while the tech lead was saying how we need to add a Neo4j database, a Leucene search index and remote procedure calls - he had read an article saying how that is cool again).

Re:Solving the Wrong Problem (2011) by thinkingkong on Wednesday October 02, 2019 @01:51AM (#21133718)
Its only debt if it sticks around long enough to need to be dealt with.
Re:Solving the Wrong Problem (2011) by ukj on Wednesday October 02, 2019 @02:18AM (#21133814)
Short-term thinking is a form of technical debt. How important of a problem are you really solving if the solution is not meant to "stick around"?

https://en.wikipedia.org/wiki/Time_preference