IME junior code (that violates DRY and SOLID) is usually fairly easy to fix. It's the overengineered code that's an absolute pain. The worst is code written by

IME junior code (that violates DRY and SOLID) is usually fairly easy to fix. It's the overengineered code that's an absolute pain. The worst is code written by a freelancer/temp. Freelancers often come in at a bad time. It's like when you see a tree stump and there's this charred tree ring that says there was a forest fire at one point. We have a piece of code which is Kotlin converted to JavaScript then Java then back to Kotlin. The worst are the ones who use it as a test bed for experimental technology. So work backwards. How badly are/were things rushed? Who built the code? Were they a bit too enthusiastic about new technologies or are they just happy with what works? Messy code isn't always a bad thing: https://www.joelonsoftware.com/2005/05/11/making-wrong-code-look-wrong/ https://www.joelonsoftware.com/2005/05/11/making-wrong-code-...