After 13 years in backend engineering, I’ve noticed something interesting. Many developers learn frameworks. But the real breakthroughs in a career come when you start understanding what happens underneath the framework. For example in Java: You may use a "HashMap" every day. But do you know: • How collisions are handled internally? • When buckets convert to red-black trees? Or when using Spring: • How does "@Transactional" actually work? • Why does it fail on private methods? After years of debugging real production systems, one thing becomes clear: Strong fundamentals beat framework knowledge every single time. So I’m starting to share insights from my journey working with: Java | JVM Internals | Databases | Distributed Systems | Cloud (GCP) If you're a developer who enjoys understanding how systems actually work under the hood, feel free to connect. Let me start with a question: What Java concept took you the longest to truly understand? #Java #BackendEngineering #SystemDesign #JVM #SoftwareArchitecture #Mentorship
For me, it was truly understanding how @transactional works internally in spring.. Initially my understanding was that spring would manage all this automatically..But later I realised that it works through AOP proxies because of this it fails in the self invocation or private methods.
I guess the fact that Java is passby value and not pass by reference
Threads and Streams
I still feel like we don't give "static" for enough credit. It basically removes the "object" from object oriented programming 😉