3 ms·
>"Neat" code can be "simple" to maintain. "Messy" code can be "simple" to implement. I was thinking something similar recently. Good code should take the next
by collyw 7y ago
>"Neat" code can be "simple" to maintain. "Messy" code can be "simple" to implement.
I was thinking something similar recently.
Good code should take the next developer less time / effort to understand it than it took the original developer to write it (assuming similar levels of ability).
- bonoboTP 7y ago> the next developer And that's often you, just in a few months' time.
- collyw 7y agoTrue. And as I mentioned in another comment, I learned the most by building a system from scratch and maintaining git for 4 and a half years. If I couldn't understand a bit of code that had written more or less straight away, then it was usually time to refactor it.