> The problem the way I see it, is that people don't just experiment with new architectures within the confines of an existing system. Typically they give in to

> The problem the way I see it, is that people don't just experiment with new architectures within the confines of an existing system. Typically they give in to the "second system effect" Have you tried to advise them otherwise? > Or maybe even suggestions that have some caution codified into them But then every suggestion is couched in a ton of warnings. Not only is this a bit useless, but if someone does start to depend on it they're at risk of a suggestion which lost its warning. Like, say the warning runs onto the next page and that page got lost. There are an infinite number of possible suggestions and all could potentially rabbit-hole a team to death. Why not embrace immutability? Why not go serverless? Why not migrate to on-prem hardware? Why not use a memory-safe language? It seems far better to build some sort of suggestibility-immunity by listening to others, and their suggestions, until you can understand but not feel compelled to copy their ideas.