site banner

Culture War Roundup for the week of December 19, 2022

This weekly roundup thread is intended for all culture war posts. 'Culture war' is vaguely defined, but it basically means controversial issues that fall along set tribal lines. Arguments over culture war issues generate a lot of heat and little light, and few deeply entrenched people ever change their minds. This thread is for voicing opinions and analyzing the state of the discussion while trying to optimize for light over heat.

Optimistically, we think that engaging with people you disagree with is worth your time, and so is being nice! Pessimistically, there are many dynamics that can lead discussions on Culture War topics to become unproductive. There's a human tendency to divide along tribal lines, praising your ingroup and vilifying your outgroup - and if you think you find it easy to criticize your ingroup, then it may be that your outgroup is not who you think it is. Extremists with opposing positions can feed off each other, highlighting each other's worst points to justify their own angry rhetoric, which becomes in turn a new example of bad behavior for the other side to highlight.

We would like to avoid these negative dynamics. Accordingly, we ask that you do not use this thread for waging the Culture War. Examples of waging the Culture War:

  • Shaming.

  • Attempting to 'build consensus' or enforce ideological conformity.

  • Making sweeping generalizations to vilify a group you dislike.

  • Recruiting for a cause.

  • Posting links that could be summarized as 'Boo outgroup!' Basically, if your content is 'Can you believe what Those People did this week?' then you should either refrain from posting, or do some very patient work to contextualize and/or steel-man the relevant viewpoint.

In general, you should argue to understand, not to win. This thread is not territory to be claimed by one group or another; indeed, the aim is to have many different viewpoints represented here. Thus, we also ask that you follow some guidelines:

  • Speak plainly. Avoid sarcasm and mockery. When disagreeing with someone, state your objections explicitly.

  • Be as precise and charitable as you can. Don't paraphrase unflatteringly.

  • Don't imply that someone said something they did not say, even if you think it follows from what they said.

  • Write like everyone is reading and you want them to be included in the discussion.

On an ad hoc basis, the mods will try to compile a list of the best posts/comments from the previous week, posted in Quality Contribution threads and archived at /r/TheThread. You may nominate a comment for this list by clicking on 'report' at the bottom of the post and typing 'Actually a quality contribution' as the report reason.

16
Jump in the discussion.

No email address required.

Trying out ChatGPT. Tried out a few topics from my field (electrical engineering) and it failed to make basic circuits. A couple queries I tried were making a CMOS inverter or a common-source amplifier, which are very simple circuits that most who have done a class could easily draw. Asked it to give the answer in SPICE syntax, because it can't draw things and SPICE is basically a code representation of a circuit. The results were poor; a MOSFET SPICE line is of the format Mxxx nd ng ns nb , chatGPT got the order of the drain/gate/source/bulk terminals wrong several times. It had some justification for how it connected the nodes of each individual device, but almost always failed to connect the outputs (drains) together for eg. an inverter. Also seemed to connect other terminals sort of at random.

FWIW these two circuits consist of 2 lines of code at minimum, 4 lines if you want something self-contained, maybe 8 if you want it to a fully functioning & simulatable netlist. So not asking for much here.

It gives lengthy canned responses explaining the circuit reminiscent of how a textbook would describe a circuit, and they sound good, but it's just wrong. Kind of reminds me of when students would throw out buzzwords in an attempt to explain something they don't know.

With some handholding (or, rather, explicit statements of how to fix the circuits) it can get closer to something functional, but usually in the process screws up something unrelated such that it's never quite right. Trying with anything even slightly more complex it falls apart pretty quickly and it's impossible to reconcile with anything approaching a functional circuit. It does much worse with analog circuits than digital circuits.

Seeing it underperform so much in my field is giving me a sort of Gellmann Amnesia effect for people touting how it can write code on its own. It certainly wrote out the circuit, and that circuit could be simulated, but it wouldn't achieve the desired behaviour of someone using it, so I'm skeptical that it can code well in other domains. That said, the field is kind of niche, and manually writing SPICE circuits slightly more so, so maybe it is just weakly trained for this subject. SPICE is also different from code in that it doesn't run sequentially, it's kind of like a hardware description language in that it's just instantiating elements that interact with eachother through simulation, so the interfaces between them aren't as simple as passing a variable to a function which does some abstracted function step-by-step. Also with how much content is out there for coding python/javascript/c# etc. it probably has a much greater wealth of resources to pull from.

I think at the moment it is essentially just stringing together user tutorials from the internet in a somewhat intelligent manner, I think anything novel or requiring critical thought will difficult for it to achieve. Maybe with some improved pattern recognition from the scraped data it will do better, I don't know.

Has anyone else tested it with things you're knowledgeable about and have any judgements of its usefulness?

Edit: it seems reasonably okay at turning explicitly stated english-language commands into bash commands. Probably well trained from stackoverflow, seems like a viable alternative to pulling information from different stackoverflow responses to do the thing you want to do. Also seems kind of helpful for asking how to do random MS Office stuff like highlighting every other cell in a column. Could be useful for simple stuff like this that is rote, common, and has good documentation but you don't usually remember off-hand, although you probably have to be extra careful when running bash scripts.

What fraction of human beings alive today do you think could generate something that plausibly looks like SPICE code? What fraction of those could "with some handholding (or, rather, explicit statements of how to fix the circuits) ... get closer to something functional?" What fraction could give "some justification for how it connected the nodes of each individual device?"

That's a bizarre question. It's well known that computers can do some things better than humans. Exactly what kind of conclusion do you draw from "computers can create garbage SPICE code and most humans can't", that you can't draw from "computers can add two fifty digit numbers and most humans can't" or "computers can spellcheck a 200 page document and most humans can't"?

Speak plainly.

I think I'm speaking pretty plainly. I'm asking OP to consider how ChatGPT performs in relation to an average human. This is a pretty common question people consider when talking about AI performance. After all, the Turing Test is one of the oldest and best-known tests of computer intelligence.

I am asking OP to consider these questions as a way of pushing back against statements like the following:

Seeing it underperform so much in my field is giving me a sort of Gellmann Amnesia effect for people touting how it can write code on its own.

"Underperform" is an interesting choice of words here, because it seems that the bar for performance is being set at "subject matter expert." Obviously ChatGPT is not at that level. To paraphrase Arnold Kling on the most recent EconTalk episode, "it's about at the level of an undergrad BS artist who didn't study for the test." But consider how much training and skill it takes a human to reach the level of "undergrad BS artist" and how few humans are able to attain even that level of performance. I think OP should be more impressed with how far we've come. We don't need to go a whole lot further to close the gap between "undergrad BS artist" and "skilled electrical engineer." The former often becomes the latter with just a few years of additional education.

I'm asking OP to consider how ChatGPT performs in relation to an average human.

But, assuming that the answer is that ChatGPT performs better than an average human, what conclusion do you mean to draw from that? You haven't stated anything. And computers have been able to perform particular tasks better than an average human for a long time.

That's like saying "computers can add numbers better than humans, so why doesn't the computer know that I want to add some numbers with my broken code?" There is no inherent strength in computers such that any program ran on a computer gains the ability to add numbers well. In other words, yes, computers can add numbers - but ChatGPT is not a computer, ChatGPT is a giant system of matrix multiplications and nonlinear transforms that happens to run on a computer. It would have exactly the same capabilities if a team of trillions of clerks evaluated it on paper. The ability of computers to add large numbers is not anywhere exposed to GPT as a reasoning system so that it could make use of it.