Remix.run Logo
▲ cautiouscat an hour ago

I feel like comments like these, are from people who don’t work with complex systems. There is absolutely a ceiling to vibecoding and I don’t think it’s technical.

When systems get complex, someone needs to know them and know where to burn the tokens. You need to know what events need to be produced because you have specific consumers. You need to know your business invariants and why.

If you’re working on something that isn’t complex, yeah I can see why you’d think you can be replaced. If it’s just a front end? Yeah I can see that. A basic CRUD service? Sure. A business critical domain service with events, data migrations, complex business logic? I don’t see it.

▲sbysb an hour ago | parent | next [-]

It is because the average developer has outsourced all product thinking to an external team. The gravy train might actually be over for the Software Engineer that takes a Jira ticket and produces a PR, but in my opinion the demand for Product Engineers is only going to increase.

However it will be similar to cybersecurity in that there will be no 'entry level' product engineer. It will probably have requirements having worked in customer service or finance or some other adjacent field to get a larger picture of what you are delivering. You will also not need 3000 of these individuals anymore (did we ever really??)

I can see a world where you go from "AI Shepard Customer Success rep" -> some middle role with increasing 'product' responsibilities -> Product Engineer.

The new roles will also probably be more generic - instead of backend and frontend you have 'Backend' (Infra + API) and 'Frontend' (Frontend + Design) and both of these roles will require genuine product thinking

▲kalcode 10 minutes ago | parent | prev | next [-]

Many LLMs are working on huge complex codebase. I'd look inwards at engineers unable to get it to work on large codebases. No different than sending a contractor in. Do you tell the contractor "understand the entire codebase, business context and documentation all at once!"

No, and it's the same with leads, they can be given a system they understand but need to reference it.

I'm very certain these are people brushing up against their lack of processes, workflows, or engineering practices.

The context are large enough. You do not need to understand the world to build a chair.

I see the very opposite in many different domains happening now, and some codebases are monsterous. They are figuring out ways that do indeed work well.

The engineers that are figuring out these problems when working with a new tool, will have jobs.

Those who continue to doubt, and distance themselves are the ones that will be behind.

▲garrickvanburen an hour ago | parent | prev | next [-]

even somewhat complex systems.

currently working on an initial product for a startup and while I'm substantially further along that I would be without LLMs, I'm at the point where the LLMs are now randomly breaking things.

▲kannanvijayan 3 minutes ago | parent [-]

I'm similarly working on a complex project and have run into these issues.

There's typically a combination of issues that are occurring when the codebase goes off the rails.

One is that cruft builds up. Large vibecoded codebases need regular "review cleaning". Where you review the whole thing top down for hygiene, contradictions, bad comments, style, redundancy, design. It's a standard thing for me now. A full review and cleanup pass once every couple months.

The second thing that tends to go wrong is that after a certain complexity threshold, the models cannot keep track of the relevant details for a task very well. They lose sense of project directionality. Every task gets disconnected from other tasks and they start pulling the system apart at the seams, exacerbating the cruft issue above and accelerating collapse.

I've found that separating my documentation into three distinct lobes helps: goaling docs, guardrail docs, and implementation docs. Goaling docs describe in prose the goals of the project which includes scope, certain design targets, and other things that you are aiming towards. Guardrails are for design and implementation choices you have explicitly ruled out, the "what not to do" part. Impl docs describe the state of the system as it is.

The top-level agent documents refer to these and make their purpose explicit.

You'd think a ticketing system might capture this, but it doesn't really provide the richness of expression a collection of documents in a directory does.

These approaches aren't perfect. The process still has a tendency to wander off the rails, but it happens less often now and I catch it more quickly. Every session misses little bits of the goaling alignment, but they also find and address small issues missed by previous sessions. Overall it does a better job of keeping the codebase hovering around some threshold of coherency.

I'm having a lot of fun to be honest. Yes it's bizarre and nothing like what development used to be, but it finally feels like there's some new things to learn now.

▲apexalpha an hour ago | parent | prev | next [-]

What makes you think there won't be a (specific) model for that, too?

▲djha-skin an hour ago | parent | prev | next [-]

This is more of a "table saw" moment. Table saws didn't obsolete carpenters, but it did mean now you only needed one.

▲cmrdporcupine an hour ago | parent | prev | next [-]

I agree and it's why I find it hilarious to find places still trying to hire based on whiteboard coding and skillz testing nonsense.

It's not that I don't think those skills are important, but they betray a fundamental misunderstanding of what SWE is, which is about managing systems, juggling complexity, and having some wisdom about how those things should fit together.

Hopefully we start to better formalize some more of that now that the grunt work can be taken out of the equation a bit. And teach it in schools, find ways to measure it in interviews. etc

▲dboreham an hour ago | parent | prev | next [-]

For me the experience is very similar to what it was like to manage a software operation with humans working for me. Actually for the first year or so it was like that where I was the senior engineer and AI was the junior devs. But then it got good enough that it could also be a trusted senior level advisor. So I'm just setting the project scope and general direction and making the odd tweak here and there now. I'm truly baffled by posts saying that AI is terrible in late 2026. My very heavy use experience is quite the opposite.

▲paul7986 an hour ago | parent | prev | next [-]

All digital forms of work are a dying field. Designing and building applications is now similar to writing a song with SUNO. Pumping out slop and anyone can do it even my friend working in an Amazon warehouse (never coded anything and a zero technical background) is pumping out apps.

What we the people need to do is gain control and hold all the power of AI in our hands - not the filthy rich's hands! Devise systems that flip the power into our hands and create economies and jobs around it (i have ideas and surely 1000s to more do to around this).

▲bothers an hour ago | parent | prev [-]

[dead]