The Goldilocks Problem: Project Sizes

github logo ・1 min read

As someone who is trying to get a job, I'm constantly thinking of little apps I could make to enhance my skills and my portfolio. Because of this, I also try and weed out ideas that are too "big". They're something I want to do, and to accomplish someday, but I'm not sure if it's worthwhile to do so early in my journey. The other problem, is that I've started to run out of "small" projects. I find myself doing somewhat of the same things, and don't feel that they are noteworthy enough make posts on so I feel like I'm stagnating.

I can't find that "just right" size of project for me to tackle. Something bigger then a small standalone app, but not something as huge as involving a database and user accounts. What are everyone's thoughts about this?

twitter logo DISCUSS (1)
markdown guide

You can make static clones of other websites this way you will not be getting into databases and stuff but still make noteworthy frontend apps. By clone I mean you should experiment around different colors or redesign it the way you like just copy the concepts.

Classic DEV Post from May 4 '17

How I went from failing every interview to a job at Amazon

About halfway through the interviews, the interviewer would seemingly give up in frustration. A few days later, I would receive the dreaded, “Thank you for your interest” email.

Nina profile image
Hi, I'm Nina! I was originally an illustrator who's gotten into web development! I volunteer my time as a front-end developer for The PokéCommunity, but am still looking for a entry level job. :)