Viewing profile — gary_chambers

Hi HN! I've been working on this project for a while and I'd love to get your feedback. Repro is a browser extension for creating replayable bug reports. It uses session recording …

I agree that WS replay could be very powerful, but I'm not sure it's straightforward. Once you get out of the realm of request/response and you are dealing with subscriptions, conn…

Both rrweb and OpenReplay are very solid projects. I've spent the last year or so building a session recording tool, and I've scrutinised their code quite heavily. Conceptually, se…

Congrats on the launch! I've been looking forward to this launch for a while; I've spent a lot of time experimenting with session recording and how it can work for regression testi…

Some screenshots of Repro in action... The Repro toolbar: https://repro.dev/screenshots/repro-toolbar-closed.png Element picker: https://repro.dev/screenshots/repro-picker.png Savi…

That's a very fair point - thank you! I don't have a demo video to hand (I will make one soon!), but this is an example of a saved recording: https://share.repro.dev/ZESo4eZ7ZUf279…

Hi HN! I'm Gary, the creator of Repro ( https://repro.dev ), the time-travel web inspector for replayable, shareable bug reports. It is available as a free Chrome extension today (…

I've been having a debate about whether code should be checked out and run locally (or on a staging environment) as part of code review. Personally, I find it easier to review a ch…

I see you played the same meta-game that I did. It took me a few tries, but I ended up with: WHISK, FRONT, GLADE, BUMPY. Probably not in the spirit of the game, but once you have 2…

I lead a small team building web apps, but we currently have very little structure around code review. I want to get the right balance of process and tooling, but it would be inter…