They mean that code review within a team isn’t important ?!?

Anyone who can’t wait a few days for their code to be committed has an excessively high opinion of their own importance.

Must be the same people that think 35mph limit on a hard turn is an inconvenience during rainy nights.

No, it is not important to get something merged in 30 minutes, other than a revert of a bad change that broke everyone.

A pipeline build and test "proves" the change "technically correct"? What? At least that's the one place in the article where it's on the right track except for this remark.

good write-up