It all depends on what's the nature of your questions.
It is completely normal to look up specific steps of a program, technical details, or bugs you aren't able to trace yourself. Even if you do it every 2 minutes, it's OK, because the 10th time you will not need to google it (or, as i prefer, duckduckgo it).
But if your questions are broad, unspecific and the answer you look for is a tutorial that explains how to do the 75% of your project or more... Maybe you should go to simpler projects to practice algorithms and data structures until you are able to come up with more complex solutions on your own. Believe me, a good basis in data structures can improve the way you think and program a lot. Much more than knowing a lot of different technologies (which isn't bad, of course).
And when it comes to learn new technologies... unfortunatelly that depends a lot on existing documentation. I tried to learn some technologies that have very short and poor documentation and I usually end up giving up. But that's not your fault; if you are forced to learn by trial and error, the process is going to be slow, hard and frustrating, so it's only natural to leave it.
However, if the documentation is up to date and high quality, then read it while you practice. Go page by page testing everything you read. When you are done, you will have learnt enough to use it in any project you want, no matter if you have to re-read something again, the knowledge will be there, you will know what you need and where to search it.
I have a friendly rant on StackOverflow usage by unexperienced users in this post, I'll leave it here in case someone finds it interesting.
Good point and nice text! The docs should be my best friend while practicing. However I agree with you that some new technologies (mainly when it comes to OSS, which relies a lot on voluntary work) have short documentation. Fortunately I feel like this problem is mitigated as the community, and the software itself, grows.
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.
It all depends on what's the nature of your questions.
It is completely normal to look up specific steps of a program, technical details, or bugs you aren't able to trace yourself. Even if you do it every 2 minutes, it's OK, because the 10th time you will not need to google it (or, as i prefer, duckduckgo it).
But if your questions are broad, unspecific and the answer you look for is a tutorial that explains how to do the 75% of your project or more... Maybe you should go to simpler projects to practice algorithms and data structures until you are able to come up with more complex solutions on your own. Believe me, a good basis in data structures can improve the way you think and program a lot. Much more than knowing a lot of different technologies (which isn't bad, of course).
And when it comes to learn new technologies... unfortunatelly that depends a lot on existing documentation. I tried to learn some technologies that have very short and poor documentation and I usually end up giving up. But that's not your fault; if you are forced to learn by trial and error, the process is going to be slow, hard and frustrating, so it's only natural to leave it.
However, if the documentation is up to date and high quality, then read it while you practice. Go page by page testing everything you read. When you are done, you will have learnt enough to use it in any project you want, no matter if you have to re-read something again, the knowledge will be there, you will know what you need and where to search it.
I have a friendly rant on StackOverflow usage by unexperienced users in this post, I'll leave it here in case someone finds it interesting.
How to get answers on StackOverflow
MiguelMJ ・ Feb 6 ・ 5 min read
Good luck and keep it up Henrique.
Good point and nice text! The docs should be my best friend while practicing. However I agree with you that some new technologies (mainly when it comes to OSS, which relies a lot on voluntary work) have short documentation. Fortunately I feel like this problem is mitigated as the community, and the software itself, grows.