I'm starting to realize that maybe the issue with my team is that they don't know how to break down complex problems into smaller parts that can be completed, tested one by one, allowing you to create save points.

To them it's either all or nothing... And once they're done, they cannot explain what they did other than it works..

@electric-ghost we are very agile... Just whatever is made is hard to reuse and fix it it breaks.... Because you can't isolate the issue to just one part and test it....

And that just goes back to bed design because they didn't actually understand the problem enough to fix it well...

Lol makes me think of some code I have dropped work with for part of my last project, the dev had a file that was around 14000 lines long and would be a total bitch to follow as you would keep jumping around from functions with like 15 parameters each, no object oriented programming, it was a nightmare to use. I ended up rebuilding it from scratch properly with seperation into classes / helpers / main logic loop, and it turned into like 5000 lines across multiple well organized files lol. Way easier to add functionality and debug now.