Good abstraction in Java lets us focus on the business problem, not implementation details. When we use List we think about users, not array resizing. That's the power of abstraction: reducing cognitive load so our brains can solve what matters. #Java #CleanCode

I've seen too many teams default to stateful JPA without considering alternatives. JDBC, JOOQ, Jakarta Data, and stateless JPA each solve different problems. The key is matching your persistence choice to your actual needs, not just picking the familiar option.

#Java #SoftwareArchitecture

"How productive are your developers?" or "How easy is it for your developers to do the right thing?"

I bet you've been part of teams that measure productivity with ticket counts, burndown charts, or lines of code, but real productivity in software is about feedback, flow, and focus.

Clean module dependencies = maintainable code. Strange dependencies between modules often signal API design issues. Keep dependencies minimal and meaningful to your architecture. ArchUnit helps enforce these rules automatically. #Java #CleanCode #Architecture

We are good at writing bad code quickly. We are bad at writing good code slowly, that is taking the necessary time to focus on quality.

Dependencies in Java projects are like garden weeds - they multiply quickly if not managed. In enterprise development, we need to prune regularly to prevent duplicate libraries, security risks, and version conflicts that can block Java upgrades. Keep your dependency garden tended! #Java

20 years of software development taught me three very important lessons;

1️⃣ Unit and integration tests are the best way to prevent bugs.
2️⃣ In the long run, the simpler the design, the better it adapts to new requirements.
3️⃣ Debugging framework code teaches you a lot about coding best practices.