"Fixing large oopsies is just a prompt away" really depends on what you are doing.
I write software responsible for updating customer controlled devices. In theory, these devices may be in use for decades. I don't get to dictate when customers update their software. I have to use whatever software is on device as part of the update process, and the software update process really should work from every single version that's ever been deployed.
So whatever decisions I make / the team makes, generally we're stuck dealing with in some form for the device lifetime.
Completely agree. But why do you think the reviewer would choose a better abstraction?
Yes, an experienced dev has a high chance of doing so. But in most teams there are not enough experienced devs.
And even I, an experienced dev, choose wrong abstractions all the time.
But fixing even large oopsies is just a prompt away. So imo it does matter less and less.
What was and is true: iteration speed just matters more. I would bet a lot of money that a team that goes from written code to merge in hours has a better quality codebase than one that takes weeks.