Web development is fun again

I personally don't find using LLMs "fun" but I do like this article for one simple reason. It points out that most contemporary frameworks for web are forms of slop and I don't think you should feel bad using an LLM to generate slop code and config to deal with it.

Something I like about our weird new LLM-assisted world is the number of people I know who are coding again, having mostly stopped as they moved into management roles or lost their personal side project time to becoming parents.

AI assistance means you can get something useful done in half an hour, or even while you are doing other stuff. You don't need to carve out 2-4 hours to ramp up any more.

If you have significant previous coding experience - even if it's a few years stale - you can drive these things extremely effectively. Especially if you have management experience, quite a lot of which transfers to "managing" coding agents (communicate clearly, set achievable goals, provide all relevant context.)

> On the frontend, you have build pipelines, bundlers, CSS frameworks with their own toolchains, progressive web apps, Core Web Vitals, SEO, layout shifts, srcset/responsive images… I remember when the biggest challenge was IE6 compatibility.

You only have those things if you choose to use them.

I've been building websites for 25 years. I use the same core technologies today that I did when I started. Sure, I make use of modern improvements to the languages themselves, but I have never permanently adopted any of the "hot new trends" and feel I am better - or at least saner - for it.

No, your marketing or e-commerce website almost certainly doesn't need a JS bundling toolchain. It almost certainly doesn't need a CSS preprocessor or even a CSS boilerplate/framework. It almost certainly doesn't need an enterprise-class PHP framework; or a dependency manager; or a CI/CD pipeline.

I remember those times, and it was a lot of fun, but there's really nothing stopping you from running a LAMP stack today, writing PHP without frameworks and with manual SQL queries.

In fact, it's a lot more fun for me to approach this today. Modern PHP is a joy. MariaSQL is very much MySQL (and switching to Postgres isn't exactly a bump in complexity). It's way easier to write code that won't get injected.

If you want to slice your designs in Photoshop (ehem, the real OGs used Fireworks) go ahead and use Dreamweaver, go ahead. That said, HTML5 makes not having to use tables for layout easy, not more complex and VS Code has all the good parts of Dreamweaver (trust me, you don't need or want the WYSIWG... if you must, just use inspect elements and move the changes over to the HTML file).

I guess all this is to say that web dev is simpler, not more complex for solo devs today. There exists more complicated tooling, but if you're solo-dev'ing something for fun, skip it!

EDIT: Also, phpMyAdmin was fun to use but also the best way to get your box popped. Today, something like DBeaver suits me just fine.

> Even with refinement and back-and-forth prompting, I’m easily 10x more productive

Developers notoriously overestimate the productivity gains of AI, especially because it's akin to gambling every time you make a prompt, hoping for the AI's output to work.

I'd be shocked if the developer wasn't actually less productive.

I feel like I can manage the entire stack again - with confidence.

I have less confidence after a session, now I second guess everything and it slows me down because I know the foot-gun is in there somewhere.

For example, yesterday Gemini started added garbage Unicode and then diagnosed file corruption which it failed to fix.

And before you reply, yes it's my fault for not adding "URGENT CRITICAL REQUIREMENT: don't add rubbish Unicode" to my GEMINI.md.

My problem is that code review has always been the least enjoyable part of the job. It’s pure drudgery, and is mentally taxing. Unless you’re vibe coding, you’re now doing a lot of code review. It’s almost all you’re doing outside of the high-level planning and guidance (which is enjoyable).

I’ve settled on reviewing the security boundaries and areas that could affect data leaks / invalid access. And pretty much scanning everything else.

From time to time, I find it doing dumb things- n+1 queries, mutation, global mutable variables, etc, but for the most part, it does well enough that I don’t need to be too thorough.

However, I wouldn’t want to inherit these codebases without an AI agent to do the work. There are too many broken windows for human maintenance to be considered.

I enjoy when: Things are simple. Things are a complicated, but I can learn something useful.

I do not enjoy when: Things are arbitrarily complicated. Things are a complicated, but I'm just using AI to blindly get something done instead of learning. Things are arbitrarily complicated and not incentivized to improve because now "everyone can just use AI"

It feels like instead of all stepping back and saying "we need to simplify things" we've doubled down on abstraction _again_

I've come to realise that not only do I hate reading stuff written by AI. I also hate reading stuff praising AI. They all say the same thing. It's just boring.

On the frontend, you have build pipelines, bundlers, CSS frameworks with their own toolchains, progressive web apps, Core Web Vitals, SEO, layout shifts, srcset/responsive images…

I've been making web stuff for a similar length of time as Mattias by the sounds of it. I started with Perl but moved to PHP 4 pretty soon after. I recognise this problem but I have different take.

All the complexity was there 20 years ago, but we ignored it. That doesn't mean it was simpler. It just means we took crazy (with hindsight) risks. Sure, there were no build pipelines like today, but we had scripts we ran to build things. There was Adobe Pagemill for making site wide changes before we deployed a new version. Back in the day we made those changes, did a very brief check that things worked locally, and then manually FTP'd files to a server, breaking it in the process because a user would see the site change as they navigated. Some of us would put up a maintenance page during an update effectively just blocking all the traffic. That's certainly 'simpler', but it's also much worse for the user, and on a site that did things with data potentially risked corrupting a user's records. It was incredible that things didn't break more often. Maybe they did and we just never realised.

We didn't have CSS frameworks but we certainly did have our own in-house templates, and they had separate toolchains. As time went on that toolchain mostly migrated to Wordpress and it's template builder plugins. Again, give me Tailwind over that mess.

We had Core Web Vitals and SEO in the form of Urchin Stats. We had layout shift but we called it FOUC. We had kind of had srcset, but it was implemented as a set of Macromedia Dreamweaver mm_ JS image preload and swapping functions. <picture> is a lot nicer.

Things are just better now. Writing web software is loads of fun. I also leverage LLMs in my code because they're awesome, but not to simplify things. I don't think the complexity is new. I just think it's visible now.

This author simultaneously admits, he cannot hold the system in his head, but then also claims he’s not vibecoding, and I assert that these are two conflicting positions and you cannot simultaneously hold both positions

I am also doing my pattern recognition. It seems that a common pattern is people claiming it sped me up by x! (and then there’s no AB test, n=1)

> I feel like I can manage the entire stack again - with confidence.

By not managing anything? Ignorance is bliss, I guess.

I understand it. I've found myself looking at new stacks and tech, not knowing what I didn't know, and wondering where to start. But if you skip these fundamentals of the modern dev cycle, what happens when the LLM fails?

> On the frontend, you have build pipelines, bundlers, CSS frameworks with their own toolchains, progressive web apps, Core Web Vitals, SEO, layout shifts, srcset/responsive images…

LLMs are successful in webdev because of unnecessary frameworks being piled on top of each other more in the name of job security than technical necessity.

<Here is a joke for you>

Factory work began when people could use other people as machines. For example, mechanized looms could weave cloth but each cloth weaving machine needed a machine to run it. So use people. Children, real slaves anyone. Slave labor. Thus began the Factory Age.

Now AI can replace people for repetitive labor. AI Can run the machines, it is the new Slave Labor. The problem now is what to do with all the freed slaves? If AI can make us the things that are needed, then how are we needed? We are not. As freed slaves, suddenly we are out of work. We are obsolete.

Unfortunately, for corporations that are now rushing to free themselves from the old, difficult, demanding, contentious slaves, they have missed one gigantic element of the equation. Hmmm. What could it be? Can you guess? What could possibly go wrong here?

Fortunately, for us - the freed slaves and factory workers - it turns out we are not just slaves after all. We were just trained to be slaves. So we have a future. If we can adapt to being free. And that is not a joke.

<End joke. I just made this up, nothing about it is true or even remotely serious. />

It's amazing to be able to try a bunch of ideas with very minimal cost. That being said, AI code assistants don't have eyeballs and they often make things that don't look very good. Craft, polish and judgement still matter.

Last paragraph resonated so deeply with me. Especially this:

```It’s also not the typing of code that I really enjoy, nor is it the syntax or structure or boilerplate that’s required to build anything. It’s the fact you get to build something out of nothing, writing code was just how you got there. And with today’s tooling, that saves a ton of time.```

I never really related with folks that code for beauty or are put off by how AI does the actual coding. The beauty is actually creating something, solving real problems, shipping, and (hopfully) winning. It might be cliche, but it is incredibly true for me to say that using AI feels like a superpower.

“I can reliably reproduce their coding standards, tone of voice, tactics, and processes.”

Doesn’t he mean the “AI tool” can reliably reproduce his friends coding practices? Hilariously ironic if so.

I'm trying to catch up with AI but it's difficult because most articles I find are kinda vague and there is a lack of clear examples.

It's always about prompting or how AI "is great" yadi yada but hardly any step by step examples.

I can easily ask gemini CLI to produce code for example. But how to work with AI in an existing codebase isn't obvious at all.

It seems also that for any serious use you need a paid subscription? It seems like the free models just can't handle large codebases.

Either the projects he's working on are side projects, and in that case I don't see why he would need to use the complex pipelines, just Vanilla JS and PHP still work super fine, even better nowadays actually, or the projects are professional ones and then to ship code written by AI is extremely dangerous and he should have resources (time and people) to do things properly without AI. So, I'm clearly not convinced.

I think it’s easier to manage full-stack development as a solo developer now even without AI.

Now TypeScript catches a lot of my mistakes before they reach runtime.

Now I have good enough browser automation testing tools to catch regressions in the frontend.

Now it’s quick and easy to run a specific database version for each app I’m working on with docker.

Now I can automate deployment to the cloud instead of having to rely on an entire IT department.

Now I have a scalable way to publish and consume reusable units of code as npm packages.

None of this was the case in what this author seems to think were the good old days. If web development seemed easy to him back then, I doubt he was working on complex projects

AI makes finishing projects easier. But I would steer away from starting them.

In order for me to be comfortable with a code base and consider it mine I need to have written the foundation, not merely reviewed in. Once the pillars are there, LLMs do make further development faster and I can concentrate on fun details (like tinkering with CSS or thinking about some very specific details).

Ironically I'm thinking the exact opposite. Now I can build stuff without dealing with the chaos in the frontend frameworks ecosystem...

As someone that only has sporadic pockets of deep time in my free time the thing that has been immensely helpful from an LLM coding point of view is mental model building. I can now much more easily get "into the flow" after being away from a codebase for a period of time by asking questions. For example, remind me where all the integration points for that API route is located. Or give me a rundown on this file. Etc.. It gets me back up to speed so much more quickly and makes me productive with limited amounts of time. It also means I don't have to try to carry this context around with me or I'll forget it.

A LOT of what is mentioned for today's frontend and backend developers is really companies dumping more and more responsibility onto developers so they can fire SEOs, Configurations Management specialists, DBAs, etc., so that the company can save more money while burning out more developers.

It's good that tools create the OP's positive feeling about being on top of the full Web stack again.

I just wish the tools that provides that feeling was a deterministic front-end code generator built from software technology and software engineering insights and not a neural network utilizing a pseudo-random number generator...

> Over the past two decades, I’ve worked with a lot of talented people

> I’ve seen the good and the bad, and I can iterate from there.

A bit of a buried lede, perhaps. Being in the industry for two decades, the definitions and fundamentals can rub off on you, with a little effort. There is a big difference between this and a decidedly non-technical individual without industry experience who sets out to do the same thing. This is not the advertised scenario for LLM vibe-coding.

I remember missing the fun with webdev, when everything got complex. That's when I tried Rails again, it's truly a joy.

In particular, and speaking as a backend engineer with zero web design skills, building things with charts/graphs is amazing nowadays! You can literally just operate at the level of "add another line representing the foo data", "add a scatterplot below it", "make them line up", "actually, make it a more reddish pink" etc. In the past I've had opinions about d3 and vega-lite and altair and matplotlib etc and learned how to use those ones at a superficial level at least. In my last personal UI with charts I didn't even ask it what framework it had chosen (chart.js is the answer)

Maybe it's just me, but the idea that the average web project out there is a complicated mess and thank God we have AI so we can finally think about the things that matter while AI deals with the mess... it makes me sad.

A product manager here. Thanks to AI, I was able to create my own website on Astro. I was so fascinated by web technologies, that I didn't realize when I created not just a website, but a blazing fast website with extensive amount of metadata generation (Json-LD, OG, microformats, Dublin Core, PRISM, RSL 1.0, Highwire Press, FAIR singposting, MODS generation) and so on. Thanks to this pet project, I'm now quite capable as a software architect of websites. And it is really fun!

We can all have fun being homeless I guess

Tackling layer of complexity often feels like this. I remember 2010 and my frustration of evergrowing complexity of networking backend programming (C++ mainly), and discovering Go. "Go made programming fun again" was a common phrase at the conferences back then.

I feel similar with web-apps development too, except we're not solving complexity here – we just outsorcing it to "AI-developer". None of the deficiencies of web stack are solved here. The worst part is that this complexity of web stack is mainly _accidental_ – i.e. coming from the tooling, not from the problem domain.

> Over the past two decades, I’ve worked with a lot of talented people: backend developers, frontend developers, marketers, leaders, and more. I can lean on those experiences, fall back on how they did things, and implement their methods with AI.

Will that really work? You interacted with the end product, but you don't have the experience and learned lessons that those people had. Are you sure this isn't the LLM reinforcing false confidence? Is the AI providing you with the real thing or a cheap imitation and how can you tell?

As someone who always dabbled in code but never was a “real” developer, I’ve found the same thing. I know the concepts, I know good from bad — so all of a sudden I can vibe code things that would have taken me months of studying and debugging and banging my head against the wall.

If you’ll forgive a bit of self promotion, I also wrote some brief thoughts on my Adventures In AI Prototyping:

https://www.andrew-turnbull.com/adventures-in-ai-prototyping...

To me, what sucks the most about programming is dealing with ecosystem issues. You want to write a little tool for personal use, but NPM starts acting out. Then you need to do something in java, which you don't use very often, and you get a giant maven error stack trace which you now need to try to understand. All of this frustration is gone since I use AI and I can focus solely on the thing I'm trying to accomplish.

Maybe its just me but I enjoy learning how all these systems work. Vibe Coding and LLMs basically take that away from me, so I dont think ill ever be as hyped for AI as other coders

Tailwind CSS has also been super useful. A vocabulary for style colocated with the elements works far better than an ever growing list of continuously overidden rules.

My guess is that the amount of total software people use will significantly increase, but the total amount of money made from SaaS will significantly decrease

I've replaced almost all of the App subscriptions with stuff I built for my self. The only subscriptions I pay for are things that are almost impossible to replace like online storage (iCloud) or Spotify

This is exactly how I feel about it. The cognitive load of starting a new project is so small now. It's also made it very easy to switch between projects, something that took way too much headspace to do on a whim in the before times.

You can still build web apps using more basic technologies like PHP, MySQL/Postgres, and just using vanilla JS.

One of the most frustrating things in my career is how over-engineered everything has become in the last 15 years.

Au contraire. Web development has always been fun, unless you add all the crap mentioned in TFA.

If you feel you need all that stuff to feel grown up, then I guess LLMs help a lot. But the barometer hasn't changed: make something that people love.

I kinda feel the same way, don't get me wrong, I'm a developer at soul level, I absolutely love programming, but I love more getting shit done, automating things, taking the human out of the equation and putting the computer to do it, AI lets me do that. I work in cybersecurity as a WAF admin, my job is 100% that, but I'm also the only developer so anything that needs to be scripted or developed I get to do it. One week I created 4 different scripts with Gemini Canvas to automate some tedious work, it took my I don't know, 3 hours? Instead of 1 or 2 weeks? Yeah sign me in.

Related question which might fit here so I'm going to try:

What is the absolute cheapest way to get started on AI coding a simple website? I have a couple ideas I want to test out and get out of my head and onto the web but have resisted for years because my webdev knowledge is stuck in 2004 and I've had no desire to change that. These are not complicated things (all static, I think) but... I hate webdev.

I am not really willing to pay to do any initial explorations, but if I like where things are going then, sure, I'll pay up. I have a decently powerful machine that can run things locally, but it is Windows (because I'm an EE, sadly), which does matter.

Yeah, I had same experience, these days I just vibed some stuff in web, i do think vibe frontend/web is great for backend developer. Checkout the one just finished yesterday. https://slsqp-vis.shuo23333.app/hs_all_cases_viz , a slsqp solver visualization.

And even more fun with tools/services like exe.dev!

Also apparently the combined of Google Antigravity/$20 Google AI plan/Opus 4.5 is blowing up the AI community lately in Reddit. Apparently the limits right now of Opus thru Antigravity are insanely generous/incredible value. Obviously this could change at any time but perhaps Google has the funds/resources to continue to provide value like this in an attempt to capture the dev userbase / win the AI war.

Been using GitHub Copilot to handle the tedious webpack/babel config files and it's a game changer for modern web dev. No more spending hours debugging build pipeline issues - it generates 90% correct configs that just need minor tweaks.

Before I clicked on this I was optimistic and thought this was going to be about how we've turned a corner and the web stack pendulum is now swinging back to the easier days before frontend frameworks.

Meanwhile, I've been feeling the fun of development sucked away by LLMs. I recently started doing some coding problems where I intentionally turned off all LLM assistance, and THAT was fun.

Although I'll be happy to use LLMs for nightmare stuff like dependency management. So I guess it's about figuring out which part of development you enjoy and which part drains you, and refusing to let it take the former from you.

Agree, I developed a 150K line stock analytics Saas that started with the will to provide my son with some tools to analyse stocks.

I enjoyed this experience of CLI coding so much that I developed Market Sentiment parsing 300,000 business articles and news daily, a dividend based strategy with calendar of payouts and AI optimised strategies to extract every drop of interest, an alert system for a strategy you backtested in the playground and its key triggers are tracked automatically so you can react, an ETF risk analysis model with external factors, all quant graphs and then some, time models with Markov, candlestick patterns, Monte Carlo simulation, walk forward and other approaches I had learned over the years. There is much more.

I know you don't measure a project in terms of lines of code, but these are optimised, verified, tested, debugged and deployed. There are so much features, because I was having fun and got carried away. I'm semi-retired and this is like having my web agency back again.

I used to program in GRASP... I have a data scientist certification, did a lot of Python, Machine Learning, NLP, etc. I really enjoy the prompt based development process as it seems like you are reaching the right resource for your question from a staff of experienced dev. Of course you need to check everything as a junior dev always creeps in when you least expect it. Especially for security. Discuss best practices often and do your research on touchy subjects. Compare various AI on the same topic. GROK has really caught up. OpenAI has slowed down. CLAUDE is simply amazing. This AI thing is work in progress and constantly changing.

I have a noticed an amazing progression over the past year. I have a feeling their models are retrained, tweaked on our interactions even if you asked for them not to use the data. The temptation is too high and the payoffs abound in this market for the best AI tools.

I'm building a code factory now with agents and key checkpoints for every step. I want to remove human intervention from multiple sub steps that are time consuming so I can be even more productive in 2026...

Going in 2026, the frontend has many good options, but AI is not one of them.

We have many typesafe (no, not TypeScript!) options with rock solid dev tooling, and fast compilers.

AI is just a badaid, its not the road you want to travel.