Oct 13th, 2014

Assertion failed: calling set on destroyed object

Today everyone was freaking out about an EmberJS component generating a huge chain of errors when navigating from one resource to the other and resizing the window; basically every subsequent call to didInsertElement seemed to instantiate parallel worlds of runloop trying to interact with destroyed objects forever.  It wasn’t the case, and the solution was as easy as keeping in mind that every $(window).on in a single page application needs to be accompanied by a $(window).off !

Oct 10th, 2014

I can post this and nobody will even notice! :)

You think water moves fast? You should see ice. It moves like it has a mind. Like it knows it killed the world once and got a taste for murder. After the avalanche, it took us a week to climb out. Now, I don’t know exactly when we turned on each other, but I know that seven of us survived the slide… and only five made it out. Now we took an oath, that I’m breaking now. We said we’d say it was the snow that killed the other two, but it wasn’t. Nature is lethal but it doesn’t hold a candle to man.