1. Do different but related when overwhelmed 2. You dont know what you don't know 3. Stop consuming too much contents 4. Slow learning process is normal
And... Save picking the cherries till you need a pick me up, attack the biggest problems first thing in the morning and if your boss is always giving you grief, save all the bad news for Friday afternoons, just before clocking off time. Gives them a couple of days to stew and get over it in their own time 😉 Most important, if your gonna complain about work, do it at work to you boss. No one else can help, it's not fair to your friends and family and it's not worth burning free time over.
Yes! When I am stuck on a problem and not making progress, the best thing I can do is walk away and take a break. I often figure out this type of problem in the shower the next day.
a year ago he posted ways to succeed as a self taught developer and now he posted this same topic again. Show's the competition is extremely tough lol XD
One of the most essential skills a software developer needs to learn is effective problem solving. Taking a complex problem and breaking it down into a set of smaller simpler problem, solving those simpler problems and then combing them together as a final solution for the initial complex problem. Basic problem solving and algorithm development were the first things we learned in computer science in university. No one wants to do this anymore, everyone thinks software development is just about writing code.
@@AfrocrimsonChronicleseven if you are not from computer science background, there are a lot of resources to learn from. Personally for me, Striver's system design worked like a charm. If you follow it properly, it is even better than paid courses.
you dont know what you dont know - this is so true. You never stop learning and the more you learn, the more you realise you don't know. More often than not, we stand on the shoulders of giants who have created things that we rely upon daily, so remember how ever hard we find things, someone has done something amazing so that we dont have to. And never give up, rather, keep on keeping on
"You dont know what you don't know" --> ironically learning more about a topic can make it feel like you know less, because you become aware just how much there still is to learn. That combined with "a slow learning process is normal" inevitably gives the feeling of being "behind", and there is no actual fix for that except to shift the mindset to looking back at what you've learned instead of looking in front at what you still want to learn.
This reminds me of my journey on learning guitar which has a lot of parallels when I started learning JS. In the beginning I learned a couple of chords and went straight into learning a song that was above my skill level. Got frustrated after couple of days and dropped the song and went to learn easier songs to the point that I didn't have to look at the guitar anymore. Went back to the original song and was much easier within a day because my rhythm, endurance, picking, chord switching improved so much by learning other songs.
Ironically one of the best things I did to improve and enjoy programming more is stop consuming youtube and IG. Not only because you waste time but also there's a lot of content creators hyping a ton of stuff and, of course not intentionally, making you feel overwhelmed with what you have to learn... No, you do not need to learn next 14 if you're comfortable with 13. Just build stuff and then once you start getting comfortable make the switch. Start learning something and actually stay focused on that, it doesn't matter that the new version is coming out in 3 weeks. Finish what you started and then either migrate or build something else.
Similar situation here! I also Started to Enjoy programming by Building my Favourite application (on smaller scale)! But I really enjoyed it so much. Nowadays I spend less time on RUclips tutorials (I only watch specific things) and more time reading documentation and important Concepts and Thinking about a problem I'm solving!
This is spot on. Especially the early stages of learning where what is called the the "Dunning-Kruger effect" will have people's cognitive bias, because of limited competence, to greatly overestimate their abilities. Then only later realize there is so much that they don't know and that there is still a lot to learn.
I'd say tip #2 was the most helpful for me. Yes programming is debugging, solving problems, etc. You need a roadmap though because as he said, "You don't know what you don't know." Having a guide speedruns your learning. Honestly just paying for a small course accelerated my learning. Wish I did it earlier.
I am so thankful for this video you made kyle. I'm a self-taught aspiring developer and everywhere i look online, people discourage me whether it be because of the untraditional route i'm taking or the harsh job market that we have. Your last pointer was most useful to me because i often get very discouraged comparing my journey to other people. I've been learning web development for a whole year already and its very easy to compare myself to other people's timelines.
@@ingeniousgoldie 24 for me actually. Just makes the feelings of "why don't I get this?" more intense. Web development has changed A LOT, and we just have to keep learning.
@@sarahwbs wow. You're right. I'm just focused on frontend, been at it for 3 years now and keep seeing new stacks to learn. Each job posting asking for a little extra than what I already know. It's so frustrating. And to think I haven't even touched backend yet 😓
What has always helped me is to work on another project. Often, this approach has led to new ideas for solving my current problem. Then, I return to my original project and continue working on it.
is it a good idea to look for someone's code and analyze it, then use it if you think that code suit on what you are making? cause I'm trying to learn and can't even think what source I'll going to use for a project
@@richiemanalansang3865if you think this code suits you, yeah it might be a good idea to study this code and think how to use it in your project. but I more often use my own code.
5:02 That's exactly what happend to me. I tackled promises and the whole concept of event loop in May for the first time and at that time it was extremely difficult and I just couldn't wrap my head around it. Through pain and effort I eventually learned these concepts but they still didn't quite make complete sense to me and I was wondering what's the point of this complicated syntax. I decided to tackle promises and the event loop once again a few days ago and literally, in the course of one day, it finally clicked. Not only I relearned these concepts again but also found many holes in my knowledge that I just didn't realize at the time. Now it all seems so easy and obvious. That's a really great advice from this video.
Thank you for sharing one of the best suggestions for developers. I've also noticed that sometimes I get stuck in the middle of my project and spend a lot of time feeling disappointed, which leads me to start learning something new. However, after a few months, when I restart the project, the previous issue is resolved comfortably.
I wish I can like this video twice. It's exactly what I needed to hear cause I am burning myself out right now. Thanks for all the amazing comments too, it's really insightful. I will keep learning and practising, giving up is not an option.
It's a pleasure to see such videos once in a while. One small suggestion: it seems like your camera is in auto mode, which constantly changes the exposure and can be annoying. It's better to keep it in manual mode for consistent lighting. Anyway, keep going. Love your content!
6 months is nothing man, it should take atleast 6 months to somewhat master flexbox and html. Ie. replicating a Figma file to HTML and CSS. Another 6 months for JS and React and probably another 6 months for TS, Nextjs, API calls.
I gave up on programming after going through a 6 month bootcamp that "guaranteed" a job after completion, little did I know it was a lot more intense than I anticipated, and the job market wasn't nearly as good as I had expected and no one even looked in my general direction, a lot of the information out there is very misleading, and I wish I approached it with a slower pace and true interest rather than expecting to get a job quickly
Well, I am actually behind everyone because I was bogged down for so long. I don't let that deter me though. I've gotten good at looking towards completing the next small goal rather than focusing on being at 5% of the project as a whole.
Just as it's hard to know what you don't know, it's hard to know if you've watched too many videos or not enough. I'd say a good thing to try is coming up with an idea for a simple app to set yourself a goal, then psudocode it out as much as you can (write out how it works in detail in english) and now you've just written yourself what you can interpret as a list of what's required to make it. *Then* you know what to look up tutorials for, and having a concrete purpose for putting the code in helps you learn it a lot better. It's hard for things you learn to stick when it's abstract and purposeless
Something I learned later than I'd hope... 9 times out of 10 when you hit a wall it's because you missed something obvious, likely because you need a break. Explaining the problem to someone else, if you can't figure it out in 15 minutes will save you massive amounts of time, hair and brain cells... coz if it is something obvious and you ask for help someone else will spot it straight away... and likely embarrass you about it 🙄 missing the obvious is the first place to look...
I was doing well with just Html, css and Js and I was building some projects. Then I decided to learn React and I just got frustrated, still frustrated but pushing
React has actually been such a relief from me coming from the basics. What I did is jumped straight into Next.js following some huge 12h+ tutorials (you can find plenty on YT). Just coded along, not really understanding but the more I did, the more I understood and when I finished a tutorial I would try to change or implement features myself. Hope this can help!
@@sw33tialucard I have found great ones on Udemy (I think Angela was her name - the one I followed the most). I haven't tried Web Dev Simplified yet but I love his channel so you might want to check it out too!
I really enjoy being a self taught developer... but I really do struggle with high complexity. I get lost in all the moving pieces. I managed to build a program to tune my engine but it's really at the edge of my skills.
Also we need tutorial for HTTP the protocol not the api in js When i understand the protocol and request-response it really helped me well on understanding the api like expressjs or any api in go or php its become so easy
If you're like me and you're teaching yourself how to code: KEEP GOING! Or if you quit, I guess it's one less candidate I have to beat out to get my first job :)
I wish he will address what AI will do to web development jobs. I want to quit because I'm afraid after putting in all these years and effort, AI will just straight up do a better job. Because it's a machine! It can read all prog language textbooks in minutes and start teaching stuff that took me months to perfect. And those who say AI is not that good yet, I'm surprised you find any comfort in that statement because these models are being fine-tuned at an alarming rate. I hope we won't be left hanging out, trying to find another career suddenly, after all this effort.
I was actually working on an auth systegm and couldn't implement it or found a tutorial on the internet but the problem is auth is fundamental i can't escape it And when you ask someone you are an actual imposter for him and he won't answer you
I feel so stupid reading docs. I can't currently do it. There are so many words used to describe what can be done and how... I feel like, it's not even English. But give plenty examples, I u derstand the limited usage I need.
Web was so easy but now the learning curve so high😢 especially for full stack dev . God help us 😂. Also i want your advice on nextjs it has very high learning curve i feel
@@yaqubnaqiyev131 you want to be on a structured environment. Wearing one hat at the time. Startups usually has fewer developers which means you'll end up doing unrelated things through a week which I don't consider ideal if you want to cement and get deep knowledge. A colleague of mine in a different company is already a midlevel backend developer while I'm only trying to survive at this point
I worked both in a startup and product based company. Learning in a startup is 200 percent more than in a product based company . You get work on limited things at a slower speed in a product based company
@@heisenbergsk21 sure that would be true for some people but I hardly believe most of us on our first job have the capacity to actually learn when you're doing 200% more. I would say that it gives you experience on how to solve problems but not necessarily expertise on how to properly do it. I think this might make a good video in fact. Interviewing junior at their first job from both kind of companies. Jack of all trades, master of none.
You can avoid Dunning Kruger effect if you start learning programing with c++. Then even after a month you won't be able to do shit and will cry each day trying to find that missing semicolon.
With AI you don’t need to code anymore 😄, or use cheaper outsourcing. You pay for AI agents todo it for yo 🚀, don’t need to dive into dozen of courses 😄. You should see every day dozen of courses to get analyzed and at the end you realize you know 0
1. Do different but related when overwhelmed
2. You dont know what you don't know
3. Stop consuming too much contents
4. Slow learning process is normal
And... Save picking the cherries till you need a pick me up, attack the biggest problems first thing in the morning and if your boss is always giving you grief, save all the bad news for Friday afternoons, just before clocking off time. Gives them a couple of days to stew and get over it in their own time 😉
Most important, if your gonna complain about work, do it at work to you boss. No one else can help, it's not fair to your friends and family and it's not worth burning free time over.
Yes! When I am stuck on a problem and not making progress, the best thing I can do is walk away and take a break. I often figure out this type of problem in the shower the next day.
a year ago he posted ways to succeed as a self taught developer and now he posted this same topic again. Show's the competition is extremely tough lol XD
@@eggxecution if he didn't post it again i wouldn't have seen it, so get your head straight.
One of the most essential skills a software developer needs to learn is effective problem solving. Taking a complex problem and breaking it down into a set of smaller simpler problem, solving those simpler problems and then combing them together as a final solution for the initial complex problem. Basic problem solving and algorithm development were the first things we learned in computer science in university. No one wants to do this anymore, everyone thinks software development is just about writing code.
Also in web understand the HTTP the protocol the system design of it not the api on any programming language jumping to the api well overwhelm u😅
@@NaifIT11how do one learn this, especially if someone is not from a computer science background
In your opinion what’s the best way to learn this. Leetcode or something else?
@@AfrocrimsonChronicleseven if you are not from computer science background, there are a lot of resources to learn from.
Personally for me, Striver's system design worked like a charm.
If you follow it properly, it is even better than paid courses.
Absolutely true. This is usually one of the things that most self taught developers overlook but focus on coding.
you dont know what you dont know - this is so true.
You never stop learning and the more you learn, the more you realise you don't know. More often than not, we stand on the shoulders of giants who have created things that we rely upon daily, so remember how ever hard we find things, someone has done something amazing so that we dont have to.
And never give up, rather, keep on keeping on
"You dont know what you don't know" --> ironically learning more about a topic can make it feel like you know less, because you become aware just how much there still is to learn. That combined with "a slow learning process is normal" inevitably gives the feeling of being "behind", and there is no actual fix for that except to shift the mindset to looking back at what you've learned instead of looking in front at what you still want to learn.
This reminds me of my journey on learning guitar which has a lot of parallels when I started learning JS. In the beginning I learned a couple of chords and went straight into learning a song that was above my skill level. Got frustrated after couple of days and dropped the song and went to learn easier songs to the point that I didn't have to look at the guitar anymore. Went back to the original song and was much easier within a day because my rhythm, endurance, picking, chord switching improved so much by learning other songs.
I learn the guitar too
hands down Kyle is the most genuine and sincere guy, who actually deeply cares about your learning
Ironically one of the best things I did to improve and enjoy programming more is stop consuming youtube and IG. Not only because you waste time but also there's a lot of content creators hyping a ton of stuff and, of course not intentionally, making you feel overwhelmed with what you have to learn... No, you do not need to learn next 14 if you're comfortable with 13. Just build stuff and then once you start getting comfortable make the switch. Start learning something and actually stay focused on that, it doesn't matter that the new version is coming out in 3 weeks. Finish what you started and then either migrate or build something else.
Similar situation here! I also Started to Enjoy programming by Building my Favourite application (on smaller scale)! But I really enjoyed it so much. Nowadays I spend less time on RUclips tutorials (I only watch specific things) and more time reading documentation and important Concepts and Thinking about a problem I'm solving!
This is spot on. Especially the early stages of learning where what is called the the "Dunning-Kruger effect" will have people's cognitive bias, because of limited competence, to greatly overestimate their abilities. Then only later realize there is so much that they don't know and that there is still a lot to learn.
I'd say tip #2 was the most helpful for me.
Yes programming is debugging, solving problems, etc. You need a roadmap though because as he said, "You don't know what you don't know." Having a guide speedruns your learning. Honestly just paying for a small course accelerated my learning. Wish I did it earlier.
I am so thankful for this video you made kyle. I'm a self-taught aspiring developer and everywhere i look online, people discourage me whether it be because of the untraditional route i'm taking or the harsh job market that we have. Your last pointer was most useful to me because i often get very discouraged comparing my journey to other people. I've been learning web development for a whole year already and its very easy to compare myself to other people's timelines.
The first minute summed up my emotions on a daily basis over the last 20 years.
SAME
20 years?!
@@ingeniousgoldie 24 for me actually. Just makes the feelings of "why don't I get this?" more intense. Web development has changed A LOT, and we just have to keep learning.
@@sarahwbs wow. You're right. I'm just focused on frontend, been at it for 3 years now and keep seeing new stacks to learn. Each job posting asking for a little extra than what I already know. It's so frustrating. And to think I haven't even touched backend yet 😓
These advice are really valuable, thanks!❤
Kyle is back!
Coming down from all that complicated stuff.
You are the man.
you are the true legand , you have said my 1 year journey in less than one min
What has always helped me is to work on another project. Often, this approach has led to new ideas for solving my current problem. Then, I return to my original project and continue working on it.
is it a good idea to look for someone's code and analyze it, then use it if you think that code suit on what you are making? cause I'm trying to learn and can't even think what source I'll going to use for a project
@@richiemanalansang3865if you think this code suits you, yeah it might be a good idea to study this code and think how to use it in your project. but I more often use my own code.
Mr Kyle is truly inspiring.
Beautiful. Interesting piece
5:02 That's exactly what happend to me. I tackled promises and the whole concept of event loop in May for the first time and at that time it was extremely difficult and I just couldn't wrap my head around it. Through pain and effort I eventually learned these concepts but they still didn't quite make complete sense to me and I was wondering what's the point of this complicated syntax. I decided to tackle promises and the event loop once again a few days ago and literally, in the course of one day, it finally clicked. Not only I relearned these concepts again but also found many holes in my knowledge that I just didn't realize at the time. Now it all seems so easy and obvious. That's a really great advice from this video.
Thank you for sharing one of the best suggestions for developers. I've also noticed that sometimes I get stuck in the middle of my project and spend a lot of time feeling disappointed, which leads me to start learning something new. However, after a few months, when I restart the project, the previous issue is resolved comfortably.
I wish I can like this video twice.
It's exactly what I needed to hear cause I am burning myself out right now.
Thanks for all the amazing comments too, it's really insightful.
I will keep learning and practising, giving up is not an option.
It's one of the very best videos that I have ever seen produced by a tech RUclipsr. Solid advices 👌
It's a pleasure to see such videos once in a while.
One small suggestion: it seems like your camera is in auto mode, which constantly changes the exposure and can be annoying. It's better to keep it in manual mode for consistent lighting. Anyway, keep going. Love your content!
I was losing hope and was so demotivated this morning, glad that this appeared in my YT feed. I'm so grateful. Thenks Kyle :)
Bro, you just summed up my journey very well! That's exactly it!
Forte abraço do Brasil!
God bless you!
Thank you Kyle, this was really helpful
Thank you for the tips, Kyle!
Thank you very much for the effort you put on those. I wish you all the success!
I think working in a team with others is a great way to learn new stuff.
The skit in the first part was way too relatable 😭
100% actually 😂😂
Yup, I was going to crack Google interview in 1 month of learning html css😂😂😂
@@AdityaRaut-l6p 🤣🤣
Thanks kyle . ❤❤❤
Wish you luck 😎😎😎
As usual Kyle is one of the best RUclipsrs who teach front end development
Thank you so much!
It's a great compliment.
The beginning of the video is painfully relatable lol
I needed this thanks a lot
I am at 6 month mark, and super annoyed at my ability to code. Can't complete any project I start. You have been a godsend.
6 months is nothing man, it should take atleast 6 months to somewhat master flexbox and html. Ie. replicating a Figma file to HTML and CSS. Another 6 months for JS and React and probably another 6 months for TS, Nextjs, API calls.
If you struggle with HTML and CSS, Webflow is a great tool to learn it faster.
In general also, taking a step back can be very good. In chess you sometimes get up for a few minutes to come back and reexamine the situation.
Kyle has nice hair; Kyle is handsome, Kyle is a good teacher; and Kyle listens to Led Zeppelin as well.
I gave up on programming after going through a 6 month bootcamp that "guaranteed" a job after completion, little did I know it was a lot more intense than I anticipated, and the job market wasn't nearly as good as I had expected and no one even looked in my general direction, a lot of the information out there is very misleading, and I wish I approached it with a slower pace and true interest rather than expecting to get a job quickly
This came at the right time ❤
Well, I am actually behind everyone because I was bogged down for so long. I don't let that deter me though. I've gotten good at looking towards completing the next small goal rather than focusing on being at 5% of the project as a whole.
Thank you that good tips❤😊
do some side tasks and unlock new skills or level up existing skills
then back to the main task and see if it's easier
Just as it's hard to know what you don't know, it's hard to know if you've watched too many videos or not enough. I'd say a good thing to try is coming up with an idea for a simple app to set yourself a goal, then psudocode it out as much as you can (write out how it works in detail in english) and now you've just written yourself what you can interpret as a list of what's required to make it. *Then* you know what to look up tutorials for, and having a concrete purpose for putting the code in helps you learn it a lot better. It's hard for things you learn to stick when it's abstract and purposeless
That is what I do when I started learning programming now I can now build something on my own in c, js, c#
Thanks Kyle
Yes yes yes yes the advice number 4 is important and i really want to hear it. Big ❤ to u
Great advice.
Thank you very much for your video
Thank you bro.
Thanks WDS!
This actually works. 🙌
Thanks bro
Something I learned later than I'd hope... 9 times out of 10 when you hit a wall it's because you missed something obvious, likely because you need a break. Explaining the problem to someone else, if you can't figure it out in 15 minutes will save you massive amounts of time, hair and brain cells... coz if it is something obvious and you ask for help someone else will spot it straight away... and likely embarrass you about it 🙄 missing the obvious is the first place to look...
The key to getting better is to practice☑
I was doing well with just Html, css and Js and I was building some projects. Then I decided to learn React and I just got frustrated, still frustrated but pushing
React is a good start. You can find many paid tutorials that can help you with it.
React has actually been such a relief from me coming from the basics. What I did is jumped straight into Next.js following some huge 12h+ tutorials (you can find plenty on YT). Just coded along, not really understanding but the more I did, the more I understood and when I finished a tutorial I would try to change or implement features myself. Hope this can help!
@@Hari983 could you recommend any? Thank you
@@sw33tialucard I have found great ones on Udemy (I think Angela was her name - the one I followed the most). I haven't tried Web Dev Simplified yet but I love his channel so you might want to check it out too!
Thank you
PERFECT!!!!)) XD Thanks for the video
I really enjoy being a self taught developer... but I really do struggle with high complexity. I get lost in all the moving pieces. I managed to build a program to tune my engine but it's really at the edge of my skills.
I have an odd question. Should developer be a fast keyboard typer?
So tru, stuck in tutorial videos
There is a typo in the Frontend Roadmap:
In the Meta Framework section, Next.js is listed in the Vue category instead of Nuxt.js.
Ty, Kyle, you are the best )
Learning Programming from Garou of One Punch man. something i didn't know i need in my life
Also we need tutorial for HTTP the protocol not the api in js
When i understand the protocol and request-response it really helped me well on understanding the api like expressjs or any api in go or php its become so easy
Amazing ❤ video
If you're like me and you're teaching yourself how to code:
KEEP GOING! Or if you quit, I guess it's one less candidate I have to beat out to get my first job :)
I wish he will address what AI will do to web development jobs. I want to quit because I'm afraid after putting in all these years and effort, AI will just straight up do a better job. Because it's a machine! It can read all prog language textbooks in minutes and start teaching stuff that took me months to perfect.
And those who say AI is not that good yet, I'm surprised you find any comfort in that statement because these models are being fine-tuned at an alarming rate.
I hope we won't be left hanging out, trying to find another career suddenly, after all this effort.
this is facts, same thing happened to me and i went to other tech stack
I'm not a self taught developer, but thanks for the tips!
I was actually working on an auth systegm and couldn't implement it or found a tutorial on the internet but the problem is auth is fundamental i can't escape it
And when you ask someone you are an actual imposter for him and he won't answer you
1 year: just read the docs bro
I feel so stupid reading docs. I can't currently do it. There are so many words used to describe what can be done and how... I feel like, it's not even English.
But give plenty examples, I u derstand the limited usage I need.
Dunning-Kruger Effect^*
nice led zeppelin shirt!
Coding like writing more practice more getting better
Unrelated comment .. Kyle, guitar stands are $15, please buy another one : )
Nice shirt 👍
I did follow that path but without the tutorial path I only watched them when I was really stuck
this isn't about programming, it's about any skill based knowledge
Web was so easy but now the learning curve so high😢 especially for full stack dev . God help us 😂. Also i want your advice on nextjs it has very high learning curve i feel
But I think it's a advantage for u if you learn more you will make the best things and you will be more valuable
+1 for the Led Zeppelin t-shirt 😉
thats exactly me bro
Very good information, but the popups ruins the video.
Guitar play/tutorial when?
Im 3 years in and i feel i too lazy and slow. I wish i was disciplined, i am SURE i would be a pro in 1 year
9 month sabbatical from JS 😂 and going strong 💪
bro you need to apply for the boss role in sonic movie
Wait you guys felt powerful, gets a bad flashback
Data structures and algorithms makes me want to quit web dev. Big o notation etc is so confusing to me.
I want to learn web development from scratch
It's so weird how point 1 works
The fact of web development is learn and learn a...........
learning any like programe
piece of advise to you trying to find your first job. AVOID startups. You're welcome!
why?
@@yaqubnaqiyev131 you want to be on a structured environment. Wearing one hat at the time.
Startups usually has fewer developers which means you'll end up doing unrelated things through a week which I don't consider ideal if you want to cement and get deep knowledge.
A colleague of mine in a different company is already a midlevel backend developer while I'm only trying to survive at this point
Noted
I worked both in a startup and product based company. Learning in a startup is 200 percent more than in a product based company . You get work on limited things at a slower speed in a product based company
@@heisenbergsk21 sure that would be true for some people but I hardly believe most of us on our first job have the capacity to actually learn when you're doing 200% more.
I would say that it gives you experience on how to solve problems but not necessarily expertise on how to properly do it.
I think this might make a good video in fact. Interviewing junior at their first job from both kind of companies.
Jack of all trades, master of none.
You can avoid Dunning Kruger effect if you start learning programing with c++.
Then even after a month you won't be able to do shit and will cry each day trying to find that missing semicolon.
Tutorial Hell they call it...
With AI you don’t need to code anymore 😄, or use cheaper outsourcing. You pay for AI agents todo it for yo 🚀, don’t need to dive into dozen of courses 😄. You should see every day dozen of courses to get analyzed and at the end you realize you know 0
It‘s all about tutorial hell ☠️
😂ahmm on these phase
😂😂😂 1 month developer says am gonna build facebook next 😅😅😅
Wow if you’re te one watching tutorial after tutorial without implementation than indeed you’re wasting your time!!