My thoughts exactly, though it should be noted that the architecture astronauts are more common in customer facing software. In most backend projects I've been involved in, the final state of the project is so well known, all different corner cases are well covered by the chosen architecture. For frontend clients however, the architectural choices mostly end up being tech debt.
Sometimes I prefer "and then, and then, and then" over "sign up async observer, send through our java-redux, oops forgot to implement async actions, hack in an and then and then and then case into it" -solutions.
Few times, alas. Most of the times it's some over-engineered monstrosity by architecture astronauts or people trying to be clever.