Well, unless you're working on a project that must go into production, you don't really have to know the language/framework you're going to use in depth. In my experience I've learned a lot more by getting my hands dirty and for me it's better than trying to know everything before starting.
That's true. One can't possibly know everything about a language/framework before starting a project but I believe it is necessary to have a strong and deep knowledge of the language/framework in which the project is to be done.
Personally, I have stumbled while starting a project with half knowledge of the required language/framework and it usually leads to very bad code as well as design. One can surely learn a lot by getting their hands dirty and learn on the go but sometimes it is risky to make mistakes on certain project which are going to impact a lot of people due to broken or inadequate knowledge of the required language/framework.
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.
Well, unless you're working on a project that must go into production, you don't really have to know the language/framework you're going to use in depth. In my experience I've learned a lot more by getting my hands dirty and for me it's better than trying to know everything before starting.
That's true. One can't possibly know everything about a language/framework before starting a project but I believe it is necessary to have a strong and deep knowledge of the language/framework in which the project is to be done.
Personally, I have stumbled while starting a project with half knowledge of the required language/framework and it usually leads to very bad code as well as design. One can surely learn a lot by getting their hands dirty and learn on the go but sometimes it is risky to make mistakes on certain project which are going to impact a lot of people due to broken or inadequate knowledge of the required language/framework.