In addition to the actual topic of the post (issues with a Heroku beta feature), I find this post pretty interesting for a number of reasons.
It seems that for blog posts are the preferred method of reporting deeper issues. I guess it's a way of publicizing the work of tracking down the problem and earning developer cred. (Do people have blog posts for pull requests too?)
Also, it's impressive to see how fast Heroku's Ryan Daigle replied. Hopefully this issue will be short-lived as the runtime metrics are pretty handy.
Yeah, I actually sent the post to Heroku and NewRelic so they were the first to see it. I think someone from NewRelic submitted it to HN (just a guess).
Curious: What other method would you suggest for reporting deeper issues? I can't think of anything else that would allow for free-form writing like blogs.
Comments
In addition to the actual topic of the post (issues with a Heroku beta feature), I find this post pretty interesting for a number of reasons. It seems that for blog posts are the preferred method of reporting deeper issues. I guess it's a way of publicizing the work of tracking down the problem and earning developer cred. (Do people have blog posts for pull requests too?) Also, it's impressive to see how fast Heroku's Ryan Daigle replied. Hopefully this issue will be short-lived as the runtime metrics are pretty handy.
Yeah, I actually sent the post to Heroku and NewRelic so they were the first to see it. I think someone from NewRelic submitted it to HN (just a guess).
Curious: What other method would you suggest for reporting deeper issues? I can't think of anything else that would allow for free-form writing like blogs.