Over the last few months, we’ve been seeing increasing number of requests about our SLA (Service Level Agreement) – do we have one? if not then why not? and so on.

We’ve been reasonably resistant to publishing an SLA until now, not because of doubts over our infrastructure or ability to deliver, but because of the minimal value we felt it would add for customers in the event of actual downtime. We’re a pragmatic bunch at Brightbox and like to avoid adding things just for the sake of it or “because everyone else does” :)

Now that we’ve looked at some of the core architecture, I’d like to shift my focus first to upgrading an application. Originally I had planned on writing about upgrading plugins first, but apparently that API isn’t quite stable. So, I figured rather than write a blog post that will be deprecated in 2 weeks, I’d rather write one that will be deprecated in 3-6 months instead.

Over the last couple of months, a new billing and subscription company - Chargify - have been popping up around the Web 2.0, SaaS, and Rails scenes. Notably, Chargify's CEO is Lance Walley, co-founder of Rails hosting company Engine Yard.

Ever since 2005, I’ve been attending and speaking at Ruby events. But the one thing I always wanted to do was run training sessions. Thankfully, over the last couple years, LSRC has allowed me to get my feet wet — but only as one of many excellent choices in a lineup of Ruby’s best and brightest. Until last weekend, I had never participated in professional training event that stood on its own.