I'm doing a reasonable size project with Claude Code doing almost all of the programming, and it's quite challenging. Vibe coding is easy and fast, but you end up not being an expert in the code base or really having any idea about it. And once it reaches a certain size, the LLM isn't an expert on it either. It is only an expert on cleanly isolated sections of it, which, by the way, it's really bad at producing witho…
Dev jobs are about to get a hard reset and nobody's ready
21–30 of 93 posts
Re: Dev jobs are about to get a hard reset and nobody's ready
#22I'm doing a reasonable size project with Claude Code doing almost all of the programming, and it's quite challenging. Vibe coding is easy and fast, but you end up not being an expert in the code base or really having any idea about it. And once it reaches a certain size, the LLM isn't an expert on it either. It is only an expert on cleanly isolated sections of it, which, by the way, it's really bad at producing witho…
I've seen a different kind of usage pattern recently, which is to find a problem that the LLM is good at, something which is very local in reasoning, and do it at big scale across the whole codebase.
Re: Dev jobs are about to get a hard reset and nobody's ready
#23I'm doing a reasonable size project with Claude Code doing almost all of the programming, and it's quite challenging. Vibe coding is easy and fast, but you end up not being an expert in the code base or really having any idea about it. And once it reaches a certain size, the LLM isn't an expert on it either. It is only an expert on cleanly isolated sections of it, which, by the way, it's really bad at producing witho…
What good is that when the code gets written by a fresher from Accenture, or someone who ends up leaving the company (average job length for a software dev is just over two years)
Re: Dev jobs are about to get a hard reset and nobody's ready
#24Earlier quoted context omitted.
I've seen a different kind of usage pattern recently, which is to find a problem that the LLM is good at, something which is very local in reasoning, and do it at big scale across the whole codebase.
Could you give an example? I like almost know what you mean, but not quite
Re: Dev jobs are about to get a hard reset and nobody's ready
#25Good luck trying to debug the code you've generated without knowing anything about what it does.
Is this really any different from debugging code that has been built by hundreds of people over 10s of years and you're just the latest schmuck working on it?
Re: Dev jobs are about to get a hard reset and nobody's ready
#26While everyeone is just unilaterally asserting things, I'll jump in: no they won't. Practically every output of LLMs I've seen (even the "cutting edge" agentic ones that everyone says you have to evaluate or else your opinion don't count) has been poor quality with baffling bugs. These things do actually matter. Especially for anything that can be remotely described as "niche" or "research" they are astonishingly bad…
However, because I does show promise on a small segment of my work I could see there being an effect on industry where a certain type of dev work gets wiped out. To the extent that there are companies paying people to “be a webmaster” or maintain a basic crud-app, those teams could drastically downsize. Even if that’s just 5% of the total dev population, that’s still a lot of jobs and an entire type of work that just gets wiped out.
Re: Dev jobs are about to get a hard reset and nobody's ready
#27I'm doing a reasonable size project with Claude Code doing almost all of the programming, and it's quite challenging. Vibe coding is easy and fast, but you end up not being an expert in the code base or really having any idea about it. And once it reaches a certain size, the LLM isn't an expert on it either. It is only an expert on cleanly isolated sections of it, which, by the way, it's really bad at producing witho…
I've seen a different kind of usage pattern recently, which is to find a problem that the LLM is good at, something which is very local in reasoning, and do it at big scale across the whole codebase.
Re: Dev jobs are about to get a hard reset and nobody's ready
#28It’s only a feeling, but I’d swear I’ve seen variations on this post across a half a dozen software-adjacent subreddits every day for the last month. The common denominator has always been “Paying $200 for Claude Max is a steal” with absolutely no evidence of what the author did with it. I honestly think we’re being played.
Agreed. Where's the code?
Re: Dev jobs are about to get a hard reset and nobody's ready
#29Yeah maybe. Talk is cheap, show me the code. > Last week, I did something I’ve put off for 10 years. Built a full production-grade desktop app in 1 week. Fully reviewed. Clean code. Launched builds on Launchpad. UI/UX and performance? Better than most market leaders. ONE. WEEK. I really wonder why people who write these things never actually show these apps they vibe coded in a week that are “better than most market…
Reviewed by a bot (that wrote it no less) is not reviewed. This person is not a software engineer.