10 Consensus Takeaways on AI-Native Software Engineering: BAs Now Scarcer Than Devs
dotey · x · 2026-08-21
A widely shared summary of a software engineering workshop lays out 10 points of consensus on going AI-native:
- Demand side is the bottleneck: BAs are now scarcer than developers (supply ratio from 1:5 to 1:2 or 1:1) as AI accelerates coding but not requirements.
- Process redesign: 3-5 day user stories are obsolete (AI finishes in a day); use Feature granularity with acceptance criteria; store requirement docs as Markdown in the repo for AI to read.
- Role shifts: testing headcount shrinks but keep one expert; B2B projects drop dedicated UI/UX designers—BAs prototype with component libraries and AI generates HTML.
- Skills migration: everyone needs design and code-review skills; communication beats pure technical depth.
- Team shape: 4-5 person teams (BA, full-stack, test expert, solution negotiator); ops gets agenticized; pure execution is no moat—the long-term path leads to business and requirements.
More from coding & agent
- Open-source AIUsage: one dashboard for quotas, costs and accounts across 12+ AI subscriptions — tom_doerr · 2026-08-21
- Stanford researcher: automated orchestrators are a big unlock, current versions not there yet — anshulkundaje · 2026-08-21
- CopilotKit open-sources OpenBot: AI coworkers that each get their own computer — Roger_M_Taylor · 2026-08-21
- Ornith 1.5 35B Q5 runs locally inside GitHub Copilot on a Mac M3 Max — DanWahlin · 2026-08-21
- Developer ditches MacBook Pro, moves all agentic work to a Linux machine — Rasmic · 2026-08-21
- Building an AI-native email client on Cloudflare Email, Workers and AI Gateway — ritakozlov · 2026-08-21