10,078 karma · joined May 1, 2009
[1] https://web.archive.org/web/20250708160846/https://ampcode.c...
Correct - covered here in my talk - https://ghuntley.com/six-month-recap/
AI isn't going to take anyone's jobs. Your co-worker who knows how to use multiple agents at a time and automates their job function will.
So what happens is inevitable:
- Wild promises of unlimited usage and consumers feeling tricked when the impossible is impossible to deliver (Cursor pricing changes).
- Quasi-unlimited usage with rate-caps, but the models get quantised to all hell? [search Twitter for folks reporting Claude feels dumber around/near outages].
- Engineers sharing tools and techniques on how to squeeze pounds out of a flat-rate plan (original post), which results in more power users doing that, which puts more pressure on margins.
In goose meme format, "What are the margins?"
Yes, you need to run these agents in a sandboxed environment when running full AFK [1] yolo. That could be a Docker container or it could be remote developer environment.
[1] https://ghuntley.com/overton
There are agentic models and oracle models. It can be modelled on a four-way quadrant of agent vs oracle and high safety vs low safety.
Grok is oracle and low safety.
- Uses ripgrep under the hood
- VSCode fork (thus suffers from the https://ghuntley.com/fracture problem)
- There are 14 different ways defined to edit a file due to its multi-modal design. Tuning this is going to be a constant source of headaches for the team.
- Kiro utilises a https://ghuntley.com/specs based workflow.