It doesn't make much sense to invest effort into verifying a plausible-looking throwaway solution that is reviewed and smoke-tested by an LLM, with a quick glance from a tired human.

This results in complexity creep everywhere: decisions, communication, code, documentation, etc.

On par with cognitive debt, as thinking and decision refinement were offloaded, nobody gained unique experience solving a niche use case. This is equal to having a knowledgeable person leave the company before the knowledge transfer occurred. All you're left with is a legacy of someone else's assumptions and decisions you'll never be fully aware of.

I already see it happening. In support, LLMs never solved any of my support requests. Support, which should know the product inside out, recommends visiting pages and clicking buttons that are hallucinated and don't exist in the product. In code, codebases are ballooning with unreasonable complexity. In product, interface decisions are outsourced to LLMs, making companies arrive at the same solution for their unique niche problems.

Are you observing something similar?

Comments URL: https://news.ycombinator.com/item?id=48819891

Points: 7

# Comments: 3

Also, the title is misleading, setup adds config to be auto executed by people who work on the repo. They would have to use vscode/cursor/claude/gemini. People who use codex / opencode / other harnesses are safe I guess.

Details: https://www.stepsecurity.io/blog/miasma-worm-hits-microsoft-...

Are they going to rectify this by laying these people off?