> We're collectively so steeped in posturing about technology stacks and idiosyncratic decisionmaking that we've missed the bigger picture: get something done.

> At the end of the day no one cares if you're a good developer. They care that the service looks good and works well.

Those decisions lead over time to an architecture that can good or bad, and assuming your software has patches or improvements over time, that's important.

Context: I've worked with too many startups with non-dry untested code that are now getting past "looks good and works well" to needs to drastically expand feature set or change underlying features.