Most of us have heard the expression “Less is more”, but have you thought about what that means for software quality?
If you’re not familiar, less...
For further actions, you may consider blocking this person and/or reporting abuse
Great article Matt, and something I've fallen fowl of myself. Trying to prune code that's no longer used is tough but immensely useful.
I find this all the more relevant when using any kind of relational databases. Having a table with a lot of columns, most of which are never used, is just bad for everybody involved.
Great post as always though!!
I'm currently rediscovering my code mojo, as the only coding I've been doing for a long time has been ad-hoc scripts for IT network engineering tasks... but I couldn't agree more! A couple of years ago I took a security policy on a firewall from 1800+ rules down to roughly 70 rules, and the difference in maintainability and general ease of operation from that point on was huge. A distant comparison perhaps, but my thought's were similar in that, the rules that are gone aren't a problem anymore... but, 12k lines of code has to be some kind of record.. nicely done!