@letsgotosleep1988
I'm 27 years old, working a dead-end call center job. It’s 5:08 AM, and I spend 4-6 hours of my 10.5-hour shift studying coding. I’m about 6 months into this journey, and I’m locked in—barely talk to people at work, not because I’m cool, but because I’m focused. I’m desperate for a better future and to break out of this rat race. I watch most of my colleagues complain about this job, but unfortunately, many aren’t doing much to change it. I’m not better than anyone—I’m just incredibly grateful that I’ve found something I love. I’ve become obsessed with learning and I’m thankful for this job because it gives me the time to study. My goal is to break into tech before I marry my beautiful fiancée! Let’s keep going!
@kpdude96
4:53:00 For those who wondered why the catch block didn't work, fetch only rejects when a network error occurs. Since responses aren't network errors, there is nothing to catch. You have to check the "ok" property in the response object and need to throw an error yourself with throw new Error("Meaningful Message").
@suupershihab
I know React already but just here to support Anson. I know it'll be a good watch and refresher. Keep up the good work, bro!
@drift-l2o
This must be one of the most amazing tutorials I've ever watched - with crystal clear explanation. Thank you so much for your enormous effort! 🙏
@dennym9213
Brilliant, I had no experience in react before. And now I'm pretty much solid with basics.
@christophermawela3318
Have already crossed 7 hr mark, this is a great tutorial and looking forward to your React projects. Thank you Anson...
@viridianite
Thanks a lot, dude! You're not only explaining syntax but also concepts, patterns, practices, and motivations. That's what makes a good programming tutorial. 4:53:00 From the fetch docs, "A fetch() promise only rejects when the request fails, for example, because of a badly-formed request URL or a network error. A fetch() promise does not reject if the server responds with HTTP status codes that indicate errors (404, 504, etc.)." After you changed the API endpoint to a non-existent one, you got a 404 error from the server which resolves and that explains why you couldn't catch it.
@bhagyawijenayake
I'm at 04:11:22. This is the best React course I have found.
@JayaramRaju-7799
Just I watched 1hr of video and it is completely different from others. Everything is explained clearly while compared to others.Thanks sir
@godwinoyale3550
1hr into the course and all I can say is that you are one of the best teachers on this app
@Joe-gy6ld
been searching for a while to get the course that first explains why and where you'd use the code your getting taught and finally found it. I appreciate you Anson. Thanks!
@MrPSolver
Great tutorial, I appreciate how thorough you were with each concept! Thanks man :)
@tarekmohamedwfa7354
Great content! Can't wait for your NextJS course
@mykun8737
Anson, you're my idol, my guiding spirit. Could you teach a full video course on HTML, CSS, and JavaScript for backend devs? I've been assigned some frontend tasks, but unfortunately, I only have prior knowledge of backend development. HTML, CSS, and JavaScript are completely new to me; I'm at ground zero. Your help would be greatly appreciated.
@roadMapLearner
I am a beginner learning react.I never understood useState concepts. But your video is super explanatory and i understood it clearly now. I dont think i found any udemy courses explaining this concept clearly
@Bad4Good2
Excellent tutorial man, thanks for doing this for us.
@KuchOriemi
This guy is great and explains so well, great content thank you 👍
@jopadjr
3.1k... Thanks Anson. This is a great video. I have just started the video and need to find out about other frameworks as well.
@therealvanny_404
Guy, I'm really love of your teaching man because your explanation is so clearly. Much appreciate man and Keep it up!
@ansonthedev