Comment by dakolli
20 hours ago
I call this junk "meta-agentic engineering", it reminds me of people who have the coolest nvim configs, spend hundreds of hours customizing it but ultimately get less work done than the guy with minimal workflows, if any at all.
I look on twitter and it's just people building tools for agents to use agents, some weird customization loop going on in the LLM space right now. Ultimately these are trends pushed on us from model providers because they 10x token consumption. Its literally just BS trends to increase revenue at these companies, most of it is largely useless.
Some of this stuff is ludicrous. I finally tried /loop last week and discovered every loop iteration passes the entire context history to the model. So pretty quickly you're running a full 1M context window, without cache, likely just to check if something is ready or needs to be done. It's miserably terrible engineering unless your entire and only goal is to burn tokens.
Wait, why isn't context cached with /loop?
Because it's typically cached for 5min (1hr is a setting you have to explicitly opt into), and very few people run loops at a cadence of < 5 mins.
3 replies →
[dead]
I think many of us engineers (including myself) are suffering from AI-induced procrastination. Fixing that pesky bug in production isn't fun. Building a harness/workflow that detects and fixes pesky bugs in production on its own is way more fun (especially when your employer pays for tokens), and it feels just as important, if not more! So what if it didn't actually fix that pesky bug in production on its own...
I never liked the term "ricing" with window managers, but this is definitely veering into LLM ricing territory sometimes. And people are getting rich off of it.