I agree with the author, but especially because it's so rare to find people with expertise (a) also in the application, (b) also in the deployment target, and (

I agree with the author, but especially because it's so rare to find people with expertise (a) also in the application, (b) also in the deployment target, and (c) also in the deployment methodology, let alone in the specific instances your team uses (maybe you used GCP at a previous company, but that's of little help if your current company uses AWS), let alone getting multiple of such people on your team (because bus factor), really, the problem is a communication problem. Get separate developers, separate infrastructure engineers, separate release engineers - but focus first on the quality and quantity of their communication. Encourage pro-active communication, the earlier the better, and encourage open feedback.