4 ms·
I appreciate the honesty, but I don't see any "this is how we'll fix it", rather, just "we promise to document it and make it clear to anyone who wants to measu
by Tekker 14y ago
I appreciate the honesty, but I don't see any "this is how we'll fix it", rather, just "we promise to document it and make it clear to anyone who wants to measure it".
Effectively, they have a fundamental architectural problem, and don't know how to work past it.
- timv 14y agoThey also have a fundamental cultural problem, and don't appear to have recognised it. In short, they went for ~2 years with documentation that advertised features that the implementation didn't have, while receiving a string of support issues that they wouldn't acknowledge as their problem. Yet, the blog posts show no indication that they are interested in working out why they offered such terrible service to their customers and how they can fix the company culture to take this issues seriously in the future. There's a chance they'll come up with an architectural solution for their routing problem. But unless they do some serious introspection and work out why they (as a team) stuffed up so badly, then there's no chance that they'll fix that problem. And if they don't fix that, then why would anyone have confidence that this sort of issue isn't going to be commonplace? (Disclaimer: Not a Heroku customer)