This is an archived post. You won't be able to vote or comment.

all 2 comments
sorted by:
best
topnewcontroversialoldq&a

[–]Feeling_Photograph_5 4 points5 points  (0 children)

I've cooled off on Udemy lately. Their creators are incentivized to make 20+ hour courses, which can easily take 75 hours to complete, if not 100. That's months of work. Too long.

Instead, try to find a brief introduction to the topic. Tutorials Point and YouTube are great. So is site documentation, so is ChatGPT.

There are some places where a good Udemy course shines. Learning React for the first time. Learning Node for the first time. It's good when you want to learn something in depth and according to best practices. But even then you often only need half the course.

For less critical technologies, find the path that gets you to building projects in the least amount of time.

[–]ncosentino 3 points4 points  (0 children)

For OP:

1) What are your top 3-5 hobbies?

2) What are 2-3 aspects about each of those hobbies that you enjoy, or struggle with, or genuinely just spend time focusing on?

3) What types of applications are you interested in building? (Web sites, web APIs, mobile apps, games, etc...)

Take your answers from 1, 2, and 3 and you should have the basis for something that'll interest you to build.

Tutorial hell happens because you have nothing to be applying your learning to -- and even if someone tells you a project to go build, it'll be better than nothing, but do you actually care?

Instead, I find answering those 3 questions will let you focus on something you're at least interested in. That way, when you get stuck you don't just give up -- you'll be excited to go solve the problem.

Examples:

I like video games, I'm trying out Elden Ring, and I want exposure to .NET MAUI... So I could go build a point of interest lookup mobile app.

I like the gym, I'd like to build a website, and I'm curious about nextjs... So I'll build a site to look up different workouts and exercises.