Passive Agressive Rails Developer @passiveagressiverailsdeveloper - Tumblr Blog

You had a problem with your tests being too damn long. You DRY'd them up by using helpers. Now you have two problems.

•18+ Adults Only

Watch Anya Live on Cam

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.

✓ Live Streaming✓ Interactive Chat✓ Private Shows✓ HD Quality✓ Free Actions

Free to watch • No registration required • HD streaming

state_machine

Well, it has come to this. You wrote this beautiful complex thing of a state_machine. You have 14 states and handle a ton of state changes in various combinations. You also wrote zero docs. Thank you.

#rails #state_machine #documentation

You have added to the Gemfile

> You are trying to install in deployment mode after changing your Gemfile. So you haven't updated Gemfile.lock after that reshuffling of gems you did. Consequently, **bundle install --deployment** failed across all servers, prevented servers from restarting, and almost brought the site down. It sure would be very nice if you could run **bundle install** on your side and commit the changes. Which is just what bundler suggests. If you don't want to, it's cool too. Not like it's a big deal or anything.

#rails #bundler #Gemfile

open(2)

**open()** working with HTTP right away is a lucky coincidence. If you really need that open() to work with HTTP, make sure to require 'open-uri'.

#http #open-uri #ruby

Trending Blogs

Last Seen Blogs

Passive Agressive Rails Developer