Thanks for sharing your latest article; it’s good to see another submission from you after we enjoyed the last one so much. Hopefully more people will adopt this interesting ‘Five Things’ format in the near future. I’m also glad to see your team has entered the exciting world of book publishing, and I look forward with great anticipation to the submission to Lobsters of Guide to Automated Root Cause Analysis—can’t wait to find out what it recommends! However, you don’t actually mention .Net nor Java, so it would be a good idea to re-tag the article accordingly. Incidentally, regarding ‘Powered by OverOps’ at the top of the blog wrapper: you should write an article on how your team integrated OverOps into the blog engine, because that sounds quite fascinating.
The title is weirdly misleading. Like, this post simply states that developers spend more than 20% of their work week doing production debugging (what?), says that this is all wasted time, and lists out five steps of production debugging as the ‘five ways’. Then it advertises an ‘automated bug fixer’ product.
I think the implication is that their tool will make developers so much more productive at bughunting that debugging will be reduced to 5% of their time, but the article doesn’t explicitly connect the two figures.
I have already messaged @talisoroker to recommend the rule of thumb that half of one’s submissions be of other people’s work, and tried to Tom Sawyer @talklittle into writing some monitoring for this rule of thumb.
Thanks for sharing your latest article; it’s good to see another submission from you after we enjoyed the last one so much. Hopefully more people will adopt this interesting ‘Five Things’ format in the near future. I’m also glad to see your team has entered the exciting world of book publishing, and I look forward with great anticipation to the submission to Lobsters of Guide to Automated Root Cause Analysis—can’t wait to find out what it recommends! However, you don’t actually mention .Net nor Java, so it would be a good idea to re-tag the article accordingly. Incidentally, regarding ‘Powered by OverOps’ at the top of the blog wrapper: you should write an article on how your team integrated OverOps into the blog engine, because that sounds quite fascinating.
The title is weirdly misleading. Like, this post simply states that developers spend more than 20% of their work week doing production debugging (what?), says that this is all wasted time, and lists out five steps of production debugging as the ‘five ways’. Then it advertises an ‘automated bug fixer’ product.
I think the implication is that their tool will make developers so much more productive at bughunting that debugging will be reduced to 5% of their time, but the article doesn’t explicitly connect the two figures.
I have already messaged @talisoroker to recommend the rule of thumb that half of one’s submissions be of other people’s work, and tried to Tom Sawyer @talklittle into writing some monitoring for this rule of thumb.