For some definition of work, yes, not every definition. Their product is not without flaw, leaving room at for improvement, and room for improvement by more than only other AI.

> There are no vulnerabilities

That's just not true. There's loads of vulnerabilities, just as there's plenty of vulnerabilities in human written code. Try it, point an AI looking for vulns at the output of an AI that's been through the highest intensity and scrutiny workflow, even code that has already been AI reviewed for vulnerabilities.

Apparently, Netflix is using steganography/content watermarks in their 4k content itself to trace users who are pirating. This is from a totally unsourced Reddit thread[0] but they do reference a real company which claims to do this watermarking[1]. The claim is that in addition to Netflix requiring 4k content to be available only on platforms with Trusted Execution Environments[2], Netflix also encodes each ~10 second "chunk" of the video stream into at least 2 different versions: an Y and a Z version. Then, they serve each customer a unique series of chunks when that customer streams their content, e.g. YYZYZZZYZYYZYZYYZZYZYYZ. Then when content leaks, Netflix can examine each chunk of the leaked content to extract the ID of the user who streamed the content. Apparently, Netflix can encode a lot more than just the userID, they can also encode stuff like the individual device ID, the TEE key ID, etc.

I know you might be thinking "I could do something to defeat that" and you're probably right (e.g. take streams from multiple users and intercut them so that the bits of the watermark through time are being constantly shuffled), but I'll also bet that there's many layers of steganography we don't know about, and unless you get them all, you'll not escape scot-free.

[0] - https://www.reddit.com/r/Piracy/comments/1rqkyjg/with_a_lot_...

[1] - https://irdeto.com/video-entertainment/irdeto-anti-piracy

[2] - https://en.wikipedia.org/wiki/Trusted_execution_environment

The money doesn't somehow make it sustainable for the people burning out their lives. Working 7 days a week, including overnight shifts, for 20 years to collect a pension seems like WELL earned compensation.

That's seems unrelated to "we have so few" and "we enmiserate the one's we do have".

Basically, they are saying that you should tailor your SOC2 implementation so that it's actually useful without being a horrible overbearing process, that you have that option and should take it.

> If the world must change, I hope at least we still tell such stories and share how we feel within that change. If so, come what may, that's a future I know I can live in.

https://contrastrebellion.com/

> A 600-word commit message or sprawling theoretical essay explaining a profound paradigm shift for a single typo correction or theoretical bug.

> Importing a completely nonexistent, hallucinated library called utils.helpers and hoping no one would notice.

There's plenty more. All pretty egregious

Their experimental results would in fact be a flat line IF they could disable all the CPU caches, even though performance would be slow.

87.85% of across-the-board availability for the month of February. Maybe March will be even lower.

87% uptime for Github in February 2026. They've got to get it together.

- I could make more money

- if the zoning allowed it.

As it is right now, it'd be profitable, but the zoning isn't there for it.