Back to blog
3 min read

Why Every Developer Needs a Personal Lab

A portfolio is static. A lab is alive. Here's why I built this site as a living workspace.

WebCareerPhilosophy

Portfolio vs. Lab

A portfolio says "look what I did." A lab says "look what I'm doing."

Most developer portfolios are graveyards. Beautiful, static graveyards. You visit once, see three projects from 2022, and never return. There's no life, no rhythm, no reason to come back.

A lab is different. It's a living workspace. Projects get added, updated, sometimes removed. There's music playing. Blog posts appear. It reflects who you are right now, not who you were when you last updated your resume.

What Makes a Lab

  1. 01It's always changing. New projects, new posts, new ideas. The date in the header isn't decoration — it's a statement that this space is alive.
  1. 01It shows process, not just results. Blog posts about how you built things, what you learned, what failed. The journey matters more than the destination.
  1. 01It has personality. Music taste, design choices, writing voice — these are signals. They tell visitors who you are faster than any "About Me" paragraph.
  1. 01It's useful to you. This isn't just for visitors. My lab has a music player I actually use while coding. The blog is where I organize my thoughts. The project list is my own reference.

The Technical Approach

This site is built with:

  • Next.js 15 — App Router, server components, great DX
  • Tailwind CSS — utility-first, consistent design tokens
  • Framer Motion — subtle animations that make it feel alive
  • Spotify embed — real music, not just a track list
  • Vercel — deploy on push, zero config

The design is inspired by two sites I admire:

  • shawnlukas.com — the "lab" aesthetic, grid overlays, bold typography, music integration
  • lucasporterbakker.com — bento grid layout, info-dense but clean

I didn't copy either. I took the principles — dark, minimal, technical, alive — and made something that fits me.

The AI Angle

Every project on this site was built with AI assistance. That's not a gimmick — it's the point. I'm exploring what's possible when you treat AI as a creative partner, not just a code generator.

The site itself was built in a single Cursor session. Not because AI is magic, but because I'd already done the thinking: vision doc, design system, wireframes. The AI just executed.

Start Yours

You don't need a domain. You don't need a perfect design. You need a folder, a framework, and something to say.

Start messy. Ship fast. Iterate forever. That's what a lab is for.

No track playing

331 tracks available

Queue · 0 tracks