I see your point and I agree that ultimately web design will be incredibly hard to automate, probably harder than almost any other programming domain, where people will likely stay for accountability reasons.
But the thing is that for the vast majority of web pages/applications, it barely matters what does the design look like, especially for B2B/internal apps. All the dashboards, CRMs, tracking tools, etc -- these exist mostly for functional requirements, so the design just needs to be inoffensive.
B2C market might hold longer, but ultimately there might emerge some sort of higher-level design specification language which would sidestep the original problem or being too recognizable.
This is like saying the design of your mobile operating system barely matters as all you use it for is to open Youtube and a browser. Design is everything when building a product people interact with.
> I don't think historical "sorry for the wall of text"s by famous intellectuals is the dunk on walls of text that people seem to think it is.
It is a bit overused phrase, but I find it to be absolutely correct -- to make something concise without losing meaning and not being overly dry is both a skill and also lots of effort. I don't think it is impossible, it is just that often it is not worth it.
Prototype is usually something working, while spike can be pure research (e.g. validate that APIs are feasible and enough, or that something satisfies requirements). Prototype is usually more polished/usable. Experiment in my mind is something which user-facing but not in stable yet.
So for me they are differentiated enough, but could be that I am just used to it.
An experiment doesn’t say anything about user facing or not. I do tons of them when reverse engineering poorly documented hardware and APIs to determine if the thing I’m trying to do is even supported.
In general, yes, but I would say "experimental features" is a pretty widely used term, so in my mind the association with something user facing is strong.
> So you end up doing a bunch of weird commentary on say a book where you as a teenager have no idea where to place it. Like if you read Dickens, will you know enough about the industrial revolution, the condition of cities at the time, and such? Will you know what kind of thing the characters would care about?
Well, you probably had some history classes, maybe watched a movie or two, heard something, maybe asked your parents or the teacher, etc. Also the books usually do set the scene by describing the environments, so you can infer from them.
It also works the other way, after reading that book it gives you some foundation for when you consume other media related to that period/place.
For women it is much harder as they don't even have an option to put less energy into kids at all, society pressures and berates them if something is off (men might get a comment but largely it is ignored and accepted), so I can totally see why she feels this way, _especially_ for a side thing.
The thing about taxi drivers is that they have something at stake, while video games have no fail state effectively. You can be punished in-game, but overall it does not matter.
Also video games in general are pretty derivative, so playing the same genre probably won't help much after a certain point. But playing different ones can be very helpful, I imagine (same with other mediums).
I assume there is enough variation to be aware of -- seasons change, constructions, car crashes, so you need to alter the route a bit. Today you have the maps with navigation, but I assume you still need to be quite aware on where to park, where is the best entrance to some places, etc. So you basically need to keep some fresh info on top of your mind.
The argument basically boils down that in non-component approach (so not a modern web framework) it is harder to reason if you use tailwind classes. The rest is some serious bikeshedding, imo.
I personally started with atomic CSS framework (that was before Tailwind, we had our own) and it has both ups and downs, but overall it is really nice to use once you learn it, and it is not really hard to do so. It does not do anything to enforce variables, but that's why you need to roll either your own layout primitive components or some classes.
I have a sizeable collection of CDs and during last year wrote my own CD reader and a ripper CLI.
As ridiculous as it sounds, but there is some intent in doing all of that and listening to the files on your hard drive. We have a vynil/CD player as well, but they are not at my workplace.
But the thing is that for the vast majority of web pages/applications, it barely matters what does the design look like, especially for B2B/internal apps. All the dashboards, CRMs, tracking tools, etc -- these exist mostly for functional requirements, so the design just needs to be inoffensive.
B2C market might hold longer, but ultimately there might emerge some sort of higher-level design specification language which would sidestep the original problem or being too recognizable.