You are right, but the "culture" has to be backed up with tools and processes. We can't rely on oral folklore to communicate the requirement and business decis

You are right, but the "culture" has to be backed up with tools and processes. We can't rely on oral folklore to communicate the requirement and business decisions. People leave the company all the time, assumptions and requirements change. We need a git repo for requirements and business decisions, with pull requests and approvals, integrated with the main code repo.