3 ms·

I think it all comes down to having an understanding of your organization’s persistent data. You need to have a culture where people are allowed to become fami

I think it all comes down to having an understanding of your organization’s persistent data. You need to have a culture where people are allowed to become familiar with what is in their files and databases, and make sure they pass that knowledge on to others. Ideally in writing, but make sure it happens. Too many developers assign more meaning to this year’s code than is really justified.

java-man 7y ago
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.