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”
If you’ve ever built a sizeable Rails app before, you know that efficient cache use can really supercharge your application. The storEDGE platform has always tried to offer the best performance to our users by keeping our memcached processes on the same instances as our application servers. While this is
The Engineering team at Red Nova Labs has been working to simplify our development process. Recently, we’ve been experimenting with Vagrant as a good tool to do this. However, we’ve had the same problem that many developers have with Vagrant – performance. The app in question is very large, and
Today I had the pleasure of presenting a session at the Kansas City Developer Conference. Renovate Your Retrospective – Adam England – KCDC 2015 from Adam England
Today, I came across a puzzling issue with Rails 4.1, ActiveRecord, and Postgres when trying to select random records from a database table. To demonstrate, let’s use a simple social network API example. Clients will POST a list of user, and I’ll “match” them to someone in my database. Easy
While looking at performance optimizations for a rails project, I noticed these lines in my debug console: ActsAsTaggableOn::Tag Load (0.5ms) SELECT “tags”.* FROM “tags” INNER JOIN “taggings” ON “tags”.”id” = “taggings”.”tag_id” WHERE “taggings”.”taggable_id” = $1 AND “taggings”.”taggable_type” = $2 AND (taggings.context = (‘tags’)) [[“taggable_id”, 103], [“taggable_type”, “Prediction”]] This makes sense,