It's true that sometimes fashionable skills stick around. I think of all my past coworkers that dismissed: git, CI, repository branches, unit and integration te

It's true that sometimes fashionable skills stick around. I think of all my past coworkers that dismissed: git, CI, repository branches, unit and integration tests, code review, local development databases, automated deployment, automated migrations, separating display logic from business logic, putting comments in git commits instead of in code comments, and removing secrets from code. Almost two decades later most is these are taken for granted in mature teams. On the other hand, some tools and techniques are on a continuum: microservices/monoliths, thick/thin UI clients, schema/schemaless databases, SQL/ORMs, strong+static/weak+dynamic types. A team needs to carefully consider their project to determine what fits best (and it might change over time). None of these are "always the right choice." We have very little science about how to accurately determine the needs of a project, so we get a lot of hearsay and fashion.