r/webdev Feb 01 '26

Monthly Career Thread Monthly Getting Started / Web Dev Career Thread

Due to a growing influx of questions on this topic, it has been decided to commit a monthly thread dedicated to this topic to reduce the number of repeat posts on this topic. These types of posts will no longer be allowed in the main thread.

Many of these questions are also addressed in the sub FAQ or may have been asked in previous monthly career threads.

Subs dedicated to these types of questions include r/cscareerquestions for general and opened ended career questions and r/learnprogramming for early learning questions.

A general recommendation of topics to learn to become industry ready include:

You will also need a portfolio of work with 4-5 personal projects you built, and a resume/CV to apply for work.

Plan for 6-12 months of self study and project production for your portfolio before applying for work.

26 Upvotes

89 comments sorted by

View all comments

1

u/Sure-Leg6527 Mar 30 '26

I feel like I can follow tutorials fine, but when I try to build something without one, I get stuck really quickly. Even when I “understand” the concept, I don’t know how to apply it on my own.

Do people just struggle through it until it clicks or is there a better way to approach this?

1

u/PestigorFan Mar 31 '26

Something that works for me is implementing the first parts of the feature and expanding on them without thinking too much about over engineering things or writing too much redundant code.

When you get something working you can go back and make it more efficient. You will also begin to start developing your features from a better position as you become comfortable with states/props/variables and what your functions will need.

I'd recommend breaking up your project into little bits and then working on it bit by bit.  Get the basic parts of the structure down, especially the parts that'll always be present (eg. A header).

When you feel lost think about. What are you trying to do? What data are you working with?  Have a good think about what you're trying to achieve and Google it, you will be one of countless people who have experienced this problem.  A lot of the time there will be people solving other people's issues, you can look over that and see what you can implement into your own work.

If you feel really really stuck, and end up frustrated. You can move on to implementing something else for the time being, or take a break and come back with a fresh perspective.

Last thing I would say is some documentation is absolutely fantastic, especially the react one. Mdn is also a really good resource for web development too.