{"id":186,"date":"2016-04-01T00:01:46","date_gmt":"2016-04-01T08:01:46","guid":{"rendered":"http:\/\/andrewwippler.com\/?p=186"},"modified":"2016-04-03T05:09:55","modified_gmt":"2016-04-03T13:09:55","slug":"blame-as-a-service-blaas","status":"publish","type":"post","link":"https:\/\/andrewwippler.com\/2016\/04\/01\/blame-as-a-service-blaas\/","title":{"rendered":"Blame as a service (BlaaS)"},"content":{"rendered":"

Today I am pleased to announce a new offering – Blame as a Service (BlaaS).<\/p>\n

With the ever increase of SaaS offerings and cloud providers with high resiliency and low downtime, there will be the inevitable glitch or hiccup whenever a CEO views your team’s area of responsibility. With the recent passing of Murphy’s Law in IEEE this has become more frequent in day-to-day operations.<\/p>\n

BlaaS helps you by receiving the blame for your incompetence by providing you with simple, easy-to-use templates that you can share with your CEO. These templates shift the blame from your SaaS choosing and put it on your BlaaS application making you the hero and us the bad guy.<\/p>\n

BlaaS has already saved several Developers from embarrassment and System Administrators from potential job loss and it can help you too!
\n<\/p>\n

BlaaS saved my job after the datacenter burned down. I just pulled out one of BlaaS’ pre-made templates, edited a few words and sent it off to my boss!<\/p>\n