Bad code is kudzu

paulgerhardt•about 2 hours ago

I’d argue Kudzu has visibility bias. It grows on sunny roadsides, railway corridors, and disturbed land. Basically all the places where people see it so attribute it to being more pervasive than it is. It's also mostly harmless[2].

Bad code is the inverse. It’s more pervasive than people think it is and builds up precisely in the places that are not disturbed. More like Privet than Kudzu. But that isn’t nearly as catchy.

If you want to dig into the quasi redemption story of why Kudzu isn’t this terrible evil we’ve given it to this was a decent episode of 99%PI at around the 18 minute mark[1].

[1] https://99percentinvisible.org/episode/roman-mars-describes-...

[2] https://www.smithsonianmag.com/science-nature/true-story-kud...

jamwise•about 3 hours ago

Bad code as an invasive species is the freshest take I've heard. I have a hard enough time arguing with people that tech debt isn't about bad code, but shifting priorities and requirements. This is going to be a really useful analogy for me going forward, thanks!

hansvm•about 2 hours ago

FWIW, I've seen the flip-side as well; solid coding patterns are easy for a person (or an LLM) to copy. To abuse the analogy a bit, your gardeners are happy copying whatever happens to be there, bad code will dominate that process unless actively removed, and the exponential nature of that arrangement favours removing trash code (weeds) early, much earlier than you might otherwise think.

omoikane•about 3 hours ago

Coincidentally, the same plant in Japanese is kuzu (クズ, or 葛), which shares the same pronunciation as the word for trash (屑). So bad code is trash.

YuechenLi•about 3 hours ago

I thought we solved the kudzu problem by having goats graze on them and rip them out by the roots, right? So maybe we should set goats on legacy git repos as well.

sigwinch28•about 3 hours ago

I will now refer to senior engineers with a bone to pick with a codebase as “hungry goats”.

ChrisMarshallNY•about 5 hours ago

> as a way to combat soil erosion

I heard it differently. I heard that it was imported for aesthetic reasons (like starlings).

Nasty stuff. We're starting to see it up here, in New York. I remember it well, from Maryland.

Yay climate change!

I often "hit the reset button" on projects. It used to be waiting until the pain was great enough, but LLMs make it a lot easier.

cvoss•about 4 hours ago

The article abridged the history too much. It was first imported as an exhibition of plants from Japan in 1876. It's usefulness as a ground cover in the US was understood later, and in the 1930s (Dust Bowl times) the USDA advocated farmers intentionally plant it as a way to hold down the soil. After that, you might say, it far exceeded its usefulness as a ground cover.

mc32•about 4 hours ago

I’ve heard similar.

The other thing is that its coverage estimation was off by at least an order of magnitude. It is a transition zone species. So they cover trees that are at the perimeter of forests or stands along highways. Back in the 70s aerial estimations were not as good as today’s. Their visual extrapolations were thus way, way off. It’s still a pest but it’s not “swallowing the South”.

rzzzt•about 3 hours ago

The hardware auto-detection tool in Red Hat Linux was also called Kudzu, before udev times: https://fedoraproject.org/wiki/Anaconda/Features/NoMoreKudzu

rglover•about 3 hours ago

This is a wonderful analogy.

Bad code is kudzu

⚡ Community Insights

Discussion (11 Comments)Read Original on HackerNews