Do you remember the part of education where they talked about tradeoffs? How making decision a means x, y, x good things and a, b, c bad things? Because it’s reading strongly like your system design methodology was “this is the path of least resistance so I’m doing that”.

Most code is not complex. Good code is usually very easy to read and understand.

Just because you can read and understand the queries you wrote doesn’t mean they’re efficient or that you’re using good design.

So yes. Stack Overflow is going to tell you to RTFM. Because someone needs to sit down with this mess, determine the pros and cons of the system design, and figure out where to start overhauling.

Thank you for signing up for Cat Facts! You will receive fun daily facts about CATS! >o<

My last role had no paradigm, conflicting inputs from multiple people you had to work with vs your management, and God help you if you prioritized one over another.

I’ve also been in roles where I “supported” people who were using an agile+waterfall hybrid, and my role included keeping an eye on their 6-12 month plans and making sure the backend things they would need would be ready when they’d need them, with the gentle understanding that they may not know what they need.

I’ve never seen a Scrum “team” that actually follows Scrum. Ask me about hour-long daily standups!