In my experience the 'traps' left by the DM, actually reflect the inherent complexity of the problem domain. Complexity it took months or years to fully understand, made out of corner cases and strange usage patterns that were never anticipated, and have been forgotten again since (forgotten, but still used, from time to time).
If you think this new trendy solution is going to be cleaner or less hacky, and still cover the same (or more) use cases, you're rather naive.
80% of the ugliness comes from getting the last 20% of the functionality (maybe even 90/10). It is trivially easy to re-engineer a system that is 80% less ugly/hacky, and covers 80% of the functionality of its predecessor. Then everyone slaps themselves on the back because the refactor is going great!.
If you think this new trendy solution is going to be cleaner or less hacky, and still cover the same (or more) use cases, you're rather naive.
80% of the ugliness comes from getting the last 20% of the functionality (maybe even 90/10). It is trivially easy to re-engineer a system that is 80% less ugly/hacky, and covers 80% of the functionality of its predecessor. Then everyone slaps themselves on the back because the refactor is going great!.