On the point 7. Starting on Big Projects Too Soon:
You also have the problem that in large projects, depending on the development practice, you only dive into developing requested features or bugfixes but you are unable to dive into topics like requirements engineering, product design, deployment and user support.
In smaller projects, in most cases the chances are that you need to do some deployment or you can influence to product design as well as talking to users directly. Imho this is a great benefit because you can see the big picture of the project and not only a small part.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great Tips !!
On the point 7. Starting on Big Projects Too Soon:
You also have the problem that in large projects, depending on the development practice, you only dive into developing requested features or bugfixes but you are unable to dive into topics like requirements engineering, product design, deployment and user support.
In smaller projects, in most cases the chances are that you need to do some deployment or you can influence to product design as well as talking to users directly. Imho this is a great benefit because you can see the big picture of the project and not only a small part.