Live data from Hacker News

Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years

news.ycombinator.com

91–100 of 240 posts

Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years

#91

> but the important information the engineer needed was what was actually right outside the boundary of the screenshot I took Ah ah. At one gig we had trained the users to always send a screenshot of the entire screen. People reviewing the tickets would dump them if the screenshot was cropped and the user warned: "No full screenshot, no ticket" . Why? The most important info was the time at which the error happened (…

This seems like it would only work if the applications in question didn't contain any PII - as soon as you get into applications or flows within an application that contain some form of PII, either displayed or the user entering it, having them send a screenshot of the entire screen is asking for the user to accidentally leak their PII to the person reviewing the ticket.

Where I work (in which the above would be a problem), we make sure to log enough information that given a relative timeframe of when the user had the issue, we can usually narrow down to where the issue was using context and some querying of the logs (splunk is incredibly helpful for this)

Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years

#93
post #58

Earlier quoted context omitted.

I would have easily paid for any of their best in class DNS, DDoS protection or CDN, but I get all of those free unmetered. Generally when this happens, I get suspicious that they are just trying to kill the competition and then increase price, but cloudflare has been free for almost like forever.

It's no secret that those products are free* with a big asterisk, if you hit some unspecified combination of total bandwidth usage, attracting DDoSes, serving the wrong types of files or moving too much data in regions where bandwidth is expensive then you get an email from sales asking you to pay up or leave. Even if you're on a paid plan, beyond a certain (also unspecified) amount of usage they will ask you to pay…

Do you have any source? I was initially suspicious of the same but found few content in reddit/other forums where multiple users said they have free plan and get millions of requests per day[1]. And I couldn't find a consistent reason for all the sites that cloudflare banned.

[1]: https://www.reddit.com/r/programming/comments/lfa1il/why_you...

Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years

#94

> but the important information the engineer needed was what was actually right outside the boundary of the screenshot I took Ah ah. At one gig we had trained the users to always send a screenshot of the entire screen. People reviewing the tickets would dump them if the screenshot was cropped and the user warned: "No full screenshot, no ticket" . Why? The most important info was the time at which the error happened (…

Indeed, that's a great rule. Another one is "What URL was the browser on?" which is rarely ever in cropped screenshots but is visible in full screenshot

Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years

#95

Also ex-Cloudflare, have been following Jam for awhile, great product! Something I would love is a way for customers to use this without having to install a Chrome extension. It would make debugging customer issues much faster - for example, if clicking 'Report a bug' on a website automatically triggered the recording flow and asked the user to reproduce it.

Stay tuned! We’re building this out soon. :)

Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years

#96

Also ex-Cloudflare, have been following Jam for awhile, great product! Something I would love is a way for customers to use this without having to install a Chrome extension. It would make debugging customer issues much faster - for example, if clicking 'Report a bug' on a website automatically triggered the recording flow and asked the user to reproduce it.

Hello! Would love to learn more! Can you send me a note at i@jam.dev?

Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years

#97
> It’s actually really hard as a non-engineer to file useful bug tickets for engineers... So the engineer would be frustrated, I would be frustrated

While I have been in this scenario before, saying something along the lines of, "If I don't get 100% bug reports, I can't do 100% bug fixes," 9 years of experience and maturity later: no, I wouldn't use this. It wouldn't engender me more respect, power or efficacy in the organization if I "just" "educated" PMs on how to file bugs, or if I "just" used some tool for them.

I should have just not asked non-engineers to ticket bugs or do QA. If that is happening, you are already failing in terms of leadership and organization. Most products fail, so that's not saying much, and they rarely fail due to bugs, which is also not saying much. That said, the best technical solution is clearly comprehensive tracing, and the best cultural solution is that engineers responsible for an end user experience must manually QA all paths.

Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years

#98

> It’s actually really hard as a non-engineer to file useful bug tickets for engineers... So the engineer would be frustrated, I would be frustrated While I have been in this scenario before, saying something along the lines of, "If I don't get 100% bug reports, I can't do 100% bug fixes," 9 years of experience and maturity later: no, I wouldn't use this. It wouldn't engender me more respect, power or efficacy in the…

That's all well and good, but even a halfway engaged PM is going to play with the product while it's in development, and they will tell you about what they discover along the way. It may not strictly be their job but they're going to do it. If a tool exists to help them capture more information that makes their inevitable reports more useful, is that a bad thing?

Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years

#100

> but the important information the engineer needed was what was actually right outside the boundary of the screenshot I took Ah ah. At one gig we had trained the users to always send a screenshot of the entire screen. People reviewing the tickets would dump them if the screenshot was cropped and the user warned: "No full screenshot, no ticket" . Why? The most important info was the time at which the error happened (…

> Why? The most important info was the time at which the error happened (which, for users who were on Windows, was in the bottom right of the screen).

Except it isn't in UTC and it doesn't show an offset.

Even if you stored the user's timezone, that doesn't mean that's where they were working from.

Post reply on HN