If you have been following me for a long time, you already know that I have been holding off on my Portfolio review for several months.
Before you ask, yes, I will finally show my portfolio website. First, I want to write about something we all may have been thinking about at some point.
Everyone needs a developer portfolio. It's one of the big ways to stand out in the tech market because it shows your work and experience to recruiters in a friendly UI format. Some may say it's a great alternative to review a candidate's work (Source: Trust me bro).
However, in the age of AI, it seems that it's almost impossible to create a portfolio that stands out. Why is that the case?
AI Can do...anything?
We all (probably) have tried using AI at some point and even still use AI in our daily lives. Whether how much you have used it, you probably already know its capabilities.
AI is trained so well that it can potentially one-shot a website portfolio. Even better, if the person decides, it can add features and other stuff to make the website look like it was built in months (even though it was built in minutes). We even got to the point where Claude was able to merge two games into one in a matter of a few weeks!
It's crazy isn't it. AI development has been rapidly growing in the last few years to the point where it is accomplishing tasks that may have taken months to do.
With that said, I thought to myself: "Why consider building a portfolio if everyone can vibe code their way into making their perfect portfolio?"
To be honest, it's a valid question. The market has been difficult because everyone is using AI to their advantage to stand out from the market. I have seen a lot of Website Portfolios and Resumes that have been assisted with AI. As a result, the bar has never been higher.
However, I still believe having a portfolio still matters, even in this age where it seems impossible. Here's my reasoning.
AI Portfolios may look different, but they are the same.
What do I mean by this? I am talking about "style".
If you try to vibe code a portfolio, people can tell that the portfolio is vibe coded. Sure, it's not the EXACT replica compare to 100 portfolios out there, but you can easily tell by seeing some UI features that are defaulted if you vaguely prompt it.
A small example is this:
I have reviewed a lot of portfolios that has this (or something similar). Sure this may be a coincidence, but I want you to try to vibe code a sample website portfolio. Most of the time, they will add this feature.
This matters because if you think about it, a lot of portfolios out there are simply the same, even though it may not look like it. You have to have good "attention to detail" to see this for sure. However, at this point, coming from a person who has reviewed candidates before, it tends to be really repetitive. Hence, making it harder in the hiring process since everyone is doing the same thing and more research needs to be accounted for.
This leads to the next point.
"New Mask, Same Task"
Yes, I took this straight up from RDJ. Though the whole point is that even though he plays a different character, he is still RDJ.
What does this mean in this context? Just because you have pretty portfolio, it does not mean your work reflects that. You can create many different portfolios under your name. At the end of the day, it's still you that needs to improve and not the portfolio.
Portfolio is used as a presentation. If you are presenting your portfolio and it looks good, I would assume you have a lot of work experience and projects that are noticeable based on your portfolio design and how you are selling yourself.
For example, you have a front-end developer portfolio, but if I were to investigate further into your GitHub, I may see the following things:
- You just joined as of this year on GitHub.
- You claimed you did Open-Source, but there is no PR that reflects that.
- Your Portfolio has good UI, your project doesn't.
I can list a lot of things, but the main point is that if you have a good portfolio with a good list of projects you have done, you better hope that your projects and work reflects on how you built this portfolio. This is ESPECIALLY true if you tried to become a front-end developer. If your UI is good, you better hope your projects reflects that.
It's something to keep in mind when building your portfolio. Of course, if you are applying for a back-end developer role, having a good UI on your website portfolio isn't really required, but it's a nice to have. The whole point is to not misrepresent yourself. Be careful on what you add on your portfolio. Always assume people will have questions on your work.
Those are the two main things. Though you may be asking "How do I make my portfolio stand out"?
Here are some key things that you can do (and yes, I am now showing my portfolio lol).
1. Start with a basic portfolio template, then use AI to add onto it.
For my case, I have used an existing portfolio from "brittanychiang.com and meikopoulos.com". From there, I grab existing features using AI and put them together into a portfolio I am proud of. Additionally, I added some new features that are not distracting, but is something I want to add onto my portfolio to make it unique to me:
Instead of building it from scratch, I encourage you to find a portfolio that already exists (Bonus points: Proven that it stands out in the tech market) and build it on top of it. This allows the portfolio to be unique and that reflects you. Additionally, building on to of a template is a good starting point because it already has the fundamentals on what makes a portfolio "good". In this case, I added a feature where the "Skills" section reveals Pokemon in each Skill Card, though I am not sharing how it works. Can you find the Easter egg that does that?
2. Usability and Accessibility!
This is the most OVERLOOK aspect of making a portfolio. Even though you can make your portfolio look nice, it's most likely that it's not accessible.
For example, it can be very laggy on low-end devices, not responsive on mobile, not following best practices, etc. There are a lot of things that is overlooked because we focus on building the best looking portfolio where we should be focusing on making our website portfolio optimized.
I would recommend spending time using AI to optimize your portfolio. In other words: "Boil the lake to make the portfolio, but boil the ocean for website optimization and accessibility".
For mine, I spend countless prompts where I tell the AI to make sure my portfolio is less "laggy" and being able to run on mobile.
This will allow to make a much cleaner portfolio and being able to be used by many people such as people who have disabilities, devices that are not powerful, etc.
3. Simplicity beats Complexity!
A lot of portfolios we have seen tends to be very complex where there are a lot of animations and such.
However, the more you think about it, the more you realized that you can stand out easily.
I have seen a lot of portfolios that are REALLY complex and have a lot of animations, but what people fail to realized is that: You are doing what everyone else is doing.
At the end of the day, you are not standing out, even if you THINK that you are. If I see a portfolio that is heavily designed using AI, I can guarantee that I can find the exact same person who can one-up that.
The best advice is making it simple. Yes, it's boring and yes it's common. But..that's the whole point.
I rarely see any portfolio that is simply built. Usually the ones that are simple tends to stand out because it shows a lot of information really quickly.
This is huge because recruiters tends to review portfolios and resumes in seconds. They will not have time to look over your awesome UI and animation you have Vibe Coded. The UI should be the icing on the cake, not the whole cake. The most important parts is your work and experience.
Then why design your portfolio? It makes it much easier for people to navigate your work and experience than reading your resume line-by-line of course lol. The point is not spending time making the UI look nice, but spending more time on making sure they are able to access your work and experience within a small amount of clicks.
4. Networking (AKA show your portfolio)
This is the biggest thing. SHOW YOUR PORTFOLIO.
What's the point of making a portfolio if no one is going to see it. You can share it to your family, friends, your LinkedIn connections, and even on DEV!
With that said, here is my portfolio. Give it a review and let me know what you think!
Speaking of, if you have a portfolio that has been sitting around, feel free to share your portfolio in the comments. I would love to see your portfolio and review them!
That is all! Cya :D















Top comments (44)
I am simplify my portfolio/cv:
Creator of mordorjs and TifY also pipeline-operator fanatic.
Those legacy tech sooner or later outdated. Make some fun until singularity!
Thanks Peter! Will look into it further and will let you know on this thread! :)
You are make me crazy, so my next project is create my github portfolio which is now try to show my ideas |> repos map. So I connected to my dev.to posts. This is not the finall format but at least hold much more information as ever before. It will be also great backround layer for my upcomming sci-fi book.
Meanwhile I making too much activity because my GPT-6 plus subscribe on 2% credits. Maybe those information also able to represent my activity level.
pipes is always lead to flow
Look man. Busy times lol.
I checked it out! Its really good and that animation of balls when you scroll up is great. I'll have to understand that implementation, I don't know why but I tried it for several minutes😅.
One question though, what does portfolio actually include?, cause I'm a student and I have an internship experience which I always refrain from talking about in public for obvious reasons and I've got some good OSSs.
Thanks Dhruv! The ball animation took me 2 planets of resources to implement for some odd reason (mainly I was bad at explaining to the AI at that time lol).
For your question, it depends on what you want to show to the recruiters. You have to think about what they are looking for. In your case, I would include your work experience, projects, and DEV blog as a nice touch.
I would recommend seeing what other people's portfolio looks like and go from there. As a bonus, see videos of people roasting other people's portfolios. A good channel to start is Anthony Sistilli where he made a series or roasting people's portfolios. He also give good tips on them along with Resumes as well!
Hope this helps!
I agree with you on the "Simplicity beats complexity", that's why I generally showcase and build my professional work and profile over the LinkedIn. It's good to follow the KISS Principles in general 😀
I agree! Always keep it simple. You will be surprise on the result you will get than overengineering it! Thanks Ranjan!
You don't need a portfolio. That simply isn't true - a total myth. They're generally just curated vanity projects that tell a potential employer next to nothing about the reality of a candidate's abilities. Far better is an active/interesting GitHub/GitLab/whatever - warts and all - false starts, finished projects, unfinished projects, contributions to other projects, unvarnished experiments... the more the better. Anyone hiring devs who knows what they're doing will glean far more from that than they would from any portfolio site.
Over thirty years as a developer I've never had a portfolio site and it's never been an issue. I also don't attach much weight to candidate portfolio sites unless they're truly awful, or exceptional/original (which is rare) - there is very little point to a cookie cutter HTML-ified CV.
In a few cases when a candidate has had a portfolio site, it has actually been the reason that they did not progress further in the hiring process... over-engineering, errors, inappropriate use of technology etc.
Hey Jon. Thanks for sharing!
I do have seen people having without portfolios and still got into jobs in this brutal market. Some of my friends who graduated didn't have a portfolio but still got a job through networking, so I see where you are coming from.
I say "need" in this case because I feel like it's a good start of having at least something to show as a good starting point in your developer journey. Of course, your first project doesn't need to be a portfolio, but it's a good starting point and it's a friendly way to showcase your future projects (if you decide to put them there). I can see where if you already have experience, then having a portfolio is just a nice thing to have, not something you need.
I believe if you are freelancing, then having a portfolio is a great thing to have because it tells you that the client not only see that this developer has experience, but also the style of the website and credibility of their work to clients. It's suitable for Front-end web developers for sure, though having it as a freelance developer in general is a must. Though, I never did freelancing before so take this as a grain of salt, but that is based on what I have seen and heard.
I am not expecting everyone to have a portfolio, but based on my experience as a beginner/mid level (in my opinion of me being a beginner/mid level) I think having a portfolio is a must and a good starting point to show your work to all audience, more than just recruiters. You may never know if the person that you share your portfolio with is impress and sharing it to their other networks.
I do have a question. When you mention "when a candidate has had a portfolio site, it has actually been the reason that they did not progress further in the hiring process... over-engineering, errors, inappropriate use of technology etc.", do recruiters or general people tend to figure out during the hiring process? How do they determine if they are using the wrong technology? I guess this is more of an elaboration?
Thanks for sharing on your view Jon! Let me know if anything!
The problem with a lot of tech recruitment is that the people doing the recruitment are non-technical. Doing it right should involve technical people from as early as possible... who will actually look in more technical detail at what is presented by the candidate.
Recruiting teams worth their salt will not be moved by sparkly nonsense that is often just 'lipstick on a pig'.
I agree with you 100%
But I still don’t have my portfolio site 🤣
All good lol. I appreciate you reading though!
Nice portfolio Francis! Great to see it live!
Thanks Julien!
Great article, Francis! You are so right
Thanks Ben!
no problem, Francis :)
Thanks for sharing Francis! I used Brittany Chiang a lot for inspiration when I was building my first portfolio. 😁
It's pretty well known (in my world lol) of her designs. Very clean and simple! Thanks Gift :)
🥳 IT'S ONLY BEEN AN ETERNITY IN THE MAKING, BUT THE PORTFOLIO IS FINALLY SEEING LIGHT!
Yea but to be fair, it's on my dev.to for a LONG time. I just never talked about it till now lol
Well yeah, but it's different when you talk about it 😂 It's good though! A portfolio goes a long way and if you wanna up it, add specifics, so people know what specific region in the codebases you had a hand in. Eg. I work on ERP systems, that's a pretty broad spectrum... But I specifically implemented the AR, AP, GL and Stock journals and ledgers, the manufacturing module, the dashboard, log-sink and cashbook modules. Knowing those details adds far more insight than 'I work on financial systems'. I really need to prep 1 tbh...
Awesome portfolio!
After seeing it, I kinda want to update mine too 😄
Glad it inspired you! If you want to share, feel free (you don't have to ofc) :)
Thanks Pavel!
Some comments may only be visible to logged-in visitors. Sign in to view all comments.