> I've worked on PHP (and non-PHP) applications with (tens of) millions of lines of code
Grats, you're a hero. Now, you're a hero. You can solve the application in your paper notebook. That does not explain why computers should know some correctness and not help you, because you're a hero. I now have the legacy of webinars. There's no webinar archives, only runtime config, blueprints, there's user forms that are only processed in batches by queue, there's 3 levels of nesting in webinars. And there's existing code with wordpress repeaters and such stuff that is working somehow. So my current task is to multiply non-existing webinars to non-existing form submissions and multiply that to wordpress and 3 levels of webinar nesting, and get a solution in a maximum of one week. Suggested solution - "we know the correctness, so you have to tell your manager - you need to completely rewrite existing logic with 10000 small methods with exceptions, then catch it everywhere, then write tests, and then debug it at runtime" for the future. That strategy followed by firing out or leaving. It should be fixed in the shortest possible way without rewriting your code. And, it should work fast using massive select/insert to reduce page loading time. If I started to split that 100 repeating fields into simple SOLID methods - it would take a month. I haven't a month, and nobody can give me a new job. So I MUST use non-breaking errors to do it faster. And the community doesn't want to implement handy solutions because they are tired of simple things (because they guess that simple things are always small instead of being plain scripts). Best! Just not enough good words. Thanks for attention.
