4 ms·

Does your code work? Can your interested peers tell what's going on? If yes, great, your code is fine. Clean code is a meme foisted upon us by bloggers and the

• 0n34n7 5y ago
  Goes a bit deeper. Can you replace a source of data with another in a few lines (besides the new implementation) and not break a whole chain of dependencies and associates unit tests? (apart from "does someone knows what's going on") - i.e. code at scale.
• mdoms 5y ago
  Can your code be easily changed, or will a change in one place cause a domino effect all over your code base? Does a simple change in requirements require a change in one (or a few) places or is it a "shotgun surgery"? Is the difficulty of changing your codebase negatively affecting the viability of your business? This type of attitude to what's "fine" is immature and in my opinion represents a clear and present danger to businesses. I have seen several companies brought to their knees because their codebases were so difficult to change. And that's not even touching on issues like security, performance, reliability, etc. Code quality matters.
• danielrhodes 5y ago
  My criteria is: how long does code last during product iteration and spec changes. If it’s immediately thrown away every time requirements change, the code probably ain’t that great. If it is relatively easy to evolve, something has gone well. However, if you can’t change the code because it’s such a complex web of interdependencies where you musta modify the requirements, the code is very bad.
• deleted 5y ago
  [deleted]