> What if someone proposes "we should rewrite X in Y language," Yes, if 50% of our development team is proficient in Y, X is a bottleneck or EOL, rewrite will

> What if someone proposes "we should rewrite X in Y language," Yes, if 50% of our development team is proficient in Y, X is a bottleneck or EOL, rewrite will solve significant problems. > we should use Z database instead. Yes, if Z is widely used in our stack, Z will realize advantages that cannot be achieved with the current database, Z is required to solve upcoming problems. That's how I take it, at least: You shouldn't say "No," you should say "this is why not."