Working in a similar company, they don't generate as much revenue but the codebase is that really messy mix of data and implementation details, imperatively bru

Working in a similar company, they don't generate as much revenue but the codebase is that really messy mix of data and implementation details, imperatively brute-forced into a "stable" lucky build I took the e2e approach, since making any changes is having that huge domino-effect of breaking everything else. I think it's really important to setup a proper build/e2e CI pipeline with instant Slack reports, and run this pipeline on every commit, from this point you can just add specs to fully cover it and then it can be released nightly without a fuss