Original Summary

Last month a customer got stuck on checkout. They didn’t email. They didn’t complain. They just left. I found out 4 days later, from a log line. I spent hours going through logs and the database. I never found the cause. So now I’m just waiting for it to happen again, and hoping I catch it next time. That’s why I’m building Bugwalk . It traces a customer’s failure to the exact line of code and opens the fix as a pull request. You review the diff, and nothing merges until you approve it. But I want to know how you handle this today: How do you find out a user hit a bug: Sentry, session replays, support tickets, or luck? How long from “a user got stuck” to “it’s fixed”? Has anyone else had a bug you couldn’t reproduce, and what did you do? Would you let an AI open PRs on your repo, or is that a hard no? If an existing tool already does this well, tell me. I’d rather know now.   submitted by   /u/vasanth7781 [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/10/9 22:19:12