Managing dependencies is important. JarAnalyzer, an open source static analysis tool for .jar files, can help. Think of it as JDepend for jars.

Wow. A lot of debate on quality versus velocity. I'm wondering if we're all on the same page with what we mean by quality.

Can you divide your logical layers into separate deployable units without changing a single line of code? You should be able to!

Layering is a powerful architectural pattern. It can be more powerful when using your deployable units as layer boundaries.

I'm curious, how many developers spend time consciously designing and managing relationships between physical entities?

Sometimes code duplication is warranted, even good.

Sometimes, we're required to do things because "that's the way things are done around here." But interpreting corporate standards and applying subtle adaptations can yield substantial rewards.