As for the aesthetics of the diagram itself
Posted: Thu Jan 23, 2025 5:46 am
We can argue about it forever. Aesthetics is nothing more than a matter of taste. Personally, I don’t see any point in discussing this parameter seriously. Conclusions Based on the examples described and their criticism, the following conclusions can be drawn: Always correlate your tools and work results with the goals you wanted to achieve. If you do not have a clearly defined goal, then, in principle, your work itself is not needed. It will be aimless work, i.e. "monkey work". If you have achieved the desired result with the help of the chosen tools, you can consider that you have done everything right.
As they say, winners are not judged. And any list of belgium whatsapp phone numbers mistakes from a formal point of view are not so important, the main thing is the result. Of course, it is necessary to study your mistakes, the formal side is also important for your own development. But you should not rely only on the formal side. The result is much more important. Diagrams are created to be passed on to other people, i.e. they can be considered a form of information transfer. And if the recipient of the information has understood everything correctly, then the diagram has fulfilled its function.
For example, if you work yourself and create a diagram for yourself, all errors from a formal point of view do not matter, the main thing is that you understand what and why you have drawn. If the diagram is passed on to a manager, programmer, other employees, it is important that it is read and understood unambiguously. Notation rules are very helpful in this, but it is not always necessary to limit yourself to one of the notations. The form of the diagram is important, it helps to understand better. The content is even more important.
As they say, winners are not judged. And any list of belgium whatsapp phone numbers mistakes from a formal point of view are not so important, the main thing is the result. Of course, it is necessary to study your mistakes, the formal side is also important for your own development. But you should not rely only on the formal side. The result is much more important. Diagrams are created to be passed on to other people, i.e. they can be considered a form of information transfer. And if the recipient of the information has understood everything correctly, then the diagram has fulfilled its function.
For example, if you work yourself and create a diagram for yourself, all errors from a formal point of view do not matter, the main thing is that you understand what and why you have drawn. If the diagram is passed on to a manager, programmer, other employees, it is important that it is read and understood unambiguously. Notation rules are very helpful in this, but it is not always necessary to limit yourself to one of the notations. The form of the diagram is important, it helps to understand better. The content is even more important.