21–30 of 151 posts
> I started as Heroku GM a few weeks ago with intense enthusiasm to be a part of such a storied team. Wow talk about terrible timing.
Fail it's because I am new; Succeed then it's my superior capability; plus, the learning rate during crisis is at least 10 times higher than the peaceful time, let alone the nerves and mental fortitude where peaceful time would never train one for.
Heroku has always been the opposite of transparent. I still don't forget how they handled the Intelligent Routing fiasco from back in the day.
Maybe that’ll change, there’s a new Sheriff in town as the saying goes? Bob was previously General Manager of AWS Elastic Kubernetes (EKS) which seemed to have a good reputation and to engage with its customers pretty well.
As a former herokai, communication was always the #1 point of discussion internally. This idea that they "can" do better is a half truth. They DID do better. I leave it as an exercise to the reader to determine what the limiting resource was here. By the way, how many senior devs and cofounders are left at Heroku Bob? Why doesn't it show up at dreamforce anymore?
Heroku never seemed to want to integrate, but instead be the "cool kids", those who just do not have to worry about the enterprisy stuff such as automated backups, DR, high availability, enabling Java, etc. Everything they did was great, everything "Salesforce" sucked, yet they never made any money before the acquisition. The acquisition was a waste of money in first place (IMHO).
The founders did not even try and so they left.
As a former herokai, communication was always the #1 point of discussion internally. This idea that they "can" do better is a half truth. They DID do better. I leave it as an exercise to the reader to determine what the limiting resource was here. By the way, how many senior devs and cofounders are left at Heroku Bob? Why doesn't it show up at dreamforce anymore?
Earlier quoted context omitted.
That isn’t a very charitable take. It’s been 24x7 for them, the acknowledgement is most welcome, in my opinion. I’m not sure waiting until Monday 9AM Pacific just to avoid these type of comments would be the right choice. The internet is 24x7 after all.
There doesn't seem to be anything different now than 6 hours ago. So posting it after 8pm EDT/5pm PDT Friday seems very intentional.
>The Heroku team and their colleagues have worked around the clock, including nights and weekends Can someone more familiar with an event like this tell me what they are working so hard on? I imagine securing the vulnerable service and resetting various credentials doesn't take that much work.
Earlier quoted context omitted.
There doesn't seem to be anything different now than 6 hours ago. So posting it after 8pm EDT/5pm PDT Friday seems very intentional.
With what intention? Honest question, I don't see a strategic advantage in posting this on a Friday. More of a disadvantage, actually, with less visibility.
The intention presumably is to be able to say they communicated this while (intentionally) limiting the amount of awareness that's spread about this.
Earlier quoted context omitted.
There doesn't seem to be anything different now than 6 hours ago. So posting it after 8pm EDT/5pm PDT Friday seems very intentional.
With what intention? Honest question, I don't see a strategic advantage in posting this on a Friday. More of a disadvantage, actually, with less visibility.
Curious why they would need to keep the GitHub integration down for a while longer. Are they afraid someone could still grab credentials?