|
|
|
|
|
|
by 5h
4070 days ago
|
|
|
I've come up against this many times over. When it stems from over-enthusiasm for using recently discovered features or concepts I've reliably changed a trend-toward-complexity by picking a small section & re-writing it in a simpler/more elegant fashion, then proposing to the author something along the lines of "can we make it _all_ that simple"? The subtle (or not so subtle) creation of a challenge towards simplicity has worked well with coders near the beginning of their career. |
|
|
I've come to learn that the best way to make your point in any programming debate is to go the extra mile and produce something people can see. Rhetoric and metrics are nice, but what really makes an impact is presenting an actual example of a refactoring.
For the original poster: Is the original code tested? What do the tests look like? Overly complicated unit tests are an indication that things aren't well factored. If you can present a simplification of tests along with your simplified revision of code, that may really speak to how your solution is better.