What's this about?
In the Chinese AI circle, Baoyu argues future software teams should keep a few deep specialists (pro front-end, pro back-end) plus a large "full-stack" middle — like company IT, where everyone knows some but experts still solve the hard problems and clean up after "vibe coding." vista8 counters that back-end stays specialist (architecture, APIs, security, scaling) while "front-end" work shifts to PMs, designers and ops.
What exactly is "vibe coding"?
"Vibe coding" is building software mostly by describing what you want to an AI and iterating on its output, rather than writing every line yourself. It lowers the barrier so non-specialists can ship things — which is exactly why people are debating who the remaining specialists need to be.
What's the community saying?
89 + 57 likes; a recurring roles-of-engineers debate.
- Specialists still needed for the hard, risky parts (architecture, security) even as the middle broadens.
- Disagreement on where the line falls — is "front-end" now a role for designers/PMs rather than engineers?
- Underlying anxiety about how AI reshapes engineering careers and headcount.