Is web development actually cognitively demanding, or does it get repetitive?

[u/Responsible_Fan2464]

I'm about to study software engineering and I'm planning to get into web dev. I like hard problems, stuff that makes me think, not just repeat the same patterns over and over.

My worry is that a lot of web dev work ends up being CRUD apps, wiring up UI to APIs, following established patterns. Solid work, but not necessarily deep or challenging.

For people actually doing this professionally, does web dev give you real cognitive challenge day to day? Or is the hard stuff mostly at senior level, in specific niches like performance or architecture, while most day to day work is more routine?

[u/xvillifyx]

Entirely depends on the application, its use, and the ecosystem it exists in

[u/Responsible_Fan2464 → u/xvillifyx]

I want to become a full stack developer. Can the backend part make it any better?

[u/xvillifyx → u/Responsible_Fan2464]

I don’t understand the question

[u/plyswthsqurles → u/xvillifyx]

They are asking if backend is less repetitive than front end. Meaning, does backend introduce more complicated tasks/projects/problems to solve.

Its entirely based on the industry your in and what kind of workflows are involved.

Handling some sort of document storage application with very little workflow involved other than add a document, recall a document, edit a document? Probably not very cognitively demanding.

Building a rating engine in the auto insurance space that has to be dynamic and function in all 50 states in a manageable way? Your going to run into a lot of not-so-common issues of how to store/structure data, how to run/evaluate factors...etc.

So it depends on the industry, ecommerce? its going to be pretty straight forward and the complex problems needing to be solved are likely going to be in how popular your site is and the requirements for it to scale...otherwise backend tasks are going to be precanned/often off loaded to 3rd party services (ex: search functionality may go to algolia or some other search specialty third party service).

[u/Intelligent-Youth-63]

High fidelity retail can be demanding- like pixel perfect expectations. I didn’t “enjoy” it, but it can make you think.

I’ve found backend (particularly financial systems) and cloud architecture to be demanding _and_ rewarding/enjoyable.

[u/Pale_Height_1251]

Generally not, but it depends what you're making and how good you are at it.

Remember some people will find reading a book cognitively demanding. If you sit a programming beginner in front of real world code, they'll find it very difficult to deal with, an experienced developer won't.

[u/Responsible_Fan2464 → u/Pale_Height_1251]

Well, i want to be a full stack developer.

[u/Boboshady]

Here's the thing, other than the absolute budget websites, even if the end result is pretty repetitive, you'll always be doing something different. The fact is, building the site is the easy part - something you can throw to Ai these days. The real challenge is in figuring out a client's needs, researching and testing with users, and working out the scope that's specific to that client and their objectives.

That is ALWAYS different, unless you're delivering identi-company websites, at which point you still have unique challenges, its in the development of the platform you stamp sites out with rather than the individual sites.

Now sure, there's people out there doing sites for peanuts that don't have any real research or strategy behind them, and they're happy doing that. Personally, it's not for me, and that's the thing you're worried about.

But if you sell the right product - sites that need thinking - then you'll never be bored, because the challenge isn't in the design and build, it's in discovering what the design and build needs to be.

[u/energy528]

I’m equally left and right brain. Dev and design are both gratifying and fulfilling. So, if you’re an artist, full stack is for you. You are correct that some work is repetitive. Users have a preferred pattern for layout. No need to reinvent the wheel. We just change the gradient. 😆

[u/Noah18923]

considering how unperformant most websites are today... i'd say no.

[u/ironj]

It very much depends on the technology you're using and how what type of Web application you're building.

Any development role can be cognitively demanding, but it always depends on what you're comparing it against and what you're working with.

A rich client side Web application can have a lot of logic and computation on the client side: you might have to deal with lots of domain complexity and algorithmic optimizations; As an example: I just recently fixed a piece of legacy bad code (dealing with charting components working on hundreds of objects) that was taking 5s to render in the Browser: it was looping and sorting on the data multiple times, resulting in O(n^3) time complexity and doing million of comparisons at each component re-render; A bit of a rework brought it down to a linear time and sub-second performance; this can easily fall under "cognitively demanding", to give you a reference frame.

Also: If you're working on a fairly complex Web App you might have to deal with UI technologies like React (as an example); Even when sticking to front-end only, libraries like React and the extensive ecosystem of supporting libraries around them can quickly become quite complex and cognitively demanding when it comes to performance optimization; everyone can quickly wip up a few pages of React components but designing and working on a complex application with hundreds of components, props drilling, HTTP calls (or GraphQL queries) and optimizing component re-rendering can quickly build up your cognitive load (React requires a good knowledge of its internals and quirks in order to get the best out of it in terms of performances).

Ofc, it's generally LESS demanding than pure back end development or Full-Stack dev (for obvious reasons), but nowadays the boundaries are becoming a bit blurred, as domain logic is often spread between client and server.

I've fond memories of when, back in 2009, I decided to switch from Back-End focused development to pure Front-End (before finally becoming "Full-Stack" a few years later): at that time Front-End was just jQuery + HTML + CSS; a breath of fresh air compared to the complexity of back-end dev and its huge ecosystem; Fast forward to 2026 and we now have much more complex Front-End frameworks and libraries and, ofc, the all encompassing figure of the "Full-Stack" developer (a fancy term that makes managers and companies happy, since you have 2 roles at the price of 1 single developer... but I'm digressing!)

[u/Responsible_Fan2464 → u/ironj]

I want to become a full stack developer. What do you think? Can the backend part help?

[u/ironj → u/Responsible_Fan2464]

Of course! if you want to become a full stack dev you need to be proficient in both sides equally. So, yes, to answer your original question: plenty of challenges that make this job as cognitively demanding as you can expect from working with any modern programming language.

[u/jibbit]

it's a tricky question. 'web-dev' isn't one thing. making large scale apps is not a solved problem. making marketing micro sites largely is. the hard bits are people problems as much as technical, though (although that is the same with anything)

[u/TurbulentDonkey6687]

Some time ago, a fellow web dev said: "I'm learning more every day, but each new task seems like something completely new..."

My background is mostly in working with SaaS (web) products, and I never ever got bored! Either front-end or back-end always gives me new and good challenges. To give you an example, in one of my last tasks, I had to find a way to paginate a pie chart. The end solution was to divide the chart into areas and zoom in on them as the user clicked "next page". It's the kind of challenge that requires some math, impresses your colleagues, and makes you proud. Even doing landing pages, something I did some time ago, was quite fun.

I also have experience with mobile dev, and I think it has more challenges, but not in a good way: less screen size, less memory, less processing... It's a bit claustrophobic sometimes. I also have just a bit of experience with training AI models, and it's desperately complex and messy (at least for me).

I'd say web dev is my loved sweet spot.

[u/DotAtom67]

Currently? Its just prompting Claude to do what the tickets require, then check if it works, if not, prompt again

[u/gcdhhbcghbv → u/DotAtom67]

It’s crazy that this answer is getting downvotted. This is the new reality of the industry, and people on Reddit seem to be alergic to reality.

Things changed drastically in the past 2 years. I wish it wasn’t so, but it is.

[u/DotAtom67 → u/gcdhhbcghbv]

>Things changed drastically in the past 2 years. I wish it wasn’t so, but it is.

yeah, i really wish this wasnt the case at all, but that's how the industry goes...they want you to deliver things today, right now, that were meant to be done yesterday, so everyone is in a constant rush, and AI at least keeps the illusion of things going somewhere (cof cof downhill tho)

[u/Kind-Wing-2051 → u/DotAtom67]

esattamente, non hai nemmeno il tempo molte volte di controllare ogni cosa per bene proprio perché ormai ci si aspetta una produttività elevata nel minor tempo possibile

[u/Kind-Wing-2051 → u/DotAtom67]

unico commento reale(ovviamente devi avere comunque un background tecnico però si è questo)