Week 6: Scientific method 🔬

We talk about the scientific method as an analogy to successful debugging.
profile photo
Jason Laster
Successful debugging is remarkably similar to the scientific method. When we're succeeding, we're running experiments and refining our hypotheses. When we're failing, we're going down rabbit holes and running in circles.
To debug successfully, we formulate hypotheses, run experiments and continuously refine our hypothesis. When we don't stick to the process, we go down rabbit holes that gets us nowhere closer to an answer.
When we think about Replay, we want to make it easy to test your assumptions and understand why things happen or why they don't!
This is why over the past week, we've revisited some of the core mechanics and tried to make the connection between timeline markers and console message clearer.
Here's a short video. We'd love to hear what you think!
Image without caption


  • We're shipping the V2 recorder today!
  • We're actively hiring for a founding designer and systems engineers. (doc)
  • We have lots of good first issues around improving the new user experience! Say hi in Slack if you'd like to get involved. 👋
Related posts
post image
We’re thrilled to share our progress on Performance Analysis: the first practical way to catch performance regressions before they ship to prod.
post image
We’re thrilled to share that we’ve officially migrated from Firefox to Chrome. It’s been a long time coming, but Chrome is better in every way.
post image
This week we’re excited to share Elements Panel V3, which brings one second element loads.
Powered by Notaku