Most developers I know, myself included, built a portfolio once and then let it quietly rot. Six months pass, you've shipped a bunch of stuff, learned a new framework, contributed to three open source projects. Your portfolio still says you're "currently exploring TypeScript." The problem isn't laziness. It's that keeping a portfolio updated is a chore that never feels urgent until you actually need it. So what are the realistic options? I wanted to lay out four approaches I've either tried or watched other devs try, with honest trade-offs for each. 1. Manual Updates (The Classic) You build a portfolio site with Gatsby, Hugo, plain HTML, whatever. You deploy it. You tell yourself you'll update it every month. Pros: Total control over every pixel. No vendor lock-in. You can show off your design taste. Cons: Nobody actually updates monthly. The friction is just high enough that it never happens. After a year, your "recent projects" section is older than some of your npm packages.…