My Journey to Next.js Developer

Started coding at 15. Within a couple years, I had launched multiple products. Here's how I got here.

The Path

1. HTML & CSS – Built terrible websites, learned the basics
2. JavaScript – freeCodeCamp, JavaScript.info, lots of trial and error
3. React – Components finally clicked
4. Next.js – SSR, file-based routing, API routes in one framework
5. TypeScript – Won't start a project without it now

Why Next.js?

• SEO – Server-side rendering built-in
• Routing – File-based, zero config
• API – Backend routes in the same project
• Images – Automatic optimization

What I Actually Use

• Framework: Next.js with TypeScript
• Styling: Tailwind CSS
• Database: MySQL or PostgreSQL
• Deployment: Vercel

That's it. No complex toolchain.

Projects That Taught Me

Clark (Discord Bot + Dashboard)

• Python/discord.py for the bot
• Next.js dashboard with FastAPI backend
• Async MySQL, Redis caching

Basedrop (File Hosting)

• Next.js + S3 presigned URLs
• Direct uploads to bypass server limits

Resources That Helped

• Next.js Docs – Start here
• React Docs – New docs are excellent
• MDN – Web API reference

Mistakes Made

1. Over-engineering – First project had Kubernetes for a to-do app
2. Perfectionism – Polished features users ignored
3. Not shipping – Waited too long to launch

Advice

• Build real projects, not just tutorials
• Ship before you feel ready
• Read other people's code
• Ask for help sooner

Related: Building Clark • Building Basedrop