And if you’re working in a business building a modern web application then it’s extremely hard to imagine the stakeholders being happy with software developed using absolute lowest common denominator tools techniques and libraries, as advocated by the “boring software” movement.
Competitive advantage and the expectations of customers leads to the need to use modern tools techniques and libraries.
And in fact developers deserve these things too because they tend to make things easier more powerful and more reliable.
If the stakeholder who is paying for the project says “can we have an animated user education intro”, and you say “no because we use boring technologies and our developers might not understand how to use the animation APIs” them I think your job would be at risk pretty quick.
Some cases need a very boring CRUD setup, yet other will require distributed events passing around CRDTs.
I've worked on terrible projects built with boring tech that was perfect for simple CRUD, but where the project wasn't anything CRUD at all but parsed huge datasets of time series, combined with events and changesets. The 'boring tech' was such a bad fit, that the project ground to a halt, cost enormous budgets just to keep running, and was impossible to move forward.
Software should be written to meet specific needs.
And those needs should be defined.
And it’s likely a software project will have many tens of needs defined.
And amongst all those needs it will become clear what technologies fit the needs.
A blanket statement like “choose boring technology” only fits projects where the project needs result in that outcome.
My guess is that systematic definition of requirements will result in very very few projects “built using boring technology”.