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
I have a long-standing love/hate relationship with Jira. The product has an impressive level of power & flexibility that it can often be intimidating to users. Jira’s automation features are a great step toward changing this. The no-code implementation is really well done, striking a great balance of high-power, low-complexity.
Today, I blindly ran a script designed for ubuntu. When it failed, I came across the following line On a Linux distro, /proc/cpuinfo provides information on the processor your computer is running. This file is not present in OS X. Instead we’ll need to use sysctl to get the information.
Sonarqube is a popular solution for static analysis of code for quality and security issues. It supports 27 different languages, and the list keeps growing. The range of coverage is one of Sonarqube’s great strengths, but unfortunately, it puts the product in a “jack of all trades, master of none”