I recently read a great article from Honeybadger that muses on what could happen to a production environment if a fat fingered developer did something like: Redis.current.flushdb. This scared me enough

A Living List What follows is a living list of heuristics I've come to internalize over the years as a developer. My goal is to periodically add to this list. Consider it a repository of programming wisdom.

Do you have skeletons in your git history? Maybe you want to re-write that history? I know I've been down that road, and since I've had to look up how to do this several times I thought it was high time

My recent (and only) RailsConf talk:

This is the last in a two-part post on creating a Ruby cli gem from scratch. Part one found here. Picking up from our last post, we want to start working on our user interface. In this case we want a cli

This is the first in a two-part post on creating a Ruby command-line gem from scratch. Part two found here. Let's write a command-line interface (cli) as a Ruby gem. We need the gem to do something slightly

If you are a programmer and have been hearing all of the fuss about THE BLOCKCHAIN but haven't yet looked into it, and were looking for a starting point, this is the post for you! Feel free to skip the

SQL can do a lot: data insertion, querying, updating and deleting, schema creation and modification, and data access control. I have to look up this stuff more often than I'd like to admit. How do I alter

> rails new app_name ...gives you all you need to get started developing an application, notably using SQLite as the default datastore. I've always worked with Postgresql (postgres) since I started

Ever try out a regular expression on rubular, stick it in your model: MEH_REGEX = /^(?=.*[a-zA-Z])(?=.*[0-9]).{8,}$/ ...start up your test suite and see this error? The provided regular expression is using

You've included rspec in your Gemfile, run bundle install and you want to initialize some examples to start testing. > rails g rspec:install The thing is you are sick of all the extras that come along

When using Rails to build an API you'll most likely be working with JSON or XML to pass around data. That is because most APIs today work exclusively with these MIME(Multi-purpose Internet Mail Extension)

You hear it all the time when reading about Ruby: everything is an object. Objects in Ruby communicate with other objects by passing "messages" back and forth to one another. Well, those messages

Ever needed to check really quick how many CPUs your *nix machine is running? Maybe you're logged into a remote server, or maybe you just forgot. In any case, I keep finding myself in a such situations