Wage workers are evaluated on behaviors, founders are evaluated on growth and revenue. Of course usage patterns and outcomes will be different

It's not required for startups. But if you are building trashy, brittle products and your main metric is speed to market, and have the expectation of high failure chances (e.g. most yc startup batches) - then yes you have to do agentic eng.

If you are making extremely specific, high quality products over a long time window and your founders are deeply experienced in that field of engineering, then no, you don't need agentic engineering and probably want very little llm code in general (outside of some boilerplate, internal toolings, etc).

I think GenAI-agentic assisted engineering is the only way of working nowadays, and it's the only way I personally have worked for months. I still think that an outright majority of presentations on AI tooling I've seen have been in the nonsensical "Look how many tokens I can burn" genre. Had to sit through one guy recently who explained why you need a complex agentic team with 6 different roles in order to ask Claude to investigate a bug, which you most definitely do not.

A guy at my company (very old company, we need to maintain our software for 30+ years) gave a presentation about how they used opus 4.6 to onboard people, like giving new team members access rights etc. Then another guy (even higher in management) proposed using a team of agents for that.. It's getting pretty wild

> I still don't know how to reconcile these reports

This is work related. So you can't expect everyone to have the same input demands or output expectations.

> Probably there is no dichotomy

It's literally staring you in the face.