News for hackers. Stuff that matters.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by ghiculescu on Tuesday July 24, 2018 @09:38AM (#17600865)
I think a lot of the time when a developer shouts “technical debt” what they are really shouting is “code someone else wrote that I’d rather rewrite than understand”. (The rest of the time is the same but they’ve understood it enough to think it’s a disaster area.)

I have found it’s best to not take tech debt complaints very seriously and instead look at actual success metrics. For example if every change to a bit of code introduces new bugs then that might be a reason to tidy it up.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by Bahamut on Tuesday July 24, 2018 @10:14AM (#17601177)
I’ve never seen technical debt referred to such at any workplace - all the time I’ve seen the term used to refer to poor or outdated design decisions that compromise the ability to deliver on business objectives in serious ways.

Complaining about technical debt complaints is an easy way to potentially bias oneself against recognizing real issues before it is too late and everything is on fire all the time. Be wary of any such blanket assumptions in engineering.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by repolfx on Tuesday July 24, 2018 @10:47AM (#17601491)
Lucky you :) I think there's a reason that post is currently voted to the top.

I'm lead engineer on my startup's project, not the CTO but reporting directly to him. Team of about 30.

There are of course many legitimate things that can be described as tech debt, files that got too large and convoluted over many patches by many people, that sort of thing. But I find I have to watch out for the concept of "tech debt" because a few engineers will abuse it if given the chance.

For instance they will insist that code that was just written fresh by a colleague is "tech debt" because they would personally have written it differently, when there are no meaningful differences between the two approaches.

They can claim that a design they don't understand the reasons for immediately (regardless of whether it's documented) is tech debt.

They can claim any feature they don't personally want to do or which is perceived as hard work will create tech debt. And so on.

I wrote the initial code and I'm close enough to the codebase still to be able to fairly thoroughly examine claims of tech debt. I'd say most such claims are actually not a big deal and do not justify any non-trivial investments of time to resolve.

Moreover the sort of engineers who pay down more than their fair share of legitimate tech debt are invariably the ones who complain about it the least.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by fhood on Tuesday July 24, 2018 @11:22AM (#17601822)
Sure, but are you differentiating between run of the mill bitching, and actual serious concerns? Because if I whine about x internal library in stand up, that is probably not important. But if I come to you in person and tell you that x internal library is introducing more bugs than saving time, I probably really mean/am concerned by that.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by Fire-Dragon-DoL on Friday August 03, 2018 @02:18PM (#17682192)
Freshly written code can easily be technical debt. An example of this could be "put a junior in a comolex piece of code and let him add a feature". That feature will work and probably is technical debt, because of bad design choices.

I've been on the other side of this. I was developing the frontend part to a series of http endpoints and my colleague was working on the http endpoints. He was creating some terrible code but I had no power at the time. When he was done, the code was functional, had various bug and a new feature was needed. I spent a week studying the code and managed to add a feature, which however was buggy due to how the code was written originally. I fixed all the bugs, and ended up totalling 4 weeks of work. This colleague was let go after this due to a series of circumstances, so I became the owner of the code. Then a new feature needed to be added but to do that i'd need to change various things in such code. Two weeks in, I still wasn't done. At some point I asked to be able to rewrite the code. I did, it took 2 weeks and was able to add the feature easily. I'm no genius but code that cripples you down from the get-go is tech debt. Tech debt is failure in software design, which ends up in unmaintainable code. I'd listen to anyone pointing at tech debt in my code, it means my code sucks, I made a big professional mistake and I need to correct it.

There is also voluntarily added tech debt, that's the one added by taking shortcuts. As long as you don't build new features on top of it, you are good.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by mcv on Tuesday July 24, 2018 @11:40AM (#17602001)

  > For instance they will insist that code that was just written fresh by a colleague is "tech debt" because they would personally have written it differently, when there are no meaningful differences between the two approaches.

  > They can claim that a design they don't understand the reasons for immediately (regardless of whether it's documented) is tech debt.

  > They can claim any feature they don't personally want to do or which is perceived as hard work will create tech debt. And so on.
Yeah, those things are not technical debt. But that doesn't mean that technical debt is a real issue. Technical debt isn't about whether you like or understand a particular approach, it's about whether the codebase as a whole is still maintainable, whether the bugs make sense and are fixable, whether new features can be added without stabilising the whole code base.

It's never the new feature that's the problem. If the new feature can't be added in a good way, it's the old codebase that has unhandled technical debt.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by jibal on Wednesday July 25, 2018 @01:47AM (#17607128)
> Technical debt isn't about whether you like or understand a particular approach, it's about whether the codebase as a whole is still maintainable, whether the bugs make sense and are fixable, whether new features can be added without stabilising the whole code base.

It's not about that either ... it's about things that were put off, generally for valid reasons at the time.

> It's never the new feature that's the problem.

What do you mean by "problem"? Many new features are inherently problematic.

> If the new feature can't be added in a good way, it's the old codebase that has unhandled technical debt.

That would only apply to waterfall development with infinite foresight. In the real world, wise people employ the YAGNI principle.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by 0xdeadbeefbabe on Tuesday July 24, 2018 @11:53AM (#17602169)
Ugh. Instead of redefining common usage you could just use a different word or words.

Edit: Is saying "bad design" or "ineffective design" going to lead to some fearful confrontation?

Re:Ask HN: As a CTO, what is your most frustrating problem w... by jibal on Wednesday July 25, 2018 @01:40AM (#17607110)
What common usage was redefined?

Where would you substitute "bad design" or "ineffective design" into the comment?

Perhaps this will help: http://wiki.c2.com/?TechnicalDebt

Re:Ask HN: As a CTO, what is your most frustrating problem w... by 0xdeadbeefbabe on Wednesday July 25, 2018 @11:28AM (#17610015)
Common usage is "I'd rather rewrite than understand the problem", as well as "I disagree with decisions that were made."

> Perhaps this will help: http://wiki.c2.com/?TechnicalDebt

Seriously, it won't. That's the point. People overload these words. It's a cute ideal definition though.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by jibal on Thursday July 26, 2018 @02:07AM (#17615371)
You are so full of dead beef. You wrote "Instead of redefining common usage you could just use a different word or words", but he used the word as correctly defined. It's a pity that you aren't helped by knowing what the word means, but that's your problem, and the consequence is that sensible people write you off as a silly troll.

Over and out.

P.S. Yeah, go ahead and downvote me, troll.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by 0xdeadbeefbabe on Thursday August 02, 2018 @11:49AM (#17672374)
Hey it's nothing personal. I'd apologize for trollishness, but I really believe what I'm saying.

Edit: I apologize for beating a dead horse.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by geezerjay on Wednesday July 25, 2018 @01:28AM (#17607077)
OP's usage and explanation of the term are spot on, and you miss the whole point if you conflate technical debt with bad design. One of the causes of technical debt is a change in requirements, and changing the initial requirements doesn't mean that the design was bad.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by 0xdeadbeefbabe on Wednesday July 25, 2018 @11:46AM (#17610148)
Common usage misses the whole point as well.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by geezerjay on Wednesday July 25, 2018 @01:49PM (#17611246)
Just because you personally misundertand a concept it doesn't mean everyone else is wrong.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by 0xdeadbeefbabe on Thursday August 02, 2018 @11:47AM (#17672352)
> I think a lot of the time when a developer shouts “technical debt” what they are really shouting is “code someone else wrote that I’d rather rewrite than understand”.

Is it obvious to you that it's not just me?

Re:Ask HN: As a CTO, what is your most frustrating problem w... by jibal on Wednesday July 25, 2018 @01:57AM (#17607151)
> Moreover the sort of engineers who pay down more than their fair share of legitimate tech debt are invariably the ones who complain about it the least.

Oh really? I recently contracted with an industrial firm where most of the programming staff copy and paste at the drop of the hat and have no idea what DRY is, and think that technical debt and refactoring are some fancy university CS theory that "practical" programmers like them have no use for. I explained to the manager at some length the development and maintenance costs of the massive technical debt of their 30 year old code base, while at the same time I tried to reduce it a bit with every submit.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by repolfx on Thursday July 26, 2018 @11:44AM (#17618352)
Good for you :)

I think your situation sounds a bit different, where the manager either isn't very technical or isn't technical enough. Otherwise they'd be able to see the problem for themselves.

What I'm talking about are employees who have managers who understand the value of refactoring. What I find is that the people who get stuck in and most unambiguously improve hairy bits of the code (with full support of management) are usually not the ones who complain loudly and publicly about tech debt.

Speaking as a manager for a sec here, what I'd watch out for in your case is to not be seen too much as a complainer. Rather than say "this codebase is shit why does nobody care" look at it as, "hey guys! why not come to my interesting 10 minute lightning talk on my favourite refactoring technique" and maybe don't phrase it as about tech debt if they aren't responsive to that kind of analogy.

Managers in particular probably know their codebase is shit even if they aren't very technical, but labelling things as "tech debt" is always tricky because it's entirely possible that the debt was created by colleagues or those very same managers themselves, and whilst financial debt is well defined and measurable, tech debt is just an analogy. They may not even agree that any given bit of code is a problem.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by jibal on Friday July 27, 2018 @04:48AM (#17624497)
> I think your situation sounds a bit different

Even if so, that's not relevant; you said that people like me "invariably" don't exist.

> where the manager either isn't very technical or isn't technical enough. Otherwise they'd be able to see the problem for themselves.

No, that's entirely wrong. As I clearly stated, it's the programming staff who can't see the problem. They are the people who never complain about technical debt while also never reducing it, contrary to your statement. That's the point, and your "good for you" is point-missingly dismissive.

> Speaking as a manager for a sec here

Just don't; I've been developing software since 1965 and I don't need your lectures (which are based on a complete lack of knowledge and erroneous assumptions about the software manager at that firm and my relationship and interactions with him), I simply pointed out that your sweeping generalization about who reduces technical debt and who points it out is erroneous. That's all. Period. The end. I won't respond further.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by thiagooffm on Tuesday July 24, 2018 @10:57AM (#17601582)
It might be upvoted because people find it catchy. But if you have ever wrote code in your life, you know that person who wrote about it got no idea whatsoever about software development.

I'll upvote it as well, as it is possibly the thing with the least amount of intelligence that I've read so far in my life.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by waterlink on Tuesday July 24, 2018 @10:27AM (#17601299)
> Complaining about technical debt complaints is an easy way to potentially bias oneself against recognizing real issues

Would you agree that we should think about specific issues that are slowing us down, and fix them one by one, starting from the worst ones?

(worst in sense of biggest slowdown/pain levels)

Re:Ask HN: As a CTO, what is your most frustrating problem w... by Bahamut on Tuesday July 24, 2018 @10:56AM (#17601565)
Sure, but my point was one should consider complaints as signal that the situation should be monitored/investigated so that the general outlines of an actionable plan can be crafted if there are potential areas of risk, or in the most serious situation, an actual plan.

Blanket painting of a class of complaints doesn't help them or you accomplish business objectives better long term.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by ghiculescu on Tuesday July 24, 2018 @11:26AM (#17601862)
We agree more than you think.

Most complaints about tech debt are not worth actioning, but that doesn't mean you shouldn't listen to all of them and try to filter the signal from the noise.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by fhood on Tuesday July 24, 2018 @11:09AM (#17601693)
This doesn't match my observations at all. In fact, way more importantly, often what is being shouted is, "we are creating more technical debt than we can possibly handle by doing X in Y way to meet Z deadline, this is going to bite you in the ass after we all switch teams/companies because nobody wants to deal with this."

Edit: If developers are warning the CTO that there is an issue with technical debt that should be a warning flag. Particularly if these are senior/experienced developers who understand the insane costs of re-writing production code.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by ghiculescu on Tuesday July 24, 2018 @11:34AM (#17601932)
> we are creating more technical debt than we can possibly handle by doing X in Y way to meet Z deadline, this is going to bite you in the ass after we all switch teams/companies because nobody wants to deal with this

This one doesn't require you to read between the lines, people usually just tell me that directly :)

Your mileage may vary - in my experience this is another one of things where it's not actually true most of the time. Note how it's a really easy to claim to make, and basically impossible to disprove ("at some unknown time in the future something bad will happen unless you let me have my cake now"). To me that's a warning sign that it might be wrong.

As a leader (or CTO or whatever) your job is to make the call. And if it turns out you were wrong and there is literally nobody who wants to touch the mess, well the buck stops with you and you have to clean it up.

I'm happy to take that bet!

Re:Ask HN: As a CTO, what is your most frustrating problem w... by nojvek on Tuesday July 24, 2018 @08:58PM (#17606190)
Or you know, the CTO could quit. I’ve seen this happen multiple times. Teams are in max feature mode, introducing a ton of code duplication, inconsistent abstractions and hidden assumptions. Team members get fat bonuses. For the next round of features, they can’t be as fast since they have to fix the mess they created to add new things without breaking old ones. So one by one they start switching to the team working on the shiny thing. New developers are hired, they realize the mess and nop out.

The harsh truth, which is evident from the thread, very few companies/managers actually reward fixing code debt.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by Buttons840 on Tuesday July 24, 2018 @12:24PM (#17602514)
> a lot of the time when a developer shouts “technical debt” what they are really shouting is “code someone else wrote that I’d rather rewrite than understand”

There's a paradox in this viewpoint. On the one hand you believe that your developers are so immature that they automatically shout "tech debt" for any code they didn't personally write ("only MY code is good"), then on the other hand you're confident that the code produced by these immature developers is actually just fine and doesn't have any technical debt.

I know you're not speaking in absolutes, so you may be right. You especially may be right about your own specific situation. However, I think a lot of people who have this viewpoint are simply kidding themselves into believing that "everything is awesome, surely there couldn't be any problems because I am the team lead".

Just remember the general form of the argument is "my team is great and talented, but I can't trust what they're telling me". It might be the case, but be careful of your own biases.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by itsdrewmiller on Tuesday July 24, 2018 @08:59PM (#17606191)
This is not a paradox (or a contradiction). Many developers prefer writing code to reading code. They may be perfectly good at both, and still err on the side of claiming that they need to write code rather than read it.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by jibal on Wednesday July 25, 2018 @02:05AM (#17607170)
You mean contradiction, not paradox. (A paradox is a contradiction that can't be resolved because both branches seem to be undeniable.) The contradiction stems from hyperbole (a type of lying) and other forms of nefarious (insincere, intellectually dishonest, aimed at winning rather than truth-seeking) rhetoric.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by mabbo on Tuesday July 24, 2018 @10:21AM (#17601239)
> “code someone else wrote that I’d rather rewrite than understand”

I'm not disagreeing, but there is something to be said for writing code that any idiot can understand so that future developers don't even want to rewrite it, and can maintain it.

I've landed in code bases on both ends of the spectrum, and I never asked management to rewrite the well-written ones.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by omeid2 on Tuesday July 24, 2018 @10:27AM (#17601292)
In a wicked way, people who write that kind of code never get credit for it, and often lose leverage of their job.

I am not saying that writing convoluted code is good, no, but I can tell, even if based on personal experience, that barely anyone talks about "wow, this is such a straight forward code" or gets promoted for "everyone can understand your code!".

It is a weird dynamic that gets worst by having non-technical managers, and the reason why I believe team leaders should be hands-on in software development and involved with code review.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by waterlink on Tuesday July 24, 2018 @10:32AM (#17601348)
Let me get this straight:

Person A, a programmer, who writes easy-to-understand code, but takes a bit more time to finish their tasks

Person B, a programmer, who writes dirty code, but takes much less time to finish their tasks

The current non-technical manager will see only one part of the picture and promote Person B. Moreover, Person A might get in trouble, and pressure to “compromise on quality.”

Within a short-term, it is understandable.

Within a long-term, this is a disaster scenario!

So should the “code quality” be part of a performance portfolio of the developer when it gets to promotion time? And how do we get there?

Re:Ask HN: As a CTO, what is your most frustrating problem w... by monocasa on Tuesday July 24, 2018 @10:42AM (#17601438)
I've also seen

Programmer A writes straightforward code that's easy to change and understand.

Programmer B writes convoluted "clever" code that completely falls apart when requirements change, or even just in production because their clever solution didn't account for all of the edge cases.

Now Programmer B has to save the day consistently, and therefore is seen as the person saving the company, when the problems were all of Programmer B's construction to begin with.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by hinkley on Tuesday July 24, 2018 @02:00PM (#17603476)
If you are a CTO and you haven’t had the “no more heroes” conversation with your employees, then it is my long reasoned opinion that you are being negligent. I can’t trust “leadership” like that.

And if you don’t take “I can’t trust you” as the highest insult a developer can give, then you are in the wrong line of work.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by linuxftw on Tuesday July 24, 2018 @11:30AM (#17601900)
I would expand upon this and say that Progammer B doesn't ship the code at all, it wouldn't pass code review muster.

Unless we're talking about a seriously silo'ed org, or Programmer B is actually "Team B"

Re:Ask HN: As a CTO, what is your most frustrating problem w... by monocasa on Tuesday July 24, 2018 @11:50AM (#17602132)
A lot of teams are a cult of personality around one developer. Particularly if there are a bunch of juniors on the rest of the team, Programmer B can usually get anything through code review with the 'ol "of course it's complicated, that's why _I_ am the one working on it. It's not for mortals to understand".
Re:Ask HN: As a CTO, what is your most frustrating problem w... by hinkley on Tuesday July 24, 2018 @02:02PM (#17603499)
Treat every question about your code as feedback. If multiple people ask the same question you have a problem that needs to be fixed. Documenting the gotcha should be your last resort. Implying incompetence isn’t even in the board.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by waterlink on Tuesday July 24, 2018 @11:38AM (#17601980)
Yeah, that is probably a few first months of a start-up (or even first year).
Re:Ask HN: As a CTO, what is your most frustrating problem w... by zenogais on Tuesday July 24, 2018 @11:18AM (#17601775)
^ This is pretty much standard at any startup in my experience.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by waterlink on Tuesday July 24, 2018 @11:39AM (#17601994)
This is not just bad. It is also unfair.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by phyller on Tuesday July 24, 2018 @10:43AM (#17601443)
You have multiple engineers working with each other on the same code base, reviewing each other's code before it can be merged into the main branch.

Then you start to find which engineers the other ones don't like to work with.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by hinkley on Tuesday July 24, 2018 @01:57PM (#17603447)
The real value of that sort of person is in the leadership they can provide and not the mountain of dramatic code that everyone mistakes for brilliance.

I would and do advise anyone who possesses that sort of clarity to push for more responsibilities. They should be involved in all of the major problem solving discussions.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by collyw on Tuesday July 24, 2018 @10:39AM (#17601406)
Yes, good code is a lot harder to spot than bad code.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by mmt on Tuesday July 24, 2018 @05:26PM (#17605092)
At the risk of sounding too glib or reductio ad absurdum:

The best code is impossible to spot, because it's not even there.

Put another way, a truism I've often heard from the most senior programmers (especially in the context of critiques of LOC as a measure of productivity), is that their best work is often writing less code, or outright deleting existing code. It stands to reason that this kind of work is much more difficult to spot if all one looks at is the codebase in its current state.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by jibal on Wednesday July 25, 2018 @02:22AM (#17607230)
See "The Most Beautiful Code I Never Wrote" by Jon Bentley.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by waterlink on Tuesday July 24, 2018 @10:25AM (#17601274)
It seems like:

“rewrite” is in sense of “I don’t even want to understand it, going to just delete it, and implement anew”,

VS

“refactor” is in sense of “I had to spend quite a while trying to understand this code, and I think it can be improved, so that the next developer doesn’t have to spend this time.”

Re:Ask HN: As a CTO, what is your most frustrating problem w... by MaxBarraclough on Tuesday July 24, 2018 @10:37AM (#17601384)
See also "Chesterton's fence"
Re:Ask HN: As a CTO, what is your most frustrating problem w... by sixstringtheory on Tuesday July 24, 2018 @10:59AM (#17601601)
That is a fantastic tidbit, TIL. This is pretty much what I had in mind to refute the assumption the earlier parent made about rewrites being desired so code doesn't have to be grokked. IME, the tech debt we complained about was in situations where we knew what we had to do to write a new feature, and why it wouldn't work because of the decisions made previously, and the monumental amount of work involved in putting just one more bandaid on that system, instead of just fixing the dang data model.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by ben509 on Tuesday July 24, 2018 @11:57AM (#17602214)
That makes me wonder: if I fix something, if I set up Chesterton's fence, how can I make it a bit more obvious why I'm putting that fence there for the benefit of future us?
Re:Ask HN: As a CTO, what is your most frustrating problem w... by gknoy on Tuesday July 24, 2018 @12:29PM (#17602573)
At the risk of sounding snarky, I feel like a block of code comments explaining the naiive approach that was rejected, as well as the particular edge cases that this is handling which the simpler generalized case doesn't handle, would help a lot for that.

I realize that as developers we often glaze over the comments (my editor even shows them as low contrast grey), but docstrings and code comments can be tremendously valuable when trying to understand why something needs to do things a particular way.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by MaxBarraclough on Tuesday July 24, 2018 @12:09PM (#17602352)
The usual code-comments/self-documenting code/git commit descriptions, no? If a long-form explanation is justified, wikis are cheap.

I see no excuse for leaving the reader to guess at what on Earth you were thinking. Implementing a wacky solution is sometimes a necessary evil. Incomprehensibility isn't.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by hinkley on Tuesday July 24, 2018 @02:06PM (#17603529)
I am downright militant about people not relocating code and breaking the commit history.

When I see WTF code, I want to know what story it was associated with so I know why the fences were erected. Sometimes they are right and I need a complex solution. Sometimes they were accomplishing something the hard way and there was an easier spot to achieve the goal.

Basically I am fixing two bugs. The old one again, and the new one.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by mabbo on Tuesday July 24, 2018 @08:27PM (#17606025)
I just love doing that part. I wish I could be paid to just refector shitty code bases all day.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by maxxxxx on Tuesday July 24, 2018 @10:24AM (#17601261)
There is a level of luck involved in producing well written code. Sometimes your assumptions turn out to be correct and sometimes a big requirements change comes and turns your code from simple to super complex.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by MaxBarraclough on Tuesday July 24, 2018 @10:31AM (#17601335)
Sure, a giant-ball-of-mud codebase might be the result of changing requirements and assumptions, but it could be the result of laziness/unskilled development.

There's a skill to writing readable, ideally self-documenting code. If that skill is wanting, even the most stable requirements won't save you from the mud.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by mixmastamyk on Tuesday July 24, 2018 @10:40AM (#17601413)
> could be the result of laziness/unskilled development.

Or not being allowed/kept too busy to fix it.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by maxxxxx on Tuesday July 24, 2018 @10:36AM (#17601378)
Correct. But don't forget that it can also go the other way. The best code writing skills can be defeated by ever changing requirements. Besides code writing there is a also a skill in being disciplined about requirements changes.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by phyller on Tuesday July 24, 2018 @10:40AM (#17601415)
From this point of view, I guess you should make an exception and treat tech debt complaints more seriously when it is coming from the devs who wrote the original code.

Sometimes in order to meet business needs and get things out the door you have to cut corners that you need to go back and take care of later, or you are crippling the future growth and stability of the project. I like your final point "if every change to a bit of code introduces new bugs then that might be a reason to tidy it up".

I think sometimes proper testing is the first thing to go in a time crunch, and good tests improve velocity. If you know that the entire app is being tested automatically, you can develop a lot faster and more fearlessly. Plus writing good tests inherently makes the original code better. You find and fix hidden bugs, and you refactor the code to be more testable which makes it better in other ways.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by waterlink on Tuesday July 24, 2018 @11:36AM (#17601961)
> From this point of view, I guess you should make an exception and treat tech debt complaints more seriously when it is coming from the devs who wrote the original code.

Oh, that is quite an interesting idea. If the author themselves acknowledges there is a problem—there should be a real problem.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by convolvatron on Tuesday July 24, 2018 @01:20PM (#17603095)
the other way works too. any developer should be able to discuss at length the compromises made and the weak aspects of any project. every piece of software has a long list of potential improvements in clarity, verification, efficiency, generality, etc.

when I first heard the term 'technical debt', I thought it was fantastic that we had a shared name. but as someone else pointed out in this thread, the normal compromises one makes because of schedule and lack of importance are really a different thing entirely than a codebase that is failing structurally.

normal compromises can be ignored, and often aren't even compositional. thats the kind of linear, easily repairable stuff I think should be called 'debt', and it isn't scary at all. you overcome it at some later date when and if it makes sense. maybe debt isn't the right word, because you aren't borrowing failure from some abstract ideal, you're just choosing to trade of time for quality, which every effort in every field has to do.

structural issues that compound exponentially, and make it increasingly difficult to make any changes at all are a different thing (call it 'crippling debt', idk). its a metastatic cancer and can easily be fatal.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by sockgrant on Tuesday July 24, 2018 @10:40AM (#17601414)
Yep. I’ve seen this in a number of startups. Didn’t see it as much at big firms.

Reading code is harder than writing code. So, IMO, lazy or slow engineers would rather complain that code should be rewritten than refactored. Or that different frameworks / languages should be used.

Ive entertained them a few times before realizing that it was a waste of time and often things came out worse.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by talmand on Tuesday July 24, 2018 @11:20AM (#17601803)
I don't think I would agree with the usage of the word "lazy" to describe coders that want to rewrite entire chunks of code. They may have their invalid reasons for wanting to do so, but I wouldn't call that being lazy.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by bjconlan on Tuesday July 24, 2018 @07:09PM (#17605648)
Yeah, I feel that this is by and large the scenario I've witnessed. Not necessarily pushed by slow/lazy engineers but those that are bored with tried and true solutions that have some 'difficult corners to chamfer'. I think the problem with developers is that they want to solve a problem in a very recognisable pattern playing into the Asperger's like nature held by most perfectionists but unfortunately ends up much like your have outlined (but now they have some hot new technology on there resume so moving onto different problems is usually more desirable than re-fixing the new problems they've introduced to solve again)
Re:Ask HN: As a CTO, what is your most frustrating problem w... by leejo on Tuesday July 24, 2018 @10:39AM (#17601401)
> I think a lot of the time when a developer shouts “technical debt” what they are really shouting is “code someone else wrote that I’d rather rewrite than understand”

IME it can be one of many things, including but not limited to: was written by someone who is no longer with the company, doesn't have (relatively comprehensive) tests, doesn't have any documentation, commit messages don't explain the codes' reason for being, is a blocker to getting more lucrative features out, nobody understands it ergo nobody dares touch it, written in a language that is hard to recruit new devs for, is working fine now but will be a problem in x months/years time, contains potential WFIO points but is business critical, is difficult to scale, and possibly more.

What i'm saying in the above is that it's possible to write something in a easy to recruit for language, that scales well, is comprehensively tested, has no nasty bugs, but could still be considered technical debt because the original developer(s) wrote useless commit messages, no documentation, and then left the company.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by ex_amazon_sde on Tuesday July 24, 2018 @11:25AM (#17601853)
> "code someone else wrote that I’d rather rewrite than understand"

I've never seen this happening but it seems to be common in hipster environments.

Do not hire people that want to rewrite something just because it's not written in the popular language/framework of the year.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by maxxxxx on Tuesday July 24, 2018 @09:44AM (#17600911)
Totally agree. And often if you make the effort to understand the code you can refactor it with reasonable effort to address the real problems.

A lot of rewrites I have seen just traded one set of problems with a different set of problems.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by carlmr on Tuesday July 24, 2018 @10:12AM (#17601160)
I like the boy scout rule. Clean up and leave it nicer than you found it. Focused mostly on things related to your change. Big rewrites cause big issues.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by pmarreck on Tuesday July 24, 2018 @10:29AM (#17601319)
> Big rewrites cause big issues.

Those issues are very much constrained by a very good test suite.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by carlmr on Wednesday July 25, 2018 @02:40AM (#17607289)
I'm just going to ask which company you've been at that a) needed a big rewrite and b) had a "very good test suite". In my experience there's not much overlap here, especially because one of the reasons why a) is necessary is often that there's so little modularization that b) is not possible to exist.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by pmarreck on Thursday July 26, 2018 @09:40AM (#17617381)
> a) needed a big rewrite and b) had a "very good test suite"

Desk.com has a gigantic Rails codebase and a test suite that runs for... well when I left them it was 40 minutes long but it's probably longer now. But it did save us many many times.

I'm working at another company right now (can't disclose) and they also have a rather large Rails codebase and a fairly good test suite.

I think the Rails community historically has been pretty great at communicating good test/design decisions, so the modularization issue you mentioned is largely moot.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by carlmr on Monday July 30, 2018 @10:12AM (#17644501)
Like I said, you wouldn't want a huge refactor of the code there, because it's already tested and probably very testable the way it is. Otherwise it wouldn't have this good test suite.

Modularization is the issue, not size. If you have a big project and it's nicely modularized you probably already have good tests for it, but don't need to refactor. If it's big and needs a huge refactor it's probably hard to test and doesn't have appropriate tests.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by waterlink on Tuesday July 24, 2018 @10:35AM (#17601371)
Unless your test suite needs a rewrite, as well…

(Better refactor, of course)

Re:Ask HN: As a CTO, what is your most frustrating problem w... by camgunz on Tuesday July 24, 2018 @12:01PM (#17602249)
Your test suite should essentially be your requirements. If it's out of date, it's the first thing you should update. Adding features or changing your requirements without updating your tests is the essence of tech debt: you're delivering features quickly at the expense of future work and brittleness.

I agree it's pretty common though. I've also seen huge test suites of only unit tests, no integration tests. As a result, you have no assurance that your refactors work because changing the inner workings fundamentally requires you to change the unit tests too, and nothing checks the top-level interface.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by Shorel on Tuesday July 24, 2018 @01:43PM (#17603328)
You either rewrite the tests, or the code.

Not both at the same time, in my opinion.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by collyw on Tuesday July 24, 2018 @10:42AM (#17601428)
You mean a test suite that will take longer to write than the rewrite?
Re:Ask HN: As a CTO, what is your most frustrating problem w... by maxxxxx on Tuesday July 24, 2018 @10:46AM (#17601473)
He means one that slowly goes out of date because nobody has the time to change it when the requirements change.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by Balero on Tuesday July 24, 2018 @10:11AM (#17601144)
Whilst I find that this is definitely a good portion of technical debt, the biggest section I see comes from the intersection of reusing code and moving requirements.

Often when some code reuse gets nested (re-using something that is re-using something), then having to tweak it a little at the end to get to the right state.

Basically a bunch of development is done towards a local maximum. But looking at it as tech debt can bring it up to a global maximum.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by dsfyu404ed on Tuesday July 24, 2018 @09:40AM (#17600886)
>I’d rather rewrite than understand

The people with this attitude seem to be the best sources of hard to understand legacy code.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by waterlink on Tuesday July 24, 2018 @10:37AM (#17601386)
That is true.

While I have to agree that it takes the pain and struggle to understand some code out there, it is still worth doing, and a good indicator of the quality of the code, and the fact that it needs improvement.

Also, I believe leaving some “bad code” without understanding it, and just rewriting it, _might be_ unprofessional…

Re:Ask HN: As a CTO, what is your most frustrating problem w... by JamesBarney on Tuesday July 24, 2018 @11:49AM (#17602107)
100% agreed.

Most code complaints are this code sucks. But honestly most code looks like shit, and battle tested code that's been heavily patched to work well and cover lots of special cases especially lookS like shit.

But when there is a documented problem with a piece of code that is important and worth refactoring because it can't be mediated otherwise then of course you need to fix it.

For example recently a previous dev split the data model across persisted HTML and rows in a database. Which means it was very easy for the domain critical computations(driven by the database) to display one set of inputs to the user, but calculate with another.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by hinkley on Tuesday July 24, 2018 @01:47PM (#17603372)
This isn’t a comparative literature class. I don’t have the luxury of spending all day savoring the clever hack you put in your code. I’m trying to fix a bug or add a feature. All the frippery just pulls me away from the problem at hand.

There was an agile coach I heard an interview with who insisted that Tech Debt was the wrong analogy. He preferred Wear and Tear. I think the problems of kludgy or overclever code are more apparent if you think of it that way.

At the very least, the main thoroughfares of the codebase need to be clean and free of dangerous obstacles.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by corobo on Tuesday July 24, 2018 @10:50AM (#17601515)
I more see technical debt as "// TODO: Refactor this into its own class rather than do it here" written by a dev 4 devs ago
Re:Ask HN: As a CTO, what is your most frustrating problem w... by fnl on Friday August 03, 2018 @05:39PM (#17683849)
Interesting that this reply is voted highest, as it doesn't actually answer the question, but rather suggest to ignore the entire issue.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by digikata on Tuesday July 24, 2018 @10:49AM (#17601510)
If you think it's mostly unfamiliarity, then that's a great opportunity to suggest some time spent to document that code (and/or operations thru that code). It helps w/ the understanding, and should be a precursor to figuring out if a redesign could help that "tech debt".
Re:Ask HN: As a CTO, what is your most frustrating problem w... by lvncelot on Tuesday July 24, 2018 @12:51PM (#17602798)
I'm sorry, but if you are going to dismiss a co-workers opinion like that, it seems like you don't value their work at all. Do you trust them enough to write decent code, but not enough to value their concerns? That doesn't seem fair to them.
Re:Ask HN: As a CTO, what is your most frustrating problem w... by refulgentis on Tuesday July 24, 2018 @03:40PM (#17604254)
This is _so_ true. I have a unique career, no CS education, built a startup to scratch my itch, had no teammates on my codebase, worked on it for 5 years, sold it, now I've been at (insert FANG) for 2 years.

On my own, I would look at code I wrote 6 months ago, wonder what idiot wrote that, then figure out if it was actually bad, or I just didn't understand it.

With staff turnover and a lack of incentive for engineers to prioritize shipping (thats the manager and PM's problem), there's a heavy bias to "It's bad, rewrite it" rather than "Oh, it gets the job done, I just didn't understand it, let me research and comment the code". _Tons_ of time is wasted.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by mcv on Tuesday July 24, 2018 @11:33AM (#17601922)
I think technical debt is a bit more complex than merely "somebody else's code". I've also written code that increased technical debt. I hated it, but when there's a hard deadline and not enough time, it's unavoidable. Better planning and coordination can prevent a lot of technical debt.

But mostly, it's decisions that seemed to make sense at the time, but now turn out to be wrong. Or simply the accumulation of fix upon fix, feature upon feature, without without doing a redesign based on changing requirements or lessons learned. If you don't work to stop it, entropy will add up and eventually turns the code into an unmaintainable mess.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by ben_jones on Tuesday July 24, 2018 @12:10PM (#17602363)
Nothing like the smell of software design truth bombs in the morning.

I'd add "this code I wrote is technical debt because I'd rather re-write it then create a proper test harness for all its bugs and edge cases".

Re:Ask HN: As a CTO, what is your most frustrating problem w... by muzani on Thursday July 26, 2018 @06:22AM (#17616332)
If that's the case, it should be documented better. Not documented more though. Too often, people add too much documentation to the point nobody reads it.

Instead of rewriting the code, there should be some effort to show figure out how it links and how it works together.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by technobabble on Tuesday July 24, 2018 @10:09AM (#17601131)
What success metrics do you use?
Re:Ask HN: As a CTO, what is your most frustrating problem w... by ghiculescu on Tuesday July 24, 2018 @11:39AM (#17601993)
Hard to give a one size fits all answer, it depends on your project. But some examples:

- speed of delivery (not so much hitting a public deadline as shipping it as fast as you thought you could internally)

- quality of final product (were there delighters that didn't get built because they were too hard)

- number of follow up bug fixes shipped shortly after the main project ships (did we ship a bunch of bugs and not realise until users found them)

- number of new users acquired from shipping the feature

Re:Ask HN: As a CTO, what is your most frustrating problem w... by Jach on Tuesday July 24, 2018 @12:22PM (#17602486)
How are you measuring these things?

1. It's one of my dreams to work at a place using prediction markets for internal estimates. Anything else feels worthless and engineers are incentivized into the "quadruple what you're currently thinking" estimate so they more often meet deadlines -- or try to "under-promise, over-deliver" except management rightly catch on to that one immediately. (As an engineer I still want to be a La Forge and work with other La Forges, even if Scotty[0] sometimes has a point; modeling managers as demanding children has some gaping model gaps.)

2. What I've seen is that many delighters aren't that hard, but they're often treated as "polish" that goes into the p3/p4 priority backlogs and maybe might resurface if a customer ever brings up a desire for that to the product management. What delighters have you seen that weren't shipped because they were too hard? Were they actually too hard, or was it just too much to get them done by some release date alongside all the other stuff so they get shoved to the backlog just the same?

3. Are you measuring bug count based on what customers report or internal bug reports? If internal, even if people aren't gaming this directly, it's still easy to get into a bad cycle where reported bugs get ignored and go unfixed which leads to fewer reported bugs. That might be mistaken for higher quality.

4. Is this one measured from surveys? Obviously not all features are directly customer visible so let's take something concrete like shipping an Observer mode for an RTS video game that shipped its big release a couple months ago. How would you measure the impact of getting new users from that one feature?

[0] https://www.youtube.com/watch?v=8xRqXYsksFg

Re:Ask HN: As a CTO, what is your most frustrating problem w... by waterlink on Tuesday July 24, 2018 @11:43AM (#17602051)
As a Lean practitioner, I love the last one:

> number of new users acquired from shipping the feature

Re:Ask HN: As a CTO, what is your most frustrating problem w... by thiagooffm on Tuesday July 24, 2018 @10:59AM (#17601605)
You sir. Have no idea about software development.

Extensibility is just as important as Bugfree software for some businesses. Actually, for most of them.

Technical debt hurts much more the extensibility of your code rather than raises the number of bugs.

Re:Ask HN: As a CTO, what is your most frustrating problem w... by Shorel on Tuesday July 24, 2018 @12:53PM (#17602818)
Do new developers in a project really use that term?

In my experience it is used by senior developers having dealt with the same systems for years.

But I don't work in a fancy startup or similar. YMMV.