What managers think: https://youtu.be/-TKjwblp1XI?t=1373
Point being, nobody gets a documentary about themselves made for delivering against a boring deadline.
People say they want to be famous, what they want is the adoration of their peers. When they find out the two aren't the same thing, they often have a hard time of it. Being famous means you can't have a slice of cake in peace while you contemplate the news your doctor just gave you. It means everyone gets to have an opinion about every setback you experience from then on.
Famous people are hated all the time. Or adored by people who are a worse fate than being hated.
You're telling me that isn't satire?
I believe a contributor to why choosing boring is hard is that often the problem we encounter in software is not new or unique, but may still the be first time a team/company is attempting it. Therefore, unless you know your company has the patience for unforeseen technical difficulties, and that your team has the skillset to overcome any fundamental challenges posed by the technology chosen, even if the technology is a better fit for a problem, it may not be a good match for the organisation.
[0] http://cloudscaling.com/blog/devops/continuous-delusion-at-t...
You'll constantly get into arguments about why we're not deploying the new upcoming thing that obviously fixes the issue.
At some point you'll need to switch over anyways, its better to get production battle experience by trying the new tech early and rolling it out where it makes sense.
It avoids internal factions and the "shadow infrastructure" that was mentioned.
Problem is, the old thing has known benefits and known flaws, while the new thing has known benefits but unknown flaws.
I think I'd claim the new thing has _claimed_ benefits. Very often those benefits turn out to be nonsense, driven by marketing and hype cycles.
By a Tesla, it has Auto Pilot!
By autopilot we just mean some slightly more advanced driver assist, it's not actually autopilot, and if you treat it as such you're probably going to die, at best.
The advice is that you take the new tech and do a boring thing with it first, like deploy or build something non-critical and gain the production experience that way.
The least interesting thing to do would still be to stabilise $old while carefully getting $new ready.
