San Francisco, CA
Joined February 2009
- Tweets684
- Following406
- Followers440
- Likes256
Ashley Stirrup retweeted
When you deliver flowers and gifts across 9 countries, not everyone behaves the same way. Why should your testing assume the same?
Find out how the Floward data science team helped drive double-digit revenue growth through experimentation with GrowthBook.
Case study ↓
growthbook.io/customers/flow…
I'm excited about 4.2! Having product analytics alongside experimentation is pretty powerful. I can't wait to see what our customers do with them both.
Shout out to @ChatGPTapp. I was about to give up on this freezer and ChatGPT gave me a simple list of things to check first. I was skeptical, but ChatGPT insisted I could do it. Turns out it was a $50 sensor!
Ashley Stirrup retweeted
Score Update
#1 UCLA 2, #5 Stanford 0
1. Sorra/Rockwell- 18-21
2. Bell/Wilson- 12-21, 16-21 ❌
3. Jackson/Belardi- 10-7
4. Stowell/Hoffman- 26-28, 17-21 ❌
5. Sharp/Gusarova- 21-18, 5-3
6 (exh.) Gubbins/Vincent- 15-21, 14-21 ❌
#GoStanford
Interesting article. A really powerful example of how @Dropbox was able to reduce incidents 10X by being data driven and building automations. This is the kind of thing that inspired @shoreline_io fiberplane.com/blog/on-call-… @tambryantbutow
From @tameemhourani at @Datadog DASH conference. "If you're not automating away toil so you can innovate, then you're just waiting to get fired"
Listening to @TigerGraphDB talk about how graph databases make machine learning smarter. United Health Group is using them to predict patient needs. Come join the webinar now bit.ly/3Rl7RG6
#DevOps #SRE
@TigerGraphDB is using @shoreline_io to streamline many aspects of ops. One automation is saving them 50 hours a month and they've really simplified cross-node debugging activities
Improving on-call processes is an obvious way to reduce on-call load. It's clearly the #1 area of investment for attendees. If you can give people tools to standardize how they work incidents, it simplifies the actual work which makes process optimization 10X easier.
This data on escalations is shocking and obvious at the same time. The average time to resolve incidents without escalations is 3.7 hours. The average escalated incident takes 10.6 hours. Reducing escalations is a huge opportunity to reduce mean time to repair (MTTR).
It was pretty interesting to hear that @awscloud is already 3.6X more energy efficient than running on-prem. If you're still running on-prem, that alone is a good reason to make the move to the cloud.
Ashley Stirrup retweeted
Long term risk means climate risk and there are only a couple of companies really thinking about it.. watch tonight
Surprised that Cramer was so negative on @okta last and didn’t even mention that losses were $0.10 versus $0.30 expectations. I know they’ve got integration challenges, but I think the stock is on sale right now.
"It's an unforgiving time. We're back to the dynamic that defined January through mid-June," says @JimCramer. cnb.cx/3CSd5Wf
Glad to hear Jon Gruden is repentant about the emails he sent, but am shocked that he wants a shot at another coaching job already. In my mind he needs to do a lot for people of color, women and the LGBTQ+ community before he earns that right.
Not investing in cloud reliability is like not building a boat, except you KNOW the rain is coming. 47% said that a big challenge in cloud reliability is "Not enough time to focus on preventing incidents or automating fixes". What else are you missing? bit.ly/3q2cycw
Looking forward to this webinar. There are some really low hanging fruit out there for most companies to dramatically reduce their cost of on-call while also improving the customer experience. There aren't too many win-win situations out there like this.
📣You do not want to miss this one!! @devopsdotcom upcoming webinar where @awgupta & @astirrup will talk about the surprising data and insights uncovered from a survey of over 300 execs & engineers responsible for on-call - 9/7 @1pmET. bit.ly/3RmUKon #SRE #DevOps #OnCall
Interesting blog on adding a sequence of events analysis to a 5 whys post mortem to put focus on incident recovery. This is a key principal at @shoreline_io. Finding new ways to get the right info to the right people quickly can have a huge impact on MTTR
How important is the incident management process in your company? Do RCAs leave you feeling a bit wanting?
We faced such concerns and discovered an improvement on the 5 Why RCA format that made a huge difference. @varunachar discusses this below
engineering.razorpay.com/how…
