> Especially the one line about the date of the report, that's just pedantic.
What they claim to have known and when is very relevant to how much you can trust them! Here's the timeline from my perspective:
1) In 2011 Tim Watson points out the problem: http://tiwatson.com/blog/2011-2-17-heroku-no-longer-using-a-...
2) Heroku responds but does nothing (https://groups.google.com/forum/?fromgroups=#!msg/heroku/8eO...)
3) On 2/8/2013 I send Heroku full details about the problem including simulations, etc
4) On 2/11/2013 Heroku responds and says the best path forward is for me to optimize Rap Genius and that Adam's done talking about it with me.
5) The Heroku's Ugly Secret article goes up on 2/13/2013
6) Heroku releases BIG apology on 2/14/2013 saying they only learned about the problem on day ago.
Heroku knew about the problem at the LATEST on 2/11, and before we made a big public stink, their response was to say "just make Rap Genius faster"
> Especially the one line about the date of the report, that's just pedantic.
What they claim to have known and when is very relevant to how much you can trust them! Here's the timeline from my perspective:
1) In 2011 Tim Watson points out the problem: http://tiwatson.com/blog/2011-2-17-heroku-no-longer-using-a-...
2) Heroku responds but does nothing (https://groups.google.com/forum/?fromgroups=#!msg/heroku/8eO...)
3) On 2/8/2013 I send Heroku full details about the problem including simulations, etc
4) On 2/11/2013 Heroku responds and says the best path forward is for me to optimize Rap Genius and that Adam's done talking about it with me.
5) The Heroku's Ugly Secret article goes up on 2/13/2013
6) Heroku releases BIG apology on 2/14/2013 saying they only learned about the problem on day ago.
Heroku knew about the problem at the LATEST on 2/11, and before we made a big public stink, their response was to say "just make Rap Genius faster"