A quick guide for when to study and when to build.
Weβre all consumers.
Consumers of products, consumers of services, and probably m...
For further actions, you may consider blocking this person and/or reporting abuse
Great post! This is a very common problem, especially with younger (in experience, not age) developers. If I may add a few little tidbits that I've seen really help with this:
As the OP mentioned, start with an MVP. But I see a lot of people fall into the trap of "I'll just add one extra thing". Do this half a dozen times and you've lost the spirit of the MVP. To help with this, write down exactly what the MVP will include before you start working. Once you've settled on that list, stick to it. If you have new ideas as you continue, that's awesome! write them down or add them as issues to your repo for a later iteration (never waste an idea!). By doing this up front, you have given yourself a clear target to shoot for. You know when you're done.
Only ever do 1 tutorial or video for a topic. After that, force yourself to rely on the documentation. This works great for me, and I have shared this with juniors I've worked with, and they've said it really helped them too. There is nothing wrong with doing a tutorial, or watching a video on a topic. It really helps to familiarize yourself with high level verbiage, concepts, and nuances of the tech. But after that, force yourself to get used to looking through documentation. This is where you will find quicker answers (rather than trying to remember what video or where in that 4 hours course you heard about that 1 thing), and deeper understanding of the tech.
If you find that you never finish the projects you start, fear not...you are not alone. There are many reasons why this might be, but let me share a few tips that have helped me and other I've shared them with:
Thanks for your article! I hope to read more soon!
Thanks for your detailed response, you've added many useful tips.
One of my favourites was around keeping projects small. I think sometimes when learners take on projects that are too big, it's very easy to get overwhelmed, get stuck on something and then quit. Keeping it small so that the task can be completed will drive confidence and motivation.
Cheers for this!
Agreed! Is very important to make every project, ours, that people see like our style, etc. Also, that helps to not be bored or overwhelmed. I like these tips too.
Amazing post! And direct to one of the biggest problems for self-taught, you think you are never ready or have not been enough. But in a world that is in constant change, you will never know anything. The better practice is working, making a team in a workspace, and learning from others.
Thank you π and yes that's exactly right!
Great post! π Could you share some community channels? π
Thanks π For communities I think being here on Dev.to is a great place to start because there are so many people and conversations to get involved in where you can talk to like-minded individuals. I would also recommend the freeCodeCamp community and Stack Overflow (for more technical support) and even Reddit can be a great place to engage and get support.
Hope that helps π
Amazing post. I am pivoting to start creating and this post was of immense value to me. Thank you
Thank you, I'm glad to hear this π
I love this entry. Such an eye-opener. Thanks.
Thank you, I wish you all the best π
That correct, i did as you say, when i am a student at university, i build 2 personal projects, but i feel alone, because nobody in my class did what i did, they usually following the course at university and it is very boring and not valuable, when i am a 3 years student i got a jobs and did not have much difficult to adap with real work. when i read your article, i rethinking about the time in college, i am did not know this tips, but lucky i am do right way :v, when i read the title of your article, i am thinking about you say about become a creator like blogger or something like that :v