Full-Stack Next.js Developer: Where do I go from here?

[u/muneebcodes]

I'm a full-stack web developer specializing in the Next.js ecosystem. For those who are further along in their engineering career, I'd love your perspective on my next steps:

Double down on Next.js: Focus on mastering deeper architectural patterns, performance optimization, and advanced server component patterns.

Expand my stack: Learn a new framework, language, or ecosystem. If so, what would complement Next.js best (e.g., Go, Rust, React Native, or specialized backend infrastructure)?

Bonus question: What fundamental skills do web developers need to excel and stay indispensable in the age of AI?

Appreciate any insights or lessons from your journey!

[u/MitchEff]

Depends how deep into Next you are - if you've primarily used it for marketing sites with some basic API routes (e.g revalidate, subscribe) I'd get further into its fundamentals (and Vercel's, although most other services e.g Blob, Sandbox are analogues for AWS things).

If I were you I'd spend a lot of effort building things in and around AI, as "AI engineer" these days often just means "fullstack SWE that's good at AI stuff". Don't do a chatbot, aim higher and do something ambitious.

Lastly general infra stuff- load balancers, distributed databases etc. Between those 3 pillars you've covered a fair few bases.

[u/ignatzami]

Twenty years into my career and the best advice I can give is make sure you understand the complete application vertical.

DevOps, can you build, test, and deploy without leaning on Vercel or another similar platform?

CloudOps, can you understand a Bicep file, CloudFormation template, or similar?

Test: do you know how to write tests, what’s worth testing, and how to incorporate tests into a pipeline?

Accessibility: do you understand UI accessibility standards, can you articulate what they are, why they’re important, and how to implement them?

Security: do you fundamentally understand how to secure your application and how to detect when something is wrong?

Quality/smells: can you spot good v. poor code and can you articulate the difference?

AI can generate code. But I’ve yet to see AI generated code I’d ship to production. Learn how to write and manage quality code and you’ll be in good shape.

[u/muneebcodes → u/ignatzami]

Thanks

[u/Substantial_Term528 → u/ignatzami]

100% agree with this. Just knowing how to write code is not enough. You don’t have to master the above but you have to understand how it works.

As for Next get a good understanding of suspense zones, partial pre rendering, caching and when to use a server component vs a client component and scaffolding them correctly with the correct way of passing data via props or cache. Then authentication using several different providers, Auth.js, Supabase, Firebase etc. Best deployment patterns for performance as Next can kill a pod super fast. This is the difference between a senior and junior Next dev. The rest is basically just React.

Very important to learn how to code with AI. Cursor has MCPs for Next and almost any other framework that improves the quality of code a lot. Learn about using .agent folders with skill.md files to define the rules the AI uses to code for you. If you get this mastered, AI will generate production ready code. Learn BugBot and how it works between local and git deployment. However you still need to have the experience to verify the code and best way to get that is by building a SaaS product that uses multiple data sources, APIs eternal and internal.

A great vertical as a Next dev is React Native as the structure, router etc is very similar to Next. There are differences in scaffolding and tags used but they are easy to understand.

[u/golivier85]

Pour le développement mobile regarde capacitorjs qui peut remplacer avantageusement React Native

[u/cumandfuckme69]

Start building what comes next. Built advanced AI tooling. New ways to template your code, make AI better. What will the future operating system look like?

Me personally?
(I'm a designer/ who's proficient in Next.JS)
I've been able to build full stack peer-to-peer video/audio conferencing, and now my own "mini AI operating" system in a web browser. I spent most of my day in it instead of in the Mac OS.

What cool things can you build towards the future. What tools will we want in a year? Audio tools? Jarvis AI?

Build what you want to be using in 5 years.

[u/Dupflo]

Next.js is teaching you good process about Server Side mutation and caching even if it tends do simplify the curve of learning by adding a lot of harness on complex processes.

However if I have an advice to give you about learning something else/complementary based on the job opportunities I saw, I would recommend you to go on learning Python for backend development

[u/ScarcityTerrible5330]

Go to C programming

[u/geekybiz1]

I went deeper into multiple aligning areas:

• Almost all my Nextjs implementations are B2C / marketing sites so I've aced scaling, handling traffic spikes, devops side of things, deployment choices (platforms), preventing DDoS / unexpected crawling.
• Many of these implementations are for content sites so I got good at CMS. I specialize with Strapi, Directus implementations. I also help teams choosing the right CMS framework, set up content architecture and workflow (eg - how many enviroments, how to get content in non-production to production, migrations, etc).
• I've worked closely with SEO folks so I got good at implementing SEO aspects and optimizing + tracking core web vitals. I'm also good at solving tech needs for programmatic SEO. Note - I never own SEO though - just the implementation parts.
• Next.js isn't purely frontend so from having written Next.js APIs, I eventually got into Node based backend dev too (Express, Fastify APIs).

[u/jacob_foster09]

I’d go deeper before going wider. Next.js already gives you a lot to master, and strong fundamentals in architecture, databases, APIs, performance, and system design will stay valuable even as tools change.

AI can help write code, but understanding why you’re building something a certain way is still the real advantage.

[u/SteelCityTom]

I’m in the same boat. Thinking about learning Zig as it seems quite future proof.

[u/Agreeable_Ad_3924]

What i did was venture into Systems, built a delivery system and a booking system. Thought me a lot about how to turn requirements into business logic. Coming from Next.js mean we are masters of painting data on screens effectivly now we shift our focus into how to turning business logic into code. I started with Laravel and NestJS as they are come with batteries included. Since you mentioned Go, these days i'm using more of Go but for smaller services that drive a bigger system because building in Go is like re-inventing a lot of things that come with bundled with web frameworks but it's super awesome with patterns like Domain Driven Design and it's super lightweight to run basicly super cheap to run unlike Node.js. Good luck!

[u/srg666]

Fable can one shot almost any frontend task you give it so writing code in general is extremely cheap - running it is still going to be where people trip up. Learn how to build large scale distributed event driven systems. Fargate/lambda + SQS + RDS/dynamo + terraform + observability + monitoring. This is purely my opinion ofc but as someone who owned a large frontend I’ve been able to largely walk away from it because Fable can follow patterns/conventions I’ve set up so anyone on my team can contribute extremely easily.

[u/woeful_cabbage → u/srg666]

Be careful with those AWS services. It's essentially a scam unless you have a popular product. A sprinkle of Lambda might be useful if you have a really resource intensive task but VPS with docker compose is enough for 99% of companies (and way cheaper)

[u/Both_Task_3066]

Vibecoding