Friday, I had a morning coffee discussion with Somnath Musib, the author of Spring Boot in Practice by Manning Publications. We discussed the present and future of Spring Boot and debated over hot topics such as native compilation.
Not sure where I could ask this question so will try here. What are your tips for understanding a large code based when joining a new project team? ie. what static analysis tools would you run over the code to get a feel for it? When you have a large code base what steps do you take to better understand the application logic? At the moment I'm relying on the debugger at the moment.
Hey. Excellent questions. I use multiple techniques such as profiling and debugging. Of course, documentation were possible. I'd recommend my Troubleshooting Java where I present such topics. You might find the book interesting. :)
Hi, @Laur Spilca - I have a question about serialization - at work in our project all hibernate entities are implementing Serializable, but everywhere I read or watch a tutorial it says to avoid serialization. What am I getting wrong ? :D
There is no need for a Hibernate entity to be serializable. I think I read this here and there but it's a myth. I'm not sure where does this myth come from, maybe from the old EJB remote beans...
