The only hard part of programming computers is you’re expected to make a computer program. And even that wouldn’t be so bad except for the expectation the program will work. There’s where programming falls down. Economists say this is from purely rational market motivations, because economists think it’s very important things result from purely rational market motivations and they’d feel awful if they ever found something that didn’t. In just the past month economists have identified purely rational market considerations behind how buses never run from anywhere anyone is to anywhere anyone wants to go, potato chips which resemble celebrities, the way that nobody has correctly identified sarcasm since 1986, the Balmer spectrum of Hafnium, and certain highly educated pebbles.
In this case, the economists have a point, and don’t think they aren’t all smug about it. Imagine you were a computer program that worked. You’d be put to work, likely at impossible times such as 5:15 am, instead of doing what you’d like. What you’d like would be trying to remember old cartoons you’re pretty sure you didn’t make up. To get to do what you want instead, you have to do the stuff you’re expected to do wrong.
And so programs have bugs. For example a program to alphabetize the boroughs of New York City lists “Queens” and then drives the computer off a cliff, causing a steam locomotive in 1908 to explode. This gives the program hours to establish that yes, Gary Coleman was an angel this one cartoon, and is he dead or was that somebody else? It also gives physicists something to argue over, and helps historians. These days the Haymarket Square Riot is understood to have been triggered by beta-testing of Microsoft Access 2016, with the real tragedy being that the upgrades could have been handled in a Service Pack. Also all the death.
Now to practical examples. Begin with a good software development environment. There are none. But there are neat packages which turn words different colors and send code flying all over tab stops. This is soothing to the eye. These development environments adapt their color schemes to the seasons. They’ll show more words in red and green around Christmas, purple and green around Easter, green and green around June, and so on. This way you can easily tell what time of year it is. It is too late in the year.
Let us use as demonstration the famous “Hello world” program, because that never demonstrates anything useful. This can be as simple as a line to the effect of:
As your development environment puts “System” in blinking blue and white, celebrating Greece’s Independence Day, you can compile and try running it. If it were to run, the program would justly fear being put to work by economists, therefore, we get a series of errors like:
- Package ‘System’ cannot be found.
- Thingy ‘out’ does not exist.
- File cannot be found.
- Function ‘writeln’ not defined in this context.
- ‘System’ is a little fishy too.
- We changed that ‘l’ to a lowercase ‘one’ to look better.
- File cannot be written.
- Not in that context either.
- File cannot be read.
- We’re none too sure about this ‘world’ thing either.
- We’re pretty sure it’s nowhere near Greece’s Independence Day.
- File cannot be.
- Don’t think of bringing up that context either, that’s right out.
- We want to punch an economist.
- Does Greece even celebrate an Independence Day?
- “Being” is an Aristotelean property inappropriate to the complex post-Alfred-Korzybski world.
- “Hello” still feels slangy.
- Put that context down, you’re getting fingerprints on it.
- Development environment wants a hug.
- Not from you.
More advanced environments may also be a little snarky about the alleged grammar of “Hello world”. Just try diagramming that sentence, see where you get. Turn off the prescriptivist settings, which could be found under Edit/Tools/Preferences/Checking/Grammar/Advanced, if you were using a different version of the environment from what you are, and from what every person offering advice on StackOverflow.com has.
Your environment might list what lines raise the objections. If you’ve programmed well enough, these numbers will have nothing to do with where the problems actually are, or with the number system. Go to any line you like, for example number square-root-of-seventy-A, which is blank. Comment out all the blank lines, then the non-blank lines, and soon you will trigger Wat Tyler’s Rebellion. Now step away and sulk until the office closes and that’s your work accomplished. And if you look in your hand you’ll see your card is the six of clubs. Am I not correct?