Discussion about this post

User's avatar
awbvious's avatar

I have come to a conclusion from this substack article and the TESCREAL essay by ex-Google-AI ethicists. The common bedfellows of TESCREAL are racists, eugenicists, fascists, and totalitarianists… It’s not so much that they all think they are right with less than complete information. Everyone thinks that (at least enough to proceed with their own decisions). What's important is that the worst of the TESCREALists and these bedfellows willingly dismiss very strongly held, near-universal, pro-social rules of our shared social contract: do not lie, steal, cheat, kill. And the bedfellows of TESCREALists should be telling enough to discourage all kinds of TESCREALists. That said, every religious extremist is appalled by the religious extremists of other religions, and still do not change. And moderate religious people are often appalled by the extremists within their own religion, but still remain adherents. So, perhaps we can at least use these bedfellows as a pretty good indicator for the rest of us to be wary. Understanding of moderates, but wary of where it can lead.

I think this paragraph basically puts it best: “Furthermore, this is a problem that compounds on itself, because a rationality that excludes the irrational in human nature cannot even rationally solve humanities problems, because it prevents thinkers from understanding themselves, including their limitations.”

Rationalism is not rationality. Not surprising. 1984’s Ministry of Peace wasn't about peace. The Nationalist Socialist party was very much not socialist. The Patriot Act wasn't very patriotic. And Citizens United was very much not for the benefit or unity of most citizens.

“It is a mathematized and instrumental view of the world-as-computer - and more importantly, of human beings as computers.”

Similarly, I say it sounds like the concept of human beings as computers is very much not about considering real computer systems.

I got nothing against the idea that people are computers. As long as we realize we have buggy, old code that rarely gets updated, with an SDLC that is neither agile nor phased, no visible source code and certainly no inline comments, and what little documentation exists is definitely not written by the developer. Further, the specs of the hardware have necessitated quite a few lines of spaghetti that only survived because they managed to stick to the wall enough to keep the entire system from shutting down.

And I think you can use the “humans are computers” concept to completely justify a philosophy of constant honesty, fairness, kindness, non-violence, and tolerance.

It's probably not hard to convince someone that people would rather work with and interact with someone who's honest. And, further, convince someone that being honest around people will create a reputation for yourself that will be beneficial to accomplishing shared goals. The one bit that might be tricky is convincing someone that they should be honest even when the odds of a lie being found out seem very low.

That is where the idea we are computers with iffy code and constrained hardware can help. Since we can only run so many processes at the same time, we need shortcuts. As mentioned previously in a comment, emotions and feelings are shortcuts. A subroutine is kicked off at the operating-system level to constantly flash a warning to plug into an outlet that gets more incessant and harder to dismiss as your battery level gets lower. So you eat a cheeseburger and stop being hangry.

There are also habits. Humans are creatures of habit. Again, because of limited specs. If you brush your teeth first thing every morning, and it's the same steps every time, it's quite likely you'll be spitting out toothpaste into the sink before you even realize you woke up. Actions become almost automatic, you don't even think about it, thus freeing up some processing resources to consider what to wear while you are swishing mouthwash.

But, let's say you don't have this good habit. You decide from time to time you'd rather have that extra five minutes in bed, such as on weekends after a long bender. Then one workday you wake up, forget even though it is a workday, get to work, and knock out your boss with your halitosis.

Frankly, I don't mind bad breath. I also don't brush my teeth nearly as much as I should. But I make a point of constant honesty hygiene. Your boss probably won't hold your breath against you, probably won't care beyond the few seconds of nasal repulsion. But a lie, she'll remember.

DRY as they say in code. You don't want errors, certainly not the kind an end user might encounter. Such that might make them think their UX with you is not so WYSIWIG. As such, just keep referencing your “let a=a” function. Or better yet, make that declaration to be honest global and static.

Lastly, you can only see so much in your task manager or console log or whatever metaphor you want to use. Just as you have limits on what you can do with your resources, there are limits of what you can know is occurring with your resources.

People don't want to think of themselves as bad people. At the very least that's just another thought to clutter up your processor from getting things done. Depression is crippling, for example. To keep a memory leak of “amibad.exe” from happening we have this automatic cleanup program “convincemyselfimgood.exe” that ideally runs very sparingly, because amibad.exe is not a bad thing to run. Now if you happen to be looking at your task manager you might catch either blip at the top of the visible part of the list of processes. But looking at your task manager is a bit hard in the moment, and doing so will be much less likely if you are in automatic habit mode. If you start habitually lying, can you be sure that you are going to catch that “convincemyselfimgood.exe” running in the background and killing “amibad.exe” before it can tell you that, yes, you are being bad?

My point in all this is to say you can think of people like computers, as long as you remember that there is no such thing as perfect code. But simple code can be pretty darn good. I'm not saying there are exactly ten commands in a universal COMMAND.COM that everyone should follow. But you'll notice certain ones among all the well known operating systems such as: do not lie, do not steal, do not kill. And these are ubiquitous because they work wonders with our hardware.

No posts

Ready for more?