[sublinear]

I'm gonna be honest here. I don't know what a non-technical person is anymore. The only people I can truly label that way are a subset of the people now near or at retirement age.

It's almost 2026. There are more people who know how to code than ever before. This stuff is taught in every school now. Everyone has access to AI to help them if they get stuck. If someone under 50 is unwilling to work I am unwilling to employ.

[weitendorf]

A huge number of those people only interact with computers as a consumer. Beyond that, maybe schools assignments, texting and other social media, light email, and video games (eg through steam or a console). There is a big gap between that and someone comfortable using git.

Don’t be an asshole to them about that, think about how many developers would do anything it takes to avoid calling someone on the phone. Obviously they can learn it, but they know they’re going to be bad at it for a while (true for both git and phone calls) and they don’t know how long it’s going to take, or the extent of what they don’t know.

The thing about software companies is that they know how to automate and build stuff so why invest the time in learning a CMS if it’s something they could quickly solve for their own use case? Well, the same applies to people who just want to point and click and write, wondering whether it’s worth it to learn what a rebase does.

[sublinear]

> think about how many developers would do anything it takes to avoid calling someone on the phone

Think about all the developers we force into that situation all the time anyway.

> they know how to automate and build stuff

To an extent, yes, but as the author said "content management" is a complex problem.

> wondering whether it’s worth it to learn what a rebase does

This is the crux of the problem. Versioning is fundamental to project management for the kind of project you'd use a CMS for, yet with a CMS everyone is too siloed and the oversimplified interface ruins any chance of doing better. Any CMS is a dead end that leads to chronically incorrect assets, incomplete patches, broken links, etc. This is also generally true for many other low/no-code solutions.

I'm not saying the "non-technical" people need to work directly in git, but they do need to be familiar with this kind of workflow when discussing with developers, and developers are absolutely still needed. Any CMS workflow is too restrictive. Nobody experienced and sane would prefer it over a git based solution unless they're being bullied into using a CMS. It's been like this forever and no CMS has ever been able to overcome this reputation.

At some point one needs to ask why a CMS is preferred and time and time again the answer is only cost cutting. In any other business decision that reason wouldn't be good enough. CMS products only exist because of neglect, ignorance, and cheapness.

[collingreen]

I've been shocked when talking to younger people who have -never used a computer that wasn't their phone-. People genuinely interested in cs degrees that needed to be taught how to use the computer first. These are not "dumb" or "unwilling" folks they just have grown up in a way I don't recognize and didn't expect. I assume it's the equivalent of how I've gone to a library to do research at most a half dozen times in my life despite doing lots and lots of reading, learning, and writing - my world just does not look like "do that at the library" anymore even though probably folks just 10 years older were almost exclusively there.

I think you're painting with too broad of a brush if your goal is an accurate model of the world here.

[antonvs]

> I'm gonna be honest here. I don't know what a non-technical person is anymore. The only people I can truly label that way are a subset of the people now near or at retirement age.

This is a parochial viewpoint that only describes the bubble you're living in.