Does it make sense to discuss about coding anymore?

The answer, in my humble opinion, is no. Human coding is dead, and so are Stack Overflow, CSS tricks, inverted binary trees, LeetCode and whiteboard interviews. IDEs are going to be dead soon. Markdown is the new HTML.

AI has changed the landscape in a way nobody imagined. This is the Industrial Revolution of software. A master weaver in 1780 could produce cloth no machine could match. Intricate, precise, beautiful. By 1820, a child operating a power loom could outproduce him fifty to one. The weaver's skill didn't become worthless because it got worse. It became worthless because it stopped being rare. That's exactly where we are.

And this is why frontend engineering, as we know it, is dead. It was a nice run, we all had fun. We got free lunches, ping pong tables, PlayStation, conference tickets and great salaries. It was fun while it lasted. We are the new weavers.

How do we survive this wave?

Shift your perspective: you're not the football player anymore, you're the head coach. Agents, skills, and LLMs are your players. Your job is to make them play well together.

The future is product engineering. Owning the whole process, not just the codebase. Understanding backend, frontend, product, design. Talking to customers. Building reliable systems. Companies will need thinkers, not ticket solvers.

Process is the real skill.

I built 10 apps in recent months. My main focus has never been the code, it's been refining a winning process. Orchestrate, organize, refine, review, QA, refine again. Take notes of what breaks, repeat until it's solid. I do more QA than code review. I research. I study how users behave. I have a framework that spins up a full app (Next.js, Supabase, Google Auth, Stripe) in one command. Login, pricing, database, all ready. My worry is how to get the user to pay, not how to name a variable. This is already happening at work too: most of my time goes into reviewing and instructing, not writing code.

Your portfolio lives in your building process now, not on GitHub. Replace those green contribution squares with slides that show your thinking, your decisions, your system. That's what matters.

One thing I've learned using AI both at work and in personal projects: always play the Italian style. The infamous catenaccio. Stay on the defensive, never trust it blindly.

UX matters more than ever.

In a world of shadcn/ui Tailwind wrappers, your UX expertise is what makes the difference. Users are overwhelmed with AI tools today. Most of them fail, hallucinate, have no idea who their ideal user is. Real UX thinking is the purple cow.

Human connection still wins.

For years we focused on our shiny tickets, pull requests, code reviews. Now if you want to survive, you have to understand your users. Talk to them. AI can't catch that frustrated sigh, that confused pause, that "ah-ha" moment on someone's face. In a web built by agents but still used by humans, you're the one who bridges the gap.

Remember JavaScript fatigue? That was nothing. The pace now is relentless. Be ready to keep up, or get comfortable being left behind.