Hi everybody – we’ve been having this conversation for 20 years already, but I stumbled across a bit of code today, and I just have to say it again: Please don’t use the database in your unit test unless there is a good reason.
Full Source Code If you aren’t using Feature Flags in your software project yet, you should start right away. It’s the key to unlocking Continuous Deployment in production, as well your best friend in managing release risks. I won’t belabor the point here, but checkout the excellent guides from Atlassian
As readers may be aware, I’m really into the Play! framework. It combines the convention-over-configuration mindset of ROR with the Java/Scala libraries and skills that I’ve worked on for years. That said, Play! isn’t idiot-proof. Here is a list of 5 mistakes to avoid in your Play! projects. 1) Using
After spending a couple months developing LiveOn using the Play! Framework, I’ve grown increasingly intolerant of other Java frameworks. While I’d used YAML before in Rails & Python, Java frameworks usually ignore YAML in favor of XML for configuration. The creators of Play! realized that XML sucked, and implemented their