[tluyben2]

I hope someone has better advice for you, but in my experience (30+ years programming, 25+ professionally programming) I could not imagine a book that could teach that. I need to have a ‘seen it all before’ feeling and that is usually the case. There is also just really really bad code (100k+ old php, millions of lines of ‘optimized for performance’ Java) which I thrive on not because I saw the structure before, but I saw a lot of code rot and I am efficient in managing/altering it; it is a common reason for people to hire me to consult; they inherited a codebase that makes the team burn out and ask me to come, analyse and explain to the team what to fix to make it less crap.

What did you do before this? Because Java projects are usually overarchitected but so are many OO projects in other languages. Many times it started with a clean design pattern (which was already often a bad idea but it fit) and then got a million things bolted on over time.

Again; hope someone has better advice but it sounds like you got some bad code there and that might or might not be repearable. 100k is not so much, especially in Java, but way too much for a rewrite so personally I would disappear for a week with the codebase to see what can be done and then suggest doing it or, if it turns out really bad and there is no funding/understanding for fixing it, look for another job.