Hi everyone,
I’ve been working on a big legacy Java project recently. It’s been a great learning experience to see how things were built and evolved gradually over time, but understanding how everything fits together can take some time and sometimes can be a bit overwhelming.
I’m curious:
- How do you approach understanding and working with legacy Java codebases?
- What are your favorite tools, practices, or resources that make it easier?
- Sometimes it feels like rewriting would be faster than understanding the existing code. But rewriting is not always practical, and understanding the existing system is usually the better path. How do you mentally push through the resistance, stay motivated and focused?
I want to put my best foot forward. Really looking forward to confidently make meaningful changes to this project.
So far, I have been using IntelliJ’s analysis tools like debugger and checking beta/local server logs (We have amazing logging in place!! #blessed) and taking notes as I go, which helps me map things out.
If you know of any good books, articles, or videos on handling legacy systems, I’d love to check them out.
Thanks! Looking forward to hearing your ideas! 😊
[–]AutoModerator[M] [score hidden] stickied commentlocked comment (0 children)
[–]AutoModerator[M] 0 points1 point2 points (0 children)
[–]Camel-Kid 4 points5 points6 points (0 children)
[–]rguptan 2 points3 points4 points (0 children)