171–180 of 524 posts
Earlier quoted context omitted.
> Claude, fix the bug. Make no mistakes. /s
You forgot to add "you are an expert software engineer with PhD level architecture insights".
Earlier quoted context omitted.
> I understand the impulse to provide a UI to manage codebases, etc. […] 'I don't care what's happening, just ask Claude to do it'. Reading the first part, I was going to say they don’t even care about whether or not there’s a codebase. It doesn’t matter; it could be all gremlins and hamsters in wheels for all they care, and for all they should care. All that matters is the functionality, the value it gives them. We’…
When I quit my day job and started Rails freelancing a big chunk of my work was from companies with "that tech guy" who had built a database in Microsoft Access that was vital to the department's operations. And then either left the company - or the app had started to fall apart under its own weight. I would get called in to rewrite it, using a proper database, documented rules and ensure it stayed scalable - and eve…
I think what a lot of us are concerned about is that the vibe-coded stuff bloats fast. It's so verbose and all over the place, that picking that thing apart will be a huge job, and relying on an AI to pick apart work that an AI already failed to maintain seem like wishful thinking.
It's literally "The AI is failing! Don't worry I'll just use AI to fix the AI!".
Earlier quoted context omitted.
The future is perpetually dealing with the fallout from all the vibe coding as the pool of people who'd have a shot at fixing it gets smaller and smaller. Shitty will be the new normal.
> Shitty will be the new normal. I’ve heard the same from the best devs, and some who thought themselves to be the best, I’ve known long before LLMs were ever a thing. I’m sure others heard the same when JavaScript and Python became near ubiquitous. When PHP emerged. When C supplanted Fortran and COBOL. When these two took over from Assembly. When punch cards went the way of the dodo. There’s always someone for whom…
Coding per se is not hard. Proper engineering is. I do hope this change brings a change in focus (people train in algorithms, efficiency, solid development patterns) but I am afraid it won’t be the case.
Earlier quoted context omitted.
> that makes claude code or codex accessible to the average user That's what they aim Claude Cowork at. Every executive/leader I've shown Claude Cowork to has gone from 'what is AI' to 'vibecoding whole apps' in weeks. Then when Claude is down for an hour, they get visibly angry and don't remember how to do anything pre-Claude :) I understand the impulse to provide a UI to manage codebases, etc. But my observation is…
> Then when Claude is down for an hour, they get visibly angry and don't remember how to do anything pre-Claude :) The drug is scary when everyone is depending on it. I wonder what is future like.
Earlier quoted context omitted.
The future is perpetually dealing with the fallout from all the vibe coding as the pool of people who'd have a shot at fixing it gets smaller and smaller. Shitty will be the new normal.
> Shitty will be the new normal. I’ve heard the same from the best devs, and some who thought themselves to be the best, I’ve known long before LLMs were ever a thing. I’m sure others heard the same when JavaScript and Python became near ubiquitous. When PHP emerged. When C supplanted Fortran and COBOL. When these two took over from Assembly. When punch cards went the way of the dodo. There’s always someone for whom…
Earlier quoted context omitted.
The future is perpetually dealing with the fallout from all the vibe coding as the pool of people who'd have a shot at fixing it gets smaller and smaller. Shitty will be the new normal.
> Shitty will be the new normal. I’ve heard the same from the best devs, and some who thought themselves to be the best, I’ve known long before LLMs were ever a thing. I’m sure others heard the same when JavaScript and Python became near ubiquitous. When PHP emerged. When C supplanted Fortran and COBOL. When these two took over from Assembly. When punch cards went the way of the dodo. There’s always someone for whom…
Earlier quoted context omitted.
The future is perpetually dealing with the fallout from all the vibe coding as the pool of people who'd have a shot at fixing it gets smaller and smaller. Shitty will be the new normal.
> Shitty will be the new normal. I’ve heard the same from the best devs, and some who thought themselves to be the best, I’ve known long before LLMs were ever a thing. I’m sure others heard the same when JavaScript and Python became near ubiquitous. When PHP emerged. When C supplanted Fortran and COBOL. When these two took over from Assembly. When punch cards went the way of the dodo. There’s always someone for whom…
Also we went from compilers with an IDE that had a debugger, profiler, built-in help and would fit on a 3.5" disk and would load on machines with 640KiB RAM (Turbo Pascal) to chat apps or password managers that are hundreds of megabytes and regularly gobble up more than a gigabyte of memory because they ship with their own browser.
Something is lost along the way.
Let me get this straight: a few times per month, someone posts horror stories about how Claude led to losing data and money. Anthropic's response: let's make a nice package out of this, and let's target specifically the businesses that are less likely to be ready to manage such horrible events.
I'm increasingly convinced that there's a killer app waiting for whoever can come up with a UI that makes claude code or codex accessible to the average user. Onboarding my non-software engineer teammates to it has super-charged them and essentially given them all their own personal developer that can automate tasks for them. Managing codebases, etc. is still a hassle though. 90% of the power of Excel was that it was…
The power of Excel is not what it was. Nor is the power of ordinary thought.
Earlier quoted context omitted.
When I quit my day job and started Rails freelancing a big chunk of my work was from companies with "that tech guy" who had built a database in Microsoft Access that was vital to the department's operations. And then either left the company - or the app had started to fall apart under its own weight. I would get called in to rewrite it, using a proper database, documented rules and ensure it stayed scalable - and eve…
But at least you could basically follow their logic. I think what a lot of us are concerned about is that the vibe-coded stuff bloats fast. It's so verbose and all over the place, that picking that thing apart will be a huge job, and relying on an AI to pick apart work that an AI already failed to maintain seem like wishful thinking. It's literally "The AI is failing! Don't worry I'll just use AI to fix the AI!".