We have this idea of AI software development where a human watches over its shoulder and shouts out things like "use uuidv7 for the id since timing is important" or "use a sum type here to make that bad state unrepresentable".
But the thing is that most of this can be encoded in a markdown file for agents to read if it doesn't already come out of the box in the next round of sota models. And funnily enough as agents get smarter, you risk being overprescriptive where you hamstring the agent from making a pivot that would have led to better engineering.
The future is pretty clear to me at this point that we won't need software engineers looking over the shoulder and instead it's just a "user with taste" asking for revisions.
A software engineer user with taste, yes.
Have you ever been really deep in a thread with an agent on a technical deep dive? The trade-offs conversations would not make sense to someone that is not able to decode the real decisions they’re making.
You can dumb down the agent, but the reason domain language matters is because of the precision of the word sometimes - not to be a gatekeeper.
Anyway - user with taste that understands all the elements of their decisions would be my modifier :)