@searls The lack of requires in Rails apps is a huge part of this problem. It encourages us to ignore our dependencies.
@searls Yep. I could tell a story about a gem, a Rails app, and a 2nd gem that corrupted data in the 1st one. It was only 3 days of my life.
@searls I've fixed at least two critical bugs of this ilk in the past few months. Both took hours/days to find.
I guarantee you that the line I just deleted to fix react-rails users will break users of older versions of sprockets, or some other thing
Rubyists rarely realize how obscenely global everything is, especially in Rails. Interaction between gems is very common, impossible to test
"Create opportunities for other people to grow." -@voodootikigod in his inspiring @JSConf Last Call closing toast
"Turned out that I'd created a service for testing stolen credit cards. Didn't realize. Because the cost [of JSBin] was so low." #jsconf
TIL @jsconf is the place you have job interviews in the hot tub, but it's not weird, there are 20 more people (mostly singing)