Instead of booking repetitive meetings, establish these solid communication practices in your software project.
💎 Well-written commit messages telling *why* you made *that* change. Use the Conventional Commits spec.
💎 Functional tests describing how you intend your functions, classes, and interfaces to be used.
A common denominator for the above is that they are included in the version control. No Confluence or external wiki sites, no messy email threads, and no digging up information from Slack messages. Only plain text files preferably formatted as Markdown.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!