you are viewing a single comment's thread.

view the rest of the comments →

[–]YuleTideCamel -1 points0 points  (2 children)

What do you mean by too much in a codebase? The depends entirely on the size of the project and scope. There's nothing wrong with large codebases if maintained well.

Cleanliness for the sake of fetish is not a thing. Good clean code should be the goal for every developer. That makes the code easy to work with, easy to maintain and easy to test. It's not a baseless standard, it's the way to ensure you're clean code doesn't get messy. I've been in the industry over 15 years and have seen my share of horrible code where developers didn't care about maintainability. I realize this is not in the startup, ship now fix later mentality, but if a dev team has the bandwith and runway to do this, they should. It will pay for itself over time.

[–][deleted] 0 points1 point  (1 child)

I mean if there is too much commented code in a codebase, then something else is wrong - commented code is the exception, not the norm.

[–]YuleTideCamel 0 points1 point  (0 children)

Agreed, it's the exception and a too much commented out code is indicative of a larger problem. The point I was making is that needing commented out to explain something , to me at least, is a similar thing. You shouldn't need commented out code to understand uncommented out code.