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.
💎 Architectural Decision Records (ADRs) for proposing and explaining significant changes to the architecture.
💎 ARCHITECTURE.md file for a birds-eye view of your technical solution.
💎 README.md file for efficiently onboarding new team members.
💎 CONTRIBUTING.md file and a Code of Conduct for making your open-source work inclusive and enjoyable for contributors.
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!