wrhn

Recent submissions

Comment · 1 month ago
Interesting. How are you handling sheer number of replays without missing anything important?
Comment · 1 month ago
Not enough community around it. Shopify would have to pioneer a lot more than they would like to get it working for their use case.
Comment · 3 months ago
These benchmarks are done with incorrectly and missing a lot of baselines. The article seems very vibe coded too.
Comment · 3 months ago
Lol. Yeah, do you have a good example I can follow and learn from? That would probably help explain well.
Comment · 3 months ago
Yep yep that's why I didn't like it when I was originally using MS Clarity. It was just summarizing stuff that was obvious (and more importantly after the issues happen). RJ here is built mainly for a single focus of being really automated. Of course, if you want the classic product analytics like replay, crashes, api, heatmaps, that also exists in the RJ dashboard but that's more for human validation of the issues spotted.
Comment · 3 months ago
Wow Turing Scholars! you guys are like the navy seals of CS at UT lol. Yes I appreciate the insight and will actually hand write it (and copy some parts of this post, but it is a bit too goofy to just use the post straight up). One thing you mentioned, I've never heard of Readmes including a history of the project, because I thought Readmes were like a small intro doc with a bunch of hyper links only.

For example, I looked at the these two Readmes: https://github.com/rybbit-io/rybbit/blob/master/README.md <-- this one is lovely https://github.com/supabase/supabase/blob/master/README.md

Both include pictures, features, ect, but not really histories, unless I'm understanding your comment incorrectly.

Comment · 4 months ago
Keep it up bro! Tell your kid to share it with his friends and family to get feedback and support!
Comment · 4 months ago
Nothing Proton VPN can't solve

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton