Project lead code

I present some of the documentation to the developers in English, and some in Russian. There are many guys who study 2+ languages, and it’s convenient for me to mentor them this way.
When I create the basis (devops) for a future product, I first design models and business flows, only after that the stack and IT architecture. This is what it looks like in reality (rus):

• A data flow diagram is a set of entities and relationships (Java). A little simpler than the Database
• When the diagram is seen by coders and business customers, everyone should interpret what is happening in the diagram in the same way
• I draw diagrams in open sources such as Draw.io/Paint. It's funny, but the simpler the better for the project
• The names of objects should be intuitive for users; no one needs complexities like in mobile applications
• It's better to do the scheme by one person. This is responsible, but it's better to lead the code alone than in a group. Easy to mislead

1. ER-diagrams are compiled based on a data model, which is also drawn by the software architect. They often resort to the help of analysts in the company, especially when it comes to API/Kafka/others.
   I believe this is unnecessary if the project manager is competent to understand the business problem and convey it independently to the team. Businesses trust direct collaboration more than giant teams with unnecessary participants. NAGI

2. Large teams love Scrum/Kanban. But these are all also tricks of marketers, because it's faster to gather not according to the sprint schedule, but according to necessity and desire. FTW
   There is an expression “The best meeting is the one that never happened”. I recommend not to waste extra time on calls when you can devote yourself to design/coding and creativity.