I'm going to guess you are typical college student age 18-22ish so I will throw out an opinion from someone double that age that you don't have a lot of experie

I'm going to guess you are typical college student age 18-22ish so I will throw out an opinion from someone double that age that you don't have a lot of experience yet to know what problems need solving. I would suggest sticking with things that are of interest to you. Or in web dev circles there are typical projects people use to demonstrate a language/framework: the to-do/task list and a blog. Idea list: - write a blog about writing a blog software, see its recursive kinda. You can't start out hosting this blog on your own software because your blog platform doesn't exist yet. - write a to-do/task list in each cool language/framework that was interesting to you. This could also apply to non-web languages - write one for mobile, on Windows/Mac, etc. - write software to track a scrum project, story points/estimates, burn down chart, velocity, etc. As much hate as Scrum gets, there are solid project mgmt principles in there and if you are learning this in school (or another PM framework) then writing software for it might help solidify what you learn - You could actually write a blog about your journey doing these things in your native language. A lot of the "tech" world's new stuff comes out of the US and the majority of people on Earth are non-English speakers. Reading thru translated API docs is probably not the best way to learn.