Oh thank god. I had the displeasure of meeting with him once, and it was so bad that when we hung up I had our team to start planning a migration off of Heroku.

Oh thank god. I had the displeasure of meeting with him once, and it was so bad that when we hung up I had our team to start planning a migration off of Heroku. The crux of the issue was that he told me that he philosophically didn’t believe Heroku should put up status notifications about downtime or performance issues until AFTER they fully understood the problem and had a fix. (My theory was actually that no engineers worked there and they didn’t have on-call rotation anymore)