Nice summary of my favorite principle.
Quite stongly-expressed article about designing code to cope with changing requirements. Don’t read without also studying Uncle Bob’s answer at http://blog.8thlight.com/uncle-bob/2015/10/30/futureproof.html
What is JAR Hell?
Nice summay but no new solutions (of course)
Database versioning best practices
Should be common sense, but anyhow…
Loosely Coupled Tests
Good explanation why mocking isn’t the answer to everything in testing with dependencies (Classical article on this topic is http://martinfowler.com/articles/mocksArentStubs.html).