(I said "good guidance" but it might be more correct to say that it's the best guidance we have, it's what Anthropic says about their own model.)
15 karma · joined March 21, 2018
(I said "good guidance" but it might be more correct to say that it's the best guidance we have, it's what Anthropic says about their own model.)
I found vomit with a small LLM much better than anything Opus 5 ever wrote. I don't think Opus 5 can write.
I wrote a little bit about it on my blog post. It's a waste of money and compute.
Blog post: https://zachahn.com/posts/1787191554
The prompt I use to tell the LLM what to fix: https://github.com/zachahn/vomit/blob/main/internal/config/s...
Wasn't received too well on Lobsters haha, wrote a small extra blurb about it there: https://lobste.rs/s/juekuk/how_fix_claude_5_s_token_vomit
About modularity, there are projects like Mongoid which can completely replace ActiveRecord. And there are plugins for the view layer, like "jbuilder" and "haml", and we can bypass the view layer completely by generating/sending data inside controller actions. But fair, I don't know if we can completely replace the view and controller layers.
I know I'm missing your larger point about architecture! I don't have so much to say, but I agree I've definitely worked on some hard-to-maintain systems. I wonder if that's an inevitability of Rails or an inevitability of software systems—though I'm sure there are exceptional codebases out there somewhere!
[1] https://guides.rubyonrails.org/7_1_release_notes.html#compos...