I don't know about you, but in a lot of situations when I'm asked to build something I have to actually figure out a lot of those requirements myself, as I go along.
Theoretically that role is generally called "business analyst" or "product manager" or "product owner" but you know the difference between theory and practice.
If we'd ever reach that point of automation my money's on many programmers just switching to some sort of "business analysis". After all, this job is all about making decisions, tons of micro-decisions.
Theoretically that role is generally called "business analyst" or "product manager" or "product owner" but you know the difference between theory and practice.
If we'd ever reach that point of automation my money's on many programmers just switching to some sort of "business analysis". After all, this job is all about making decisions, tons of micro-decisions.