This comparison between the construction industry and the software industry always comes up, and it's always wrong.
Once you've built a building, you can't change it easily. This is not true of software.
The biggest problem in building software is not writing the code, but understanding the problem. It is often massively easier to build a throwaway prototype to understand the problem, and then build a "real" version with much better understanding of the problem, than it is to collect all the requirements in the first place.
This isn't an option open to architects. There are lots of options that are not open to architects. The two industries are very different, for very good reasons.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This comparison between the construction industry and the software industry always comes up, and it's always wrong.
Once you've built a building, you can't change it easily. This is not true of software.
The biggest problem in building software is not writing the code, but understanding the problem. It is often massively easier to build a throwaway prototype to understand the problem, and then build a "real" version with much better understanding of the problem, than it is to collect all the requirements in the first place.
This isn't an option open to architects. There are lots of options that are not open to architects. The two industries are very different, for very good reasons.