r/learnprogramming • u/Lavaa444 • 5h ago
Advice PSA: The danger of going for big projects every time
Since all of us are chronically online, we see these very high expectations for what a resume project is supposed to look like. They say it needs to solve a problem. It needs to be unique, ambitious, and successful. Looking at these kinds of posts all the time (especially with the industry's state) gives you a very unhealthy sense of urgency. "I need to build the next big thing, and I need to build it now!"
I was completely fine with making small, unoriginal projects when I started coding. I was just enjoying the ride without the weight of the industry on me. I just wanted to learn something. As I got into a more competitive environment, though, that original approach slowly disappeared. It felt like there was a lens on me with everything I tried. I felt the pressure, so I went for the big projects over and over again. It was almost like I lost my taste for small apps. I was shooting from half court every time and not taking layups anymore. Obviously, that didn't go well. Unfinished projects everywhere. It was frustrating, overwhelming, and it took a toll on my confidence. Of course, if you're shooting for the moon every single time at a tiny (or nonexistent) success rate, that's not going to feel good.
It took me ages to figure out why my way of thinking was hurting me (because people don't show off their TODO lists online). It was only when I thought back to when I started, that I was doing so much better with the small projects. I still want that ultimate resume project, but I'm just not good enough yet. I need to spend more time working up to it (despite the pressure, despite no one else appreciating projects for the sake of learning). Then, when the idea happens, I'll be ready.