If you don't know the meaning of Portfolio; this is what Google says:
A portfolio is a collection of academic and professional materials that showcase your beliefs, skills, qualifications, education, training, and experiences.
Now, let's talk about portfolios, specifically for developers planning to create their own.
In this massive digital world, where everyone has their own little corner filled with numerous social URLs; having a portfolio is crucial.
However, it's not mandatory to code it, a point that many of us fail to understand.
There are tools available that can help you in building your portfolio without any coding. After all, coding to make your unique one takes a lot of effort because poorly constructed portfolios can leave a negative impression.
In my experience of 2 years, having a portfolio or an equivalent platform is important. However, coding it isn't necessary at all.
I understand the feeling & thrill that creating a portfolio brings, but people in the early stages with very little to showcase can use platforms like GitHub as a substitute for a portfolio.
What do you guys think? Share your thoughts on these two questions:
- Do we need a portfolio?
- If we choose to have a portfolio, is coding it necessary?
I encourage you to share your experiences and opinions in the comments!
Next week, I am planning to write a post that will prove that you don't need to code a portfolio and will discover ways where you can make yours in less than an hour.
I'm not kidding, so keep an eye out for that.
I'm not suggesting you shouldn't create a portfolio, but if you do, make it truly unique so it's worth the time invested.
Personally, I don't have a separate portfolio; my GitHub serves as my development portfolio.
If you're considering creating your portfolio, here are a few resources:
300+ Portfolios - Highly recommended
Until next time :)
Top comments (10)
Whether it's hosted on GitHub, a CMS platform, or even hand-coded, portfolios are crucial for developers to showcase their work and abilities. They serve as tangible evidence of your skills, going beyond mere words to display projects you are proud of and personally crafted. While having a GitHub is sufficient for developers and doesn't necessitate a standout portfolio, be cautious of falling into the trap of seeking GitHub repository clout. Many developers might emphasize the importance of those green activity boxes on GitHub, but in reality, the substance of your work is what truly matters. Your GitHub is quite respectable and there's nothing wrong with it.
For employers, especially when looking to join a company, recruiters or hiring managers often appreciate more visually oriented presentations. This can be especially true for those not deeply versed in technology, who may find a simple GitHub link less accessible compared to a well-organized portfolio website that showcases your work in a more user-friendly manner. Ultimately, the necessity of a visual portfolio alongside your GitHub depends on the role you're targeting. Most of the time, having a visual element to complement your GitHub is beneficial. Companies appreciate seeing visual demonstrations of your work, as it not only showcases your ability to compile and architect projects but also adds credibility to your front-end web development skills.
@c0mmand3rj
Thanks so much for sharing such valuable suggestions.
Don't worry; I will complete my portfolio by next month, and it will be one of the best :)
I really liked your perspective on
Coding a portfolio can be useful in two situtations:
You should not except from a Backend, Frontend or Full Stack developer to know how to design a beautiful website. Recruiters won't care if you are using a template for your portfolio, they only care about the initial impact. When you reach the technical interview phase, you can talk about your personal projects.
Thanks for sharing. UX Portfolios are the best ^^
Absolutely agree that having some decent projects is a must before building our portfolio.
It's interesting to note that few people label their portfolio as a project, which, for obvious reasons, it already is.
I would never hire a coder without self coded portfolio. So, you just will lose every opportunity from people like me. Why would you want to do that. Maybe, many are like me. It is not much time you have to spend.
Guess you would never hire Elon Musk. Sorry, just kidding. I want to add a little bit of humor so that the conversation is not too serious :)
I totally understand your point, and believe me, I've heard that a lot. I even agree that having a decent portfolio can lead to more job opportunities.
However, it's worth noting that a bad portfolio is worse, even if the person coded it. There are platforms like Polywork (and more) that can bridge that gap.
I would say, focus on building a portfolio when someone has 2-3 decent projects.
I don't want to contradict anyone, so big thanks for sharing your opinion.
It's 100% unnecessary... and I mean having a portfolio, not coding one.
Thanks for sharing your opinion.
Please provide facts or scenarios that can support your statement.
A portfolio would be relevant if the person is an influencer or is involved in various activities.
I've seen people doing great without one, and while others with a portfolio.
It's more like a personal preference :)
I think it's an obligation now
Haha! Well, now it's a must-have!