2 ms·
The more I code, the more I like messiness. By that I don't mean bad code. I mean code where all techniques in and out of books are used together. For example,
by GuB-42 7y ago
The more I code, the more I like messiness. By that I don't mean bad code. I mean code where all techniques in and out of books are used together.
For example, a mix of exception and error returns, direct access to class members combined with accessors, etc... I like to see best practice rules being broken when there is a good reason for that.
Rule of the thumb: good code is short code. If your "tidying up" makes the code longer, then it is probably better to leave it as it is. What you are going to do is most likely add useless layers of abstraction or try make it abide by some made-up rule that shouldn't apply here.
As for "efficient" code. Most efficient code I see is actually quite good and readable. The worst code I see usually gives no fucks to efficiency. At least premature optimizers show some love to their code.