Is a developer portfolio still worth it in the AI era?
Yes, but not the kind you’re picturing. In an era where anyone can generate a polished portfolio site in an afternoon, the template-with-skills-bars portfolio is worth close to nothing. What’s worth more than ever is proof of shipping: real projects, live, linked from one page with your name on it. Evidence beats presentation.
What changed about portfolios?
AI collapsed the cost of looking professional. A beautiful single-page portfolio with smooth scroll, a headshot, and a skills grid used to signal effort; now it signals a prompt. Hiring managers and clients have adjusted: they skim past the presentation layer and look for things that can’t be generated, shipped products with real users, code they can read, decisions they can ask you about, and a trail showing the work happened over time. The portfolio didn’t die. The decorative portfolio did.
What should a developer’s site actually contain?
Five things, and it fits on one page. Who you are, in two honest sentences. The three projects you’d defend in an interview, each linked and live, each with one line saying what it is and one saying what was hard about it. Everything else you’ve shipped, behind a “more” if the list is long, because volume over time is itself the signal. Links to where the receipts live: GitHub, a technical post, a talk. And a way to reach you. That’s the entire spec. Every added section (testimonial carousels, animated skill percentages, stock-photo hero) subtracts credibility now, because it reads as filler where evidence should be.
Does it matter for freelancers and indie founders too?
More, if anything. A client can’t read your resume; they judge the trail. A prospect deciding whether your $29 product is trustworthy checks who made it. In both cases the question being answered is the same: is this a real person who ships real things? One page that aggregates everything you’ve built answers it in five seconds, and every individual project should link to that page, because the person deciding is usually standing on one of your projects when they wonder. That’s the case for connecting your work: your best project is your best marketing for every other one.
How do you keep it from going stale?
Make updating it cost nothing, because a portfolio last touched three years ago reads worse than none. The trick is separating the page from the projects: your sites carry one permanent link to the page; only the page changes. Then automate the change. This is the system BuiltByBadge runs from inside your AI assistant: a hub page with your face, top three, and everything else, plus a three-line badge on each site, and when you finish shipping something new your assistant asks whether to add it. Say yes and your portfolio just updated itself. Hand-rolled or automated, the principle is the same: a developer’s site in 2026 is a living index of shipped work, not a brochure. Keep the index honest and the index does the selling.
Built by