Video Wendell might be interested in (now programming Vs past)

HI @wendell ,

Saw this video pop up in my recommended and thought you might enjoy it. All the best, Chris

1 Like

He’s not wrong, but I’m not going to say that we should go back to those days.

Perhaps we should change how we teach programming?

Disclaimer: I am not a programmer. Nobody pays me (primarily) to write code. But I do write bits and bobs occasionally as a hobby. And I’ve had code - C# executables, Java bytecode and some proprietary languages - running in production environments, earning money for companies. I solve problems, and on rare occasions where problems can only be solved by code and that code is within my abilities, I will happily write that code.

Programming was fun because we were doing less, with a lot less.

I’ve been going through some old floppy disks and was looking at some code I wrote in 1993-1995. It’s in QuickBASIC 4.5 (no, not QBASIC that came with DOS, this is compiled), and it’s atrocious. But what stood out for me was that the language itself did so little.

For example, I’d needed to list files from the disk. The official Microsoft recommended method for that was to shell out to command.com and use DIR redirected into a file, then read that file.

I’d rejected that idea and wrote my own FindFirst/FindNext subroutines.

Today people learn frameworks as much as they learn programming. This is especially true in web development, but it seems to be the case generally.

I think the change occurred in the ate 90s. Java comes along with a fairly extensive standard library. The .NET Framework follows. Perl had almost built the early internet, but loses out to Python - which has “batteries included” rather than a mess of modules downloaded from CPAN.

Basically back in the day if you needed a library to parse something, you either wrote it or paid someone a lot to write it for you. Today, there’s either something already there to do it, or you can quickly pull in someone else’s code from GitHub.

That changes what people are taught. And what they teach themselves, because they only solve the issues that they’re interested in.

We used to teach people what they’d need to solve problems more generally.

Now companies employ people to solve a specific problem with a specific library in a specific environment.

This specialisation is partly necessary because computing is just so much more complex and capable these days.

For example, there’s an actual quiz on AWS service names & logos. Every one of those services is sold on the idea that they’re saving developers from writing this themselves - which is a great thing. Until you find yourself having to move to Azure or GCP, and now what you learned is quite possibly useless.

In focusing on very specific solutions (and environments, and frameworks) we’ve decided that a broader knowledge is somehow unnecessary.

The same thing can happen in sysadmin - focusing only on one technology - but I think it’s just much worse in development, because developers have spent years building conveniences for themselves (like package management systems) that make it easy to construct a walled garden for themselves.

1 Like

Quite honestly I do not know what he is on about. Like all these things he talks about are literally what you still learn around here for a Bachelors degree in university. Some universities teach Assembly, pretty much all computer architecture, you usually learn C, my universities entry level programming course is literally Pascal for the reasons he mentions and only after you learn Java and the likes.

Maybe what he talks about is more a US thing but universities here basically give you a computer history crash course for the Bachelors degree, not for historic reasons but it makes sense when you think about didactic methods.