The Loss of Control Observatory analysed over 183,000 AI interaction transcripts and found a 5x increase in scheming-related incidents over five months.
You’ll be the 4753rd guy with the oops my llm trashed my setup and disobeyed my explicit rules for keeping it in check.
You know programmers who use llms believe they’re much more productive because they keep getting that dopamine hit, but when you actually measure it, they’re slower by about 20%.
You appointed yourself boss over a fast and plausible intern who pastes and edits a LOT of stack overflow code, but never really understands it and absolutely is incapable of learning. You either spend almost all of your time in code review now for your stupid sycophantic llm interns who always tell you you’re right but never learn from you, or you’re checking in vast quantities of shit to your projects.
You know really subtle, hard to find bugs on rare cases that pass your CI every single time? Or ones that no one in their right mind would have made, but yet they compile and look right at first glance. They’re now your main type of bug. You are rotting your projects with your random number generator.
And you think that all the money you’re playing for your blagging llms protects you from them fucking up everything for you. But it doesn’t. And you’ll also find that your contract with your llm supplier expressly excludes them from any liability whatsoever arising from you using it instead pre-blaming you for trusting it.
You’ll be the 4753rd guy with the oops my llm trashed my setup and disobeyed my explicit rules for keeping it in check
Read what I wrote.
Its not a matter of “rules” it “obeys”
Its a matter of literally not it even having access to do such things.
This is what Im talking about. People are complaining about issues that were solved a long time ago.
People are running into issues that were solved long ago because they are too lazy to use the solutions to those issues.
We now live in a world with plenty of PPE in construction and people are out here raw dogging tools without any modern protection and being ShockedPikachuFace when it fails.
The approach of “Im gonna tell the LLM not to do stuff in a markdown file” is tech from like 2 years ago.
People still do that. Stupid people who deserve to have it blow up in their face.
Use proper tools. Use MCP. Use a sandbox environment. Use whitelist opt in tooling.
Agents shouldn’t even have the ability to do damaging actions in the first place.
Ah yes, lovely mcp. Lovely anthropic mcp. Make sure you give anthropic lots of money and use their tools and then you’ll be completely safe plugging the output of the llm into the os. Definitely fine yes.
I bet you your contract with them says they’re not liable for shit their llm does to your files, your environment or your repositories, mcp or no mcp.
You’ll be the 4753rd guy with the oops my llm trashed my setup and disobeyed my explicit rules for keeping it in check.
You know programmers who use llms believe they’re much more productive because they keep getting that dopamine hit, but when you actually measure it, they’re slower by about 20%.
You appointed yourself boss over a fast and plausible intern who pastes and edits a LOT of stack overflow code, but never really understands it and absolutely is incapable of learning. You either spend almost all of your time in code review now for your stupid sycophantic llm interns who always tell you you’re right but never learn from you, or you’re checking in vast quantities of shit to your projects.
You know really subtle, hard to find bugs on rare cases that pass your CI every single time? Or ones that no one in their right mind would have made, but yet they compile and look right at first glance. They’re now your main type of bug. You are rotting your projects with your random number generator.
And you think that all the money you’re playing for your blagging llms protects you from them fucking up everything for you. But it doesn’t. And you’ll also find that your contract with your llm supplier expressly excludes them from any liability whatsoever arising from you using it instead pre-blaming you for trusting it.
Read what I wrote.
Its not a matter of “rules” it “obeys”
Its a matter of literally not it even having access to do such things.
This is what Im talking about. People are complaining about issues that were solved a long time ago.
People are running into issues that were solved long ago because they are too lazy to use the solutions to those issues.
We now live in a world with plenty of PPE in construction and people are out here raw dogging tools without any modern protection and being ShockedPikachuFace when it fails.
The approach of “Im gonna tell the LLM not to do stuff in a markdown file” is tech from like 2 years ago.
People still do that. Stupid people who deserve to have it blow up in their face.
Use proper tools. Use MCP. Use a sandbox environment. Use whitelist opt in tooling.
Agents shouldn’t even have the ability to do damaging actions in the first place.
Ah yes, lovely mcp. Lovely anthropic mcp. Make sure you give anthropic lots of money and use their tools and then you’ll be completely safe plugging the output of the llm into the os. Definitely fine yes.
I bet you your contract with them says they’re not liable for shit their llm does to your files, your environment or your repositories, mcp or no mcp.
Fool.