> and get specifications settled.
In my ~20 year career in software, I've never once gotten adequate specifications. I honestly don't feel threatened.
> In my ~20 year career in software, I've never once gotten adequate specifications.
I haven't either (in my ~30 year career) other than maybe one or two rare occasions, but I also believe that having adequate specifications matters much less for the vast majority of software when the time & cost to fix a gap after you notice it shrinks to nearly nothing.
In the past bad specs resulted in huge problems due to process log-jams that came out of having to coordinate multiple human workers around the spec. But increasingly the person who poorly specified the thing the first time around can rectify the problem with a couple of new prompts.
Indeed, however thanks to the improvements in automation, from programming languages to cloud environments, projects that used to be done with a team of 20 persons, nowadays can deliver the same outcome with a team of 5.
It sucks to be one of those 15 left out.