Programming is alien. It’s fundamentally hard to comprehend, because the computer will do exactly what you tell it to, regardless of what you mean. You have to think for the both of you.

GOTO 0

Why should they? Less users are programming anything, but more people have become users of computers in the first place. And we have more users of computers, precisely because the levels of abstraction do not require the ordinary user to program anything. Today’s ordinary user is more “ordinary” than fifty years ago. This development of making a tool or subject more accessible to the layman, by hiding the complexities with abstractions and yet allowing more skilled users to gain advantages by peeling away the abstractions, is present in many different fields throughout the history of mankind.

If you look closely, it is not really surprising. Not even a problem at all. In fact, if you have the simple understanding that maybe somebody doesn’t want to program, not because they are a stupid idiot or a lazy normie consumer, but because they simply don’t give a shit about it, follow other interests and can contribute to the world with other skills, then the observation that most users are not programming anything, is insanely unproblematic.

It will only get worse with the phone and tablet generation and LLMs.

College computer science courses have had to go back to teaching students what computer files and folders are. A lot of computer programs have simplified themselves as ease of use overtook features as a driving factor for use.

Most people don’t know how to program because they don’t know the basics of computing.

I dunno about this; IME even when it was highly approachable most people didn’t do it. I was around back then, got my first Commodore in '84, and even the Geek / Nerd circles were mostly just for people swapping copies of commercial software. It wasn’t any better when I graduated High School in '91 and even in College almost no one outside of STEM was doing any programming.

It wasn’t and still isn’t a popular activity.

140 years after the automobile, most drivers can’t or won’t repair their car!

50 years after BASIC and nothing is written in BASIC.

To replicate its success from the 80s we would need a language that is simple enough for everyone to learn but actually performant and powerful enough to write an entire operating system and application stack in. Then perhaps non-programmers would feel more inclined to look under the hood, see how things work, and change their program’s behavior.

The problem though, is that for any reasonably complex system or application, you need to use structured programming. This is what enabled the levels of abstraction that we use to break down programs into layers that can be understood in pieces, and it is what makes large complex software possible without ending up with a mess of spaghetti.

However it is these abstractions that turn a software’s code into a Domain Specific Language, and endless APIs that need to be learnt and understood by the programmer.

For programmers it is normal to us that when we want to work on a new codebase we have to learn the idiosyncrasies of the codebase, and learn its DSL and the APIs that it uses, or exposes. But for a non-programmer, this would essentially feel like learning everything about programming from scratch. They would have to become a programmer and develop maintainer skills just to understand what they want to change. (This is why programmer is still a job).

Perhaps the real value of BASIC was that without structured programming, every program was just a pile of spaghetti that even a child could pull apart with a fork.

In my experience it doesn’t matter how accessible the language becomes, most people find the precision required to make machines behave in a desirable way is exhausting or alien to them.

This isn’t any kind of failing though. I’ve come to see how organising modern businesses (with processes, regulations, standard etc) is a kind of “programming”. And there are many who are good at that (designing human processes to automate goals) where I completely flounder, even with the help of the ‘right’ training, books, coaching etc

Sixty years ago as this article was published in 2014

Today’s users have massive amounts of computer power at their disposal, thanks to sales of billions of desktop and laptop PCs, tablets and smartphones. They’re all programmable. Users should be able to do just enough programming to make them work the way they want. Is that too much to ask?

Smartphones – and to a lesser degree, tablets – kind of are not a phenomenal programming platform. Yeah, okay, they have the compute power, but most programming environments – and certainly the ones that I’d consider the best ones – are text-based, and in 2025, text entry on a touchscreen still just isn’t as good as with a physical keyboard. I’ll believe that there is room to considerably improve on existing text-entry mechanisms, though I’m skeptical that touchscreen-based text entry is ever going to be at par with keyboard-based text entry.

You can add a Bluetooth keyboard. And it’s not essential. But it is a real barrier. If I were going to author Android software, I do not believe that I’d do the authoring on an Android device.

When Dartmouth College launched the Basic language 50 years ago, it enabled ordinary users to write code. Millions did. But we’ve gone backwards since then, and most users now seem unable or unwilling to create so much as a simple macro

I don’t know about this “going backwards” stuff.

I can believe that a higher proportion of personal computer users in 1990 could program to at least some degree than could the proportion of, say, users of Web-browser-capable devices today.

But not everyone in 1990 had a personal computer, and I would venture to say that the group that did probably was not a representative sample of the population. I’d give decent odds that a lower proportion of the population as a whole could program in 1990 than today.

I do think that you could make an argument that the accessibility of a programming environment somewhat-declined for a while, but I don’t know about it being monotonically.

It was pretty common, for personal computers around 1980, to ship with some kind of BASIC programming environment. Boot up an Apple II, hit…I forget the key combination, but it’ll drop you straight into a ROM-based BASIC programming environment.

After that generation, things got somewhat weaker for a time.

DOS had batch files. I don’t recall whether QBasic was standard with the OS. checks it did for a period with MS-DOS, but was a subset of QuickBasic. I don’t believe that it was still included by later in the Windows era.

The Mac did not ship with a (free) programming environment.

I think that that was probably about the low point.

GNU/Linux was a wild improvement over this situation.

And widespread Internet availability also helped, as it made it easier to distribute programming environments and tools.

Today, I think that both MacOS and Windows ship with somewhat-more sophisticated programming tools. I’m out of date on MacOS, but last I looked, it had access to the Unix stuff via brew, and probably has a set of MacOS-specific stuff out there that’s downloadable. Windows ships with Powershell, and the most-basic edition of Visual Studio can be downloaded gratis.

I only used BASIC to open infinite windows to crash Windows 95.

Working with some proprietary no code tools at the moment, and, yea, not letting people just program in a decent language is a mistake.

Man who celebrates the invention of the wheel laments that people won’t reinvent the wheel

I can only think of one example where some simple programming skills could benefit ordinary users: Home Automation. All the more difficult stuff is already neatly packaged into ready to use modules, and the user doesn’t have to worry about the ZigBee protocol or APIs or network ports to turn on a light bulb. Here some knowledge about conditionals, variables, loops can easily be used to program useful automations.