I've been building for the web for over two decades. I've survived the jQuery era, the rise and fall of framework fatigue, and more "Ruby on Rails is dead" takes than I can count. And I'm telling you right now: if you're thinking about getting into web development, or you're already in it and wondering where things are headed, this is the moment.
Not because the tools are shinier. Not because salaries are up. Because the job itself has fundamentally changed — and it changed in our favor.
It was never about the code.
Here's something that took me years to internalize: web development was never about writing code. It was always about solving problems for people. The code was just the medium.
Think about it. Nobody hires you because you write elegant Ruby or perfectly typed TypeScript. They hire you because their users need something — a workflow that doesn't suck, a way to get paid faster, a dashboard that actually tells them what's going on. Your job is to figure out what that something is and make it real.
The problem is that for a long time, the "making it real" part consumed so much energy that we barely had time for the "figuring out" part. You'd spend three days fighting CSS grid or debugging a race condition, and by the time you shipped, nobody remembered what problem you were solving in the first place.
That ratio has flipped.
AI handles the typing. You handle the thinking.
AI code assistants are writing most of the boilerplate now. And honestly? They're pretty good at it. Not perfect — you still need to review, refactor, and make architectural decisions — but the days of spending an afternoon scaffolding a CRUD interface are over.
What this means in practice is that you finally have time to do the parts of the job that actually matter. Validating requirements with stakeholders before you write a single line. Questioning whether the proposed solution is even the right one. Thinking about edge cases, accessibility, performance, security — all the stuff that separates a feature from a good feature.
AI didn't replace developers. It removed the busywork that was preventing developers from doing their actual job.
Iteration speed is a superpower.
Here's where it gets really interesting. When generating code takes minutes instead of days, you can produce multiple solutions to the same problem. Not hypothetically — literally. You can build two different approaches, put them in front of real users, and let data decide which one wins.
A/B testing used to be something only companies with dedicated growth teams could pull off. Now? A single developer can spin up variants, instrument them, and iterate based on results. You're not guessing anymore. You're experimenting.
That changes the entire dynamic of how we build products. Less "I think this is the right approach" and more "let's find out.".
The end of backend developer vs. frontend developer
I'm going to say something that might be uncomfortable: the distinction between "backend developer" and "frontend developer" is dying. And if you're clinging to one of those labels, it's time to let go.
AI has lowered the barrier to working across the entire stack. The frontend specialist who "doesn't do databases" and the backend engineer who "doesn't touch CSS" — those roles made sense when each layer required deep, specialized knowledge just to be productive. But the tools have changed. You can scaffold a Rails application in seconds, write a new feature, test it, and deploy it — all in the same afternoon.
The market is moving toward full-stack web developers. People who understand the whole picture, who can own a feature end to end, who don't need to wait for three different teams to align before something ships.
Either you're a web developer, or you're competing against someone who is. Adapt accordingly.
You're a builder now
This is the mindset shift that matters most. You're not a "developer" in the old sense of the word — someone measured by lines of code, pull requests, or how many Jira tickets they close. You're a builder.
And builders are measured by what they ship.
How many features did you deliver this quarter? How many improvements made it to production? Did user retention go up? Did support tickets go down? Those are the questions that matter now. Not "how clean is your git history" or "how many code reviews did you do."
I'm not saying code quality doesn't matter — it does, as a means to an end. But the end is always the same: working software in production, making money for your company, solving problems for your users.
The best code in the world is worthless if it's sitting in a branch that never got merged.
The best code is the code in production
Let me be blunt about this one. The best code is the code that's in production making money for your company. Full stop.
Not the code that's "architecturally pure." Not the code that follows every pattern in the book. Not the code that got praised in a conference talk. The code that shipped, that works, that users interact with every day, that generates revenue.
This isn't an excuse to ship garbage. It's a reminder that perfection is the enemy of delivery. A well-tested, slightly imperfect feature that's live and generating value beats a beautifully engineered feature that's been "almost ready" for three sprints.
Three OKRs for the AI development era
If you take nothing else from this post, take this. In this new era, every feature you build should be measured against three criteria. Think of them as your personal OKRs:
Useful. Does it solve a real problem? Did someone actually ask for this, or are you building it because it's technically interesting? If users don't need it, it doesn't matter how well it's built.
Performant. Does it work fast enough that users don't notice it? Performance isn't a nice-to-have. A slow feature is a broken feature.
Secure. Is it safe? Did you think about authorisation, input validation, data exposure? Security isn't something you bolt on after launch. It's baked into every decision from day one.
Useful. Performant. Secure. If your feature checks all three boxes, you did your job. If it doesn't, nothing else matters.
The opportunity is right now
We're in one of those rare inflection points where the tools, the market, and the culture are all aligned in favor of people who build things for the web.
AI is handling the grunt work. The industry is consolidating around full-stack, outcome-oriented roles. Companies are starting to reward shipping over process. And the web itself — still the most open, most accessible, most democratic platform ever built — isn't going anywhere.
If you're already a web developer, level up. Learn to think across the stack. Embrace AI as a tool, not a threat. Focus on outcomes, not output.
If you're thinking about becoming one, stop thinking and start building. The barrier to entry has never been lower, and the ceiling has never been higher.
There's never been a better time.
