Infra-office (ie in person) for the high bandwidth interfaces, usually the whole team is in the same office.
Inter-office for lower bandwidth interfaces, ie between teams and functions.
You definitely have some interactions that are effectively remote, say if your project involves working closely with $remote_team, but in general the highest-order terms in the equation should be in office, if you are doing a traditional WFO org.
This is baked into Git at the core, but just like many other cases, GitHub subverts the intent of fundamental expectations about the way Git is supposed to be used and actively goes out of its way to make it difficult if you're interacting with the project through GitHub instead of local tools. (In fact, for new GitHub accounts, it even defaults to obscuring users' contact info, and it attributes all changes made through the web UI to an opaque @github.com email address. You have to deliberately go into the settings to turn this off, without ever getting a notification that that's what GitHub is doing.)
Have you tried turning on voice control? That allows you to control the entire screen without holding phone (“show numbers”, “Tap 5”, “Tap 4”, “Text I want to enter”, “Tap send”)
CDK is significantly more comprehensible than CloudFormation. Particularly: it has patterns and convenciones baked in that let a few lines of code translate into 100s of lines of CloudFormation