Hey, web developers: Choosing your portfolio projects? You need to know this
I’ve decided to start blogging about my journey to become a web developer, which so far it’s been exciting and fun but also demoralizing at times. I’m not going to lie, I thought about giving up at some point. But the developer's community is just so rich and full of people willing to help and give advice that I always found ways to keep motivated.
As you all know there is a point as you are learning to code, where you feel you are ready to start applying for jobs. And the nº1 advice is always: You need a portfolio! And you think sure, I’ll just build one, no worries. Well…some worries.
If you are in the process of building your portfolio, then I suggest you check out this How to Craft a Stand-Out Web Developer Portfolio article on Skillcrush, that I found extremely useful. And if you are the inspirational kind, these 15 Web Developer Portfolios to Inspire You on freeCodeCamp may come in handy.
But the reason I’m writing this article is because of the much-dreaded project section. Because the thing is, I build my portfolio, put it out there for the world to see, and started applying for jobs. And well honestly? Almost no one called back. I knew there must be something I could do to improve my chances and that's when I started doing what I do best: research.
I watched many web developer's channels on YouTube, and let me tell you, I know listening to stranger's advice on youtube may not be for everybody but to me, it was very helpful. Those videos where they review junior developer's portfolios can really help you identify the weak spots on yours.
There was one piece of advice I kept hearing over and over from different developers and that’s when it hit me. My problem was not in the portfolio itself, my problem were my projects. I uploaded four or five small projects that didn’t really showcase my abilities.
The best advice you’ll receive is: No course projects.
Do not, I repeat, do not by any means upload the projects you build along in a course. I know it’s tempting, I know you probably think, but I spend so much time on it, I build it, it´s mine, my own.
But no. Just no. Think for a moment about all the people that took those same courses, build those same projects, and also uploaded them to their portfolios. How is that a smart way of standing out?
And at the same time, it’s not really something you built from scratch, but rather something you coded along. Someone else provided the solutions to any problems you may have faced while building the projects, so how does that really show you can solve them on your own?
This advice just makes sense. And I would love to tell you I wasn’t guilty of it, but…. I am. I’m working on building new projects that can really show my skills and set me apart from other candidates. And I know you are probably wondering how can I give advice on something I haven’t even tried? Well, for one thing, It’s not my advice I’m simply passing it along from other far more experienced developers. But also IT. JUST. MAKES. SENSE. I’m working on some awesome new projects and when they are up, I’ll let you know the outcome.
I’d love to know what you think in the comments below. Have you built your web developer portfolio? What projects have you chosen?
