I actually ended up really loving this subject and had a great time working with my team mates, Josh and Ethan, over the course of our two projects. My main annoyances were the restrictive and awful JGameGrid library we had to use that completely went against all of the good software design principles they had taught us and wanted us to use. I could have a whole rant about how bad this library is, but I'll save that for another time (or if you ask me about it).

Both projects were very similar, in that they gave us a codebase and we had to fix any bugs and add a new feature to it. It was really eye-opening to see how not thinking ahead and not following good software design principles can really come back to bite you in the ass when you want to improve upon your code. In all honesty it's made me a better programmer because I'm now always thinking ahead, and thinking about how I can make it easier for myself and others in the future.

The first project was a basic ore mining simulator that was all jammed into one "monster" class, resulting in pretty much every software design principle that you can think of being murdered with an axe. It had private inner classes, it had global vars being touched by everyone, it had high dependencies on everything around it, cohesion was awful and talk about high coupling. You can find the project here.

The second project was much the same, with again using JGameGrid (gah) and this time horrible design for the card game LuckyThirdteen (they made a spelling mistake and we had to keep it so their testing would still work lol). It had basically the same issues as the first project, but required more complexity due to the bots we had to add and required basically a complete rewrite to get all the new rules and features in. You can find the project here.