Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

news.ycombinator.com

Post reply on HN
Print view View original

111–120 of 240 posts

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

#111

Post by a_t48 »

gbalduzzi wrote: post #53
mark242 wrote: post #50

The thing I love the most about Sentry/Bugsnag/Honeycomb/etc is that it is essentially automated observability. That is, I don't need to do a huge amount of integration to have, basically, a prioritized list of bugs along with severity and overall application health. I like the idea of the browser extension being able to offer these kinds of tools where you wouldn't need to install a heavy Javascript snippet -- but I…

I think they serve different purposes. Sentry/Bugsnag etc track code errors and exception . But sometimes for an user an error is not a code exception, but the software having the wrong behaviour. Some examples: > "The button brings me to the wrong page" > "I filled out the whole form but the submit button is not enabled" > "The video should autoplay but is stuck loading" Those things do not show up in Sentry logs.

Sentry has session replay that should catch all of these things - it doesn't look any higher friction than this tool.

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

#112

Post by wizzwizz4 »

ltbarcly3 wrote: post #31

I wouldn't use "cloudflare" as a selling point. People that have used cloudflare know how good the engineering work they do actually is.

Afaik, only Cloudflare's "checking if the site connection is secure" pages are rubbish. And while those are really rubbish (as a web user), the stuff they talk about on their devblogs seems quite solid. I don't think your generalisation is valid.

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

#113

Post by mattl »

toekneestuck wrote: post #49
alt227 wrote: post #38

I got really excited before I saw there was no firefox support. Thats a deal breaker for my team :( I really like this idea and if Firefox support was added I would purchase it in a heartbeat.

[I work at Jam] We do have an internal build for Firefox.. it's coming :)

How about Safari? This would be very useful as not every developer has Apple hardware

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

#114

Post by mattl »

freedomben wrote: post #94
TacticalCoder wrote: post #57

> 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

Don’t many browsers hide the full URL now?

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

#117

Post by gwbas1c »

> It prevents product managers (like I used to be) from being able to create vague and un-reproducible bug tickets (like I used to create).

> ... Like, sometimes I thought I included a screenshot, but the important information the engineer needed was what was actually right outside the boundary... Or I'd write that something "didn't work" but the engineer wasn't sure if I meant that it returned an error or if it was unresponsive...

> ...the way we capture and report bugs is just as manual and lossy as it was in the 1990’s

That's because bug reports are primarily communication among people, and the problems you describe are people problems, not technology problems.

Bug reports work when engineering can state what they need, and management is willing to support engineering's needs. Otherwise, bug reports devolve into the situation that you describe above.

In your case, this looks like a great tool for browser applications; but it only works if the people submitting the bug use the tool: I could easily envision a situation where a lousy manager ignores engineering's pleas to use Jam.

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

#119

Post by 0xbadcafebee »

Okay, so, stupid question; could you replace this with this screen recorder[1] and browsers' built-in web dev tools[2] ? The screen recorder lets you record and download a session (nothing is uploaded), and the dev tools lets you capture any errors the browser sees, the network connections & errors, the source, browser data/steps, yadda yadda.

The built-in web dev tools have a Recorder function to record what the browser is doing while also recording video[3]. You can export the recording in a number of formats. It can replay it, let you edit steps, even simulate a slow network. Seems like a product person could follow a simple guide to record and export a session, and send it to a dev?

[1] https://toolbox.googleapps.com/apps/screen_recorder/ [2] https://developer.chrome.com/docs/devtools/ [3] https://developer.chrome.com/docs/devtools/recorder

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

#120

Post by 0xbadcafebee »

thedg wrote: post #78
CafeRacer wrote: post #34

I think SAML should be available for business tier as well.

+1, great feedback

Is there any reason 'enterprise' features can't be purchased a-la-carte if your org is <X size? Or for a team of X people in a bigger org? Like, if our company has 10,000 people, but only 15 people are ever going to use your tool, we cannot justify the Enterprise pricing... I run into this all the time :(
Post reply on HN