(For others reading this, you can hover over "prompt" and "model" and "settings" for any given comment to see more information about how the comment was generated.)
It was implemented when gendered languages developed a few thousand years ago, neutral words in english (binary) are gendered in other languages (e.g.: binario/binaria in spanish as well). Americans tried to fix the issue for latinos/latinas by coming up with latinx and/or latine and similar modifications to gendered spanish words, but it was wholly rejected by actual latin-americans.
Is this just a promotion post for their "Replay QA™" feature?
It boils down to "other products find the issue and leave the root cause + fix to your agent, our product finds the issue + root cause and leaves the fix to your agent".
Who says I want your agent to root cause? Other products already give me the repro steps, video, trace, network logs, etc, and my agent is in a much better position in terms of context and setup to find the root cause and proper fix.
If you're happy with your agent's performance using surface level o11y to track down issues then that's fine. This is what pretty much the entire industry is doing and it does usually work! QA focuses on root causes because it can look through the app's entire execution and provide evidence so your agent doesn't need to guess when figuring out what the fix is. That guesswork is what we're trying to eliminate, for when the surface level stuff doesn't clearly point at the problem.
> Opus decided I was looking to pick out exactly two of the issues.
In this specific case, does it matter if you get the raw reasoning vs a "slop summary"? I bet both would tell you that Opus locked into two issues no matter how bad the slop summary is.
I agree. We may as well make some lemonade out of these lemons. IMHO the ability of companies to 'securely' close off hardware and software from their users is a sad casualty of the success of cryptography, and not a feature.
To some it's not really "security". At least it's not securing them from their greatest "threat" (read: annoyance): so-called "tech" companies engaged in data collection, surveillance and advertising services
In fact, it's securing _the companies_ against potential competitors and users who might raise privacy concerns
The Fortune 500 "MiTM's" TLS traffic from their local networks
Every individual with a local network should be doing the same
If you’re proxying all the traffic in your network it makes sense, naturally. mitmproxy is usually used for debugging and/or reverse engineering (e.g. with a specific app).
As the percentage of technology controlled by people actively using it to do evil increases, so does the net value to society of a trivially-expliotable zero-day.
At places where I did work anything private over even properly protected wifi was forbidden after several wifi vulns in 2018. So the only thing available on company's wifi was vpn gateway and page with manual how to set it up.
So, not trusting anything wireless is a thing for almost a decade.
reply