There's a lot of talk here about Meeting time vs. Project time or Manager schedule vs Programmer schedule ( with good reason, given PGs take on it )
What I have seen is that teams will need to find their own cadence for sync points given their familiarity with collaboration tools and the particular work they have.
There is a story about marines in training that goes something like this: At first as they move through unfamiliar territory, they talk all the time. They call out things they see, the call out directions to look and walk, but as they become cohesive they become silent.
Build a "basic training" environment for yourselves. Learn Git completely if that's your toolset. Grok something excellent together [ jira, AWS, Gitlab], and do it in the context of some voice/video chat tool. Zoom or teams or discord or slack, and explore how to track the things you are doing in the conversation you are having. Zoom and Teams ( depending on what else you use ) have chat and app integrations to keep your workflow documented in your conversation. Share you screens to see exactly what you're looking at together, share control of someone's computer to teach, annotate on a code review. Etc.
Explain that this is contextualized exploration. Meet more than you want to and then cancel meetings down to the cadence that works for you.
You may want to meet twice a day if you're tackling smaller chunks of tickets/backlog or have devs newer to the project, or once a day may be a burden.
Set agendas ( or hire a scrum master or similar, even better ) to keep your sync points productive, establish your next period of work and get back to the good stuff.
Keep documentation of your meeting notes in a Teams channel / slack channel / Zoom team chat and check back on it.