Let’s be honest:
Most developer portfolios are digital graveyards. We build them in a weekend, push them to Vercel, and then let them gather virtual dust until the next job hunt. It recently hit a point where my old site felt like it belonged to a different version of me.
As a student at NUST SEECS balancing deep 5G research with full-stack engineering, I realized I didn't just need a list of links, I needed a living artifact that showed how I think, not just what I've coded.
Here is the journey of rebuilding my Portfolio and why I shifted my focus from "look at me" to "let’s build together."
The Death of the Project List:
The biggest mistake I made in previous iterations was treating my portfolio like a laundry list. Modern engineering is about impact-driven storytelling. When I built CreatiFlow, an AI-powered image SaaS, the goal wasn't just to use a cool API. I wanted to see if I could handle the "boring" but essential parts: credit-based systems, secure image ingestion pipelines, and persistent state management
In the 2026, recruiters are looking for this "Production Engineering" mindset—moving beyond _vibe coding*_* and into building maintainable systems.
Bridging the Gap:
The Researcher-Engineer, One of the hardest things to communicate in a portfolio is the intersection of different worlds. My days are spent between Web Engineering: Building real-time apps, AI Research: Optimizing algorithms for vehicular network communication. For a long time, I kept these separate. My new portfolio treats research not as a credential, but as evidence of high-level algorithmic thinking that I bring to every line of JavaScript.
I'm curious to hear from this community: What is the one tiny detail in your portfolio that you’re most proud of (a specific micro-interaction, a clean API route, or an academic achievement)? How are you balancing vibe coding with production-grade engineering? Do you think the rise of AI agents is changing what a senior portfolio looks like? For those in both research and dev: How do you showcase your papers without making your site look like a 1990s university directory? I’d love for you to check out the new site and tear it apart (constructively!). Let's connect:
I’m always looking to collaborate on Web/AI projects.
Happy coding!
Top comments (0)