Skip to content

Comment on Google's ‘Gopher Team’parent

Comments

I would argue that bad code is already shit. There's no doubt that good code can be turned to shit too if it's being modified all the time with bug fixes, etc, without paying the required technical debts.

Not sure what your example of untouched code represents. The OP says that what makes code turn bad is accumulated local changes and bug fixes without thinking about the big picture. Of course if no one ever touches the code, its quality doesn't change.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.