231–236 of 236 posts
Earlier quoted context omitted.
[flagged]
Like I said, it's embarrassing to hold onto a model of a world that does not match reality for this long but if it helps you cope...
Please stop inundating us with bad code. At least make sure your diffs compile before attaching them to the PR.
Earlier quoted context omitted.
This is what people were saying about Rails 20 years ago: it wows the kids who use it to set up a CRUD website quickly but fails at anything larger-scale. They were kind of right in the sense that engineering a large complex system with Rails doesn't end up being particularly easier than with Plone or Mason or what have you. Maybe this will just be Yet Another Framework.
Ruby OnRails is an interesting hype counter point. A substantial number of the breathless LLM hype results come, in my estimation, quicker and better as 15 min RoR tutorials. [ Fire up a calculator (from a library), a pretty visualization (from a js library), add some persistence (baked in DB, webhost), customize navigation … presto! You actually built a personal application. ] Fundamental complexity, engineering, sc…
Agreed, but: being able to read and apply the 1st-party documentation is a virtue
> You no longer need to review the code. Or instruct the model at the level of files or functions. You can test behaviors instead. Maybe for a personal project but this doesn't work in a multi-dev environment with paying customers. In my experience, paying attention to architecture and the code itself results in a much more pliable application that can be evolved.
Agree. And with the comments in the thread. I'll caveat my statement, with AI ready repos . Meaning those with good documentation, good comments (ex. avoiding Chestertons fence), comprehensive interface tests, Sentry, CI/CD, etc. Established repos are harder because a) the marginal cost of something going wrong is much higher b) there's more dependencies c) this makes it harder to 'comprehensively' ensure the AI didn…
And not even by much, 1/2/4 have always been signs of good engineers.
I am still a WindSurf user. It has the quirk of deciding for itself on any given day whether to use ChatGPT 5.2 or Claude Opus 4.5 in Cascade (its agentic side panel). I've never noticed much of a difference, they are both amazing. I thought the difference must be in how Claude Code does the agentic stuff - reasoning with itself, looping until it finds an answer, etc. - but I have spent a fair amount of time with Cla…
Wondering too, I found Windsurf excellent for what it does, but do miss my preferred $EDITOR
> You no longer need to review the code. Or instruct the model at the level of files or functions. You can test behaviors instead. Maybe for a personal project but this doesn't work in a multi-dev environment with paying customers. In my experience, paying attention to architecture and the code itself results in a much more pliable application that can be evolved.
I know this because I am at one now making an ungodly amount of money with 50k active users a day on a complete mudball monothilic node + react + postgres app used by multiple Fortune 100 companies.