Some ways to reduce memory usage as you gather records out of your database into Rubyland.
Changing Ruby’s garbage collection parameters is the least invasive way to optimize your app’s memory usage.
Part one of a four-part series which will show you how to optimize a memory-heavy Rails API action.
Spring, as described in its README, is a Rails application preloaded. “It speeds up development by keeping your application running in the background so you don’t need to boot it every time you run a test, rake task or migration.” I want to focus on the first assertion in that description…
Flash messages were one of those little features that amazed me when I was first introduced to Rails. Developers often use Rails’ flash to display messages to their users, but messages aren’t the only reason to use flash.
Healthcare.gov leaks patient data to 3rd parties. Does your Healthcare startup do the same?
Tools like Chef and Puppet make configuring servers repeatable and reliable. However, handling the private data, like server passwords and API access keys is still a difficult problem. Today we take a look at one solution available to the Chef community: Chef Vault.
Realm is a good alternative to CoreData for your iOS apps. Setting up properties to be stored in the database is as simple as defining them in a model. But what about those properties that you don’t want persisted?