PSA: The danger of going for big projects every time
Posted by Lavaa444@reddit | learnprogramming | View on Reddit | 19 comments
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.
ajamdonut@reddit
Just finish a big one then its not a problem. I have a stack of enormous projects, some 15 years old. Some ongoing right now. Our latest one took 2 years and is now paying our grocery bills...
So, yeah, nice advice to start small... But don't ignore big... Big is where you learn real project structure, headaches, bugs, issues. A big unfinished project with lots of insane arms and legs - looks better to me - than some simple todo app i've seen a tutorial for 100 times on github.
parazoid77@reddit
You shouldn't be judging projects on their entertainment value to you though, you should be looking for markers of quality, or evidence of learning. One huge mess of a project is worse than multiple smaller, working projects as the smaller ones show a person is able to create value. There's a reason todo apps are popular, because people still use todo apps today. Jumping into a deep pool is not the same as being able to swim in it...
And with the existence of AI, you can no longer assume a large project has required any more effort than looking up ideas.
ajamdonut@reddit
I just disagree. Literally my big messy projects have made people directly give me job offers. From the creators of the libraries I use themselves.
JandersOf86@reddit
I appreciate your take on this. You dont have to be specific about your project but what kinds of loose ends did you have that still got you a job? Im working on somethong right now that is pretty monumental compared to what I've published on my github in the past and have quite a bit of loose ends to tie up.
ajamdonut@reddit
In my case it was often smaller parts of the bigger projects that got me noticed. (so it does track that a big project isn't necessarily the important part). For example the rendering library had no tutorials on making light systems. So when I made mine, I posted it in the discord, forums etc. This continued as I continued my project - until the library developers invited me to interview.
The point isn't really the big project is good.. It's just that small projects don't expose you to real challenges, big challenges, challenges that other people haven't even solved yet.
JandersOf86@reddit
Awesome. That's rad. Thanks for the explanation.
ajamdonut@reddit
"I wish someone would just offer me a job" - Then continues to do nothing out of the ordinary, copies everyone else, makes tiny applications, looks like everyone else.
kyky_otaku@reddit
Totally agree!
rustyseapants@reddit
Why do you hide your profile?
davidHwang718@reddit
'Shooting from half court every time' was the exact thing that finally clicked for me too. The shift wasn't really about choosing smaller projects, it was about choosing projects where you could get to a working first version in days instead of months. A small project that actually ships to real users teaches you things no abandoned big one does.
marrsd@reddit
WTF is a resume project? First I've heard of one. If you don't have prior work experience then you need to show you can code. A basic web app will suffice. It doesn't need to be Facebook.
poofighter19@reddit
I feel like every beginner tries to make the next Facebook as their first project at some point.
AdventurousLime309@reddit
This is honestly one of the most valuable realizations in programming. Small projects teach completion, iteration, debugging, and confidence. Huge “dream projects” mostly teach how to accumulate unfinished folders on your desktop lol.
The internet kind of destroys people’s perception of normal progress because everyone only posts polished outcomes. Most good developers got better through dozens of small boring projects before building anything impressive.
Key_Use_8361@reddit
this is painfully real 😭small messy projects honestly teach way more than spending 4 months planning the perfect big project runable has actually been pretty nice for quick little experiments because setup friction kills motivation fast 💀
MeruconRei@reddit
One of the most important posts I have seen in a long time. I had the same thought recently when I looked at a project I made in school 8 years ago now. I just expanded a project we made during class and the teacher was so impressed. Everything was in a single file, OOP principles were unknown to me and it was just something I made from scratch with no big framework in java. But it was fun. No pressure no anything. Just fun building the project and it worked.
All this online doomerism about how competitive the market is now and the whole AI thing really makes you forget that social media isn't reality.
GooseExtension5272@reddit
big facts here, op. we often forget that it's all about the journey and learning, not just the end project. small wins matter and can build your skills without the stress of chasing perfection.
redzzzaw@reddit
bot
stoneyape-@reddit
A huge struggle for me right now and you are so right. I just published my first git repo and it was a simple bash and python log parser. It feels so elementary but we all start somewhere and im proud to know i published something.
Snowpecker@reddit
I feel the same way. I used multiple API’s for a personal dashboard for the first time and hosted it. It’s the small wins and progression that counts.