The Industry Qs Nobody Wants to Ask Out Loud

The industry is loud about answers and quiet about questions. That is a tell. When a field is actually changing, the honest people sound slightly lost on purpose. They ask things that would have been career-limiting in 2022 and are now the only adult conversation in the room.

Who owns the diff?

If an agent opened the PR, a human clicked merge, and production later asked a question nobody could answer, the owner is not "the model." The owner is the name on the release. We still pretend otherwise because blame is awkward and dashboards are soothing. Ownership is the ability to teach the change at 2 a.m. without opening the agent's chat log like a holy text.

What is a junior now?

If juniors only exist to type boilerplate, we have automated them into a corner and then complained they cannot think. The junior of 2026 is an apprentice in judgment: reading diffs like evidence, writing acceptance criteria that survive a prompt, learning the seams — auth, money, data — while the machine handles volume. If your junior programme is "watch Copilot," you do not have a junior programme. You have a subscription.

Is a smaller team shipping more surface a gift or a trap?

Both. A four-person shop with agents can stand up web, mobile, and a backend that used to need a department. That is leverage. It is also how you get a surface area that nobody on-call can hold in their head. South African enterprises already know this texture: lean teams, real money, networks that lie, executives who saw a demo. Capacity without recovery is just a faster way to need a weekend.

Taste versus velocity — which one is the strategy?

Velocity is what you buy. Taste is what you keep. Generated UI converges on a pleasant average. Generated architecture converges on a plausible blog post. The teams that still feel like a point of view are the ones who reject the first draft as a matter of hygiene. Taste is not aesthetics as dessert. It is the refusal to ship a system that cannot be explained.

Where did the product manager go?

Specs arrive as screenshots and voice notes. Agents propose PRs before the problem has finished forming. Someone still has to name the outcome, the non-goal, the customer who will be harmed by a clever default. If that someone is "the engineer with the best prompt," congratulations: you have a PM, you just will not pay them like one.

Are we measuring the wrong century?

Hours, lines, commits, tokens — activity with better fonts. The question that still works: what feature is out, does it hold, and can you restore it when it does not? Everything else is a supporting actor that got promoted because it is easy to graph.

Will there be jobs?

There will be work. There may be fewer seats for people whose identity was typing. There will be more seats for people who can secure, observe, recover, and tell the truth in a steering committee. That is not a TED talk. It is a staffing plan.

Ask the questions in the stand-up, not in the keynote. The keynote already knows what it wants you to feel. The stand-up still has to ship.