Comment by organsnyder
5 hours ago
The biggest appeal of the frontier models is for those trying to get autonomous agentic systems running that do real work with minimal human input. I went down a rabbit hole trying that with frontier models, and after a lot of initial promise it ended up actually slowing me down.
We've all been through that no? In the beginning you can do a ton of stuff without reading code. But the LLMs miss all the good abstractions, they just push and push unmaintainable code until at some point you start having more bugs and then you NEED that LLM to fix the codebase you don't understand anymore.
There are guardrails you can and must add to protect your team if you take the vibe approach: a good type system, a good database with clearly written business model and a good data model to drive your business. Make it loud and clear when something breaks with your tooling.
But... I'd definitely not vibe everything after a certain point. Reading and fixing code is also a lot of fun.
They're insanely good for prototypes though. To be able to actually see something working before deciding whether it's worth investing the time to build it for real is invaluable.
Made an account to semi-disagree with you, haha!
I have to advocate for the vibe-coded mess-colony.
There are applications where it either works or it doesn't, and it's simultaneously obvious whether it does. Think stock price prediction software. I've killed time in the evenings verbally chatting with agents about that specifically, and what emerged worked! It didn't work well, but it clearly outperformed randomness, and I was able to verify that myself easily.
I didn't look at a line of code, but I had an absolute blast.
You couldn't have possibly verified that. Stock prediction based on what? What's your sample size over what period of time? Using what indicators? how far is your lookback?
1 reply →