My 2c. A lot of what’s being discussed here may boil down to experience (or lack thereof) of writing good functional (and non-functional) requirements. Some developers are always thinking about implementation (or at least, implementation approach), and as a result they are very technically prescriptive. There’s nothing wrong with that per se if you’re actively driving towards a specific architecture (for your own reasons - which could be specified as non-functional reqs).
What others are describing is the BA skill of capturing good _business_ requirements ie. specifying outcomes and qualities rather than methods.
We should be clear about who’s being the BA, the architect and the developer here. At one end, a human vibe coder is acting as BA and the AI as architect, designer and engineer. At the other end, the human is a senior dev closely instructing a AI junior dev. All approaches are valid depending on what you need and the AI tools available (eg. SOTA model vs small self-hosted open-weights model).
What others are describing is the BA skill of capturing good _business_ requirements ie. specifying outcomes and qualities rather than methods.
We should be clear about who’s being the BA, the architect and the developer here. At one end, a human vibe coder is acting as BA and the AI as architect, designer and engineer. At the other end, the human is a senior dev closely instructing a AI junior dev. All approaches are valid depending on what you need and the AI tools available (eg. SOTA model vs small self-hosted open-weights model).