I want to lead an Angular + NodeJS project. As this is my first experience, I thought about using UML diagram as both designing/architecting the project and also the project's documentation.
But I am not sure if using UML diagrams is a good idea? I mean it takes longer time and many details that I don't know if is it necessary to writing them or not? I say this because in previous projects that we worked on, we were just talking about things we want and each member could do the task by his/her understanding, but at this time I decided to do the next project more organized with more developers, but don't know how much of detail or abstraction is enough and from where it's redundancy and not necessary?
I also though if I use UML diagrams in designing/architecting stage, we can also use this design as our project's documentation too and we won't read much documentations in the future, but I don't know if I think true or not?
I should mention we are a startup like company with 4-5 guys looking for extending up to 10 or more developers.