angryonrails's profile picture. Web development that hurts less than Java.

Angry on Rails

@angryonrails

Web development that hurts less than Java.

Uptime is so easy; there's no excuse for downtime. DDoS attack, whaaat?


A living legend lives no more. RIP @jimweirich


If terminology and dealing with all those deprecation warnings is so damn important, then shouldn't it be rspec-doubles?


All of Rails' uptime problems can be solved by hiring from outside the bottom 99.999% of ops teams.


Wah, supporting Ruby 1.8 is soooo hard… Shut up.


There's going to be some money in producing materials that guide people through upgrading Rails 2.3 to 4.0.


GitHub, where you can trust us to remember all your code history, but not your authentication.


"David is a heavy hitting Rubyist who would rather be commenting on issues instead of pushing code." osrc.dfm.io/dhh


This slide is the punchline to the bad joke we've been telling ourselves. bit.ly/10VzJXr


Anyone who was holding their breath for Passenger 4 has long since died of asphyxiation.


Angry on Rails รีโพสต์แล้ว

Mechanize relies on Net::HTTP::Persistent. WebMock is known to break N::H::P. FakeWeb works, but FakeWeb is deprecated in VCR. Argh.


Postgresql went so far in replicating MongoDB features that they accidentally included the loses-all-your-data feature.


I guess @engineyard ran out of other people's conferences to sponsor.


Anyone know if Groupon or LivingSocial are still hiring?


GitHub errors are the new Twitter fail whale.


Engine Yard over the years: environment centric, then application centric, now clusterfuck centric.


Use handy Rails feature. Feature moved to gem. Find gem git repo. Follow link to official non-Rails repo. 404. Fuck Rails Life. #frl


Angry on Rails รีโพสต์แล้ว

learning about the wonders of Ruby GC, 200ms out of 350ms total page time? Sure, why not.


Loading...

Something went wrong.


Something went wrong.