Why your technical portfolio isn't getting results

Over the past few years I’ve reviewed a lot of technical portfolios for other people, it’s very clear the projects that stand out versus the ones that don’t. The ones that stand out are built with quality in mind. It’s not enough to make something that looks nice, companies want to know you care about the code you’ve written.
In this blog post, we will cover the 7 most common things I see that aren’t added to someone’s portfolio, that could add a lot of value if they were.
First things first, do I think you need to have a portfolio?
Not necessarily, for example I don’t have one and many amazing engineers I know don’t have one. However, I caveat that with already having enough years of experience to allow us to not need to rely on a portfolio. Some of us had other ways of entry that we were able to use to our advantage at the time and acknowledge that the market is different now to what it was 10 years ago.
If you are wanting to use your portfolio to get noticed and to get your foot in the door, I would say that these 7 focus areas will help you stand out and get noticed. They will also help you in most technical tests that you do have, because developing software in this way is desirable.
Read more on my blog post:
open.substack.com/pub/jadecod...
Visit my LinkedIn:
/ jade-codes

[@thebehavioral]

It seems like balancing the “I’m having fun and learning” part of one’s portfolio with the “I’m demonstrating web-scale class best practices” is the hard part.

[@Jade-Codes]

Absolutely, and I think you can still have fun learning whilst building things with good practices in mind

[@emamhossan8798]

Excellent video

[@Jade-Codes]

Thank you!!