Showing posts with label computer science. Show all posts
Showing posts with label computer science. Show all posts

Friday, October 31, 2025

Tech Reflection - Two Sides of AI

“This Halloween, I’m dressing up as generative AI. I’m going to show up to the party without a costume and just start stealing pieces of other people’s outfits.”
An X dispatch my niece screenshotted for me

Introduction

Is AI the amazing new technology that’s changing the world, or a petty thief that just steals people’s ideas and passes them off as its own? Does it actually carry out anything approaching thought, or is it just a zombie, stalking humans’ digital relics and muttering “brains … brains … brains” as it angles to get a piece of us?


In this post, I examine the two most fundamental functions AI chatbots can carry out, and draw a distinction between the two. I believe this can give us useful guidance in deciding how we ought to use this game-changing technology.

Ecclesiastes vs. Barthelme

AI is evolving fast, perhaps faster than our ability to understand it. I’m having to adapt; for example, I’ve stopped spelling it “A.I.” because leading media outfits like The New Yorker and The New York Times have now eschewed the periods. So if you’re reading this on your phone in a sans serif font you may have initially thought I was writing about there being two sides of Albert or Alfred. I asked ChatGPT what to do about this ambiguity between a capital “i” and a lowercase “L,” and it suggested I could “kern or tweak the glyphs.” I’m not exactly an expert at kerning glyphs, so I asked the chatbot how. It gave me all kinds of strategies, the best one for my blog format (HTML) being this:

AI <!-- default -->

A<span style="letter-spacing:0.05em;">I</span> <!-- slightly looser -->

So you can see, GPT is right there with an answer when queried about a technical operation that has been done before. But what about doing something creative and original? This is a fundamental distinction and I am going to propose we look at AI from two largely separate perspectives, for which I’ve invented labels:

  • Operational mode – I thought about calling this Ecclesiastes mode, for “no new thing under the sun.” This mode is about helping with a nuts-and-bolts operation (e.g., HTML scripting, DNS routing) that somebody else, probably many people in fact, already figured out and documented out there on the Internet for AI to gobble up, distill, pretty up, and present. Here, AI is basically a really good large language model that excels at combing through gobs of chaff to find answers, and organizes and summarizes information very clearly. I wouldn’t say it’s as parasitic as what’s suggested by the X epigram above, because lots of people freely post technical stuff to the Internet just to be helpful, without thinking of it as sacrosanct intellectual property.
  • Creation mode – I think of this as Barthelme mode, named for the writer Donald Barthelme, because I think he’s the epitome of totally original, wacky, one-of-a-kind creative types with an absolutely distinctive voice. In other words, this is the intelligence that I am quite convinced AI could never approach. By creation I mean using the full capability of your own mind to advance ideas that are new, and yours.

The trouble is, many people don’t make any distinction between these two general areas of AI, so on the basis of its prowess as a natural language search engine, they are be led to believe it can do a perfectly good job at creation mode. And since most people aren’t English majors, and in fact don’t respect English majors, AI platforms get to roll out some pretty inferior writing and everybody thinks it’s genius. (This widespread lack of sophistication is also why McDonald’s makes so much money.)

So what?

For many years, as I’ve lamented at length in these pages, kids have been told all the jobs are in tech, and they need to study STEM. And now, many of the kids who dutifully followed these marching orders are graduating from college with Computer Science degrees and not getting jobs, and tech is laying off gobs of people. Next time I meet a STEM major I’m gonna ask him, “Computer Science? What are you gonna do with that?”

So how did STEM go from meal ticket to a food stamp? Well, I think it’s largely because AI is actually getting pretty good at the operational mode. It writes software so well, all industry needs is a seasoned coder to check it. Will we still have seasoned coders in 20 or 30 years, when all the current ones have retired and nobody has come through the ranks to replace them? Probably not, but that’s a whole other blog post somebody has surely already written. (I did blog about ChatGPT’s prowess with operational mode earlier this year, here.)

So as we look at AI, and particularly its role in our personal and professional lives, I think we need to ask ourselves what we have to offer that is rare and valuable, and how AI can help. Specifically, I believe we should be asking the question: how do we use operational AI to handle rote stuff, so we have more time to develop our unique, original ideas—so as to bring out our inner Barthelme?

What to use AI for

I have to confess, I love AI for light research when I’m blogging. The kernel of my posts always comes from my own brain, usually from pondering all kinds of things while I’m out on a solo bike ride. But ChatGPT is a great way to chase down and pinpoint something I had vaguely committed to memory. For example, when working on a recent post I asked it, “Can you track down the Lore Segal quote from ‘Her First American’ about ‘protocol is the art of not doing what comes naturally’?” I probably could have found this with Google, but the AI helped (and might have been indispensable here had I not remembered the name of the novel). ChatGPT was also super helpful when I was writing my post on induction ranges, in researching certain facts (e.g., energy efficiency info and whether government rebates are available).

AI is also pretty helpful at work, where I use a “walled garden” version my employer provides. (It doesn’t use any of my chats as training data for the AI’s ongoing education.) In fact, my employer exhorts all us employees to use AI every day. It’s like with any great tool: we’re expected to work more efficiently because we have it, so we’d better use it well. Recently, I took several product specification documents for different Internet hardware devices, fed them into an AI utility, and asked it to read them all, highlight the differences among the different makes and models, and tell me which one I want for xyz purpose. This was much faster than poring through everything myself, which is a decidedly operational task. The report it generated was clear and reasonably concise, and probably won’t be read very carefully anyway. In fact, someone will probably upload it to a chatbot and have it summarized. All this is fine with me.

One other great use for AI chatbots is to ask them for instructions for quotidian technical matters in your personal life, like disabling the child lock on your new microwave oven, charging your new bike’s electronic shifting, or restoring your playlist after updating your smartphone’s MP3 app. Sure, these are things you could look up on YouTube, but often that search can be tricky, and the videos can be agonizingly slow. The following video tutorial, which is crisp and concise and beautifully shot, is perhaps the exception that proves the rule:

I guess one benefit with YouTube is it’s less likely to hallucinate. I asked ChatGPT if my bike’s brake/shift levers have button cell batteries, and it explained in great detail how there are actually wires running from the battery pack to each lever, so they get recharged along with the derailleurs. The chatbot even drew me a nice diagram to illustrate this. Alas, it was hallucinating: the levers totally do have button cell batteries that need to be periodically replaced.  But all this being said, it’s easy enough to sanity check this kind of output, and I usually get a good answer from AI when I can’t locate a product owner’s manual or don’t feel like leafing through the 50-page one that I have, trying to get past the 14 foreign language versions.

What NOT to do with AI

I think where people get into trouble with AI is when they try to get it to do their work for them, particularly writing documents or correspondence that they then pass off as their own. In some cases this is an ethical or even legal matter; as I described here, the New York Times is suing OpenAI for copyright violation, and I have firsthand evidence of ChatGPT essentially plagiarizing this blog. But I doubt you overmuch care about that. There are two bigger issues, I think:

  • What this “creation mode” usage does to the quality of “your” writing
  • What it does to the quality of your thinking

There’s this notion that you can ask a chatbot to write something for you, anything from an email to an invitation to a work report, and then you can just polish it up a bit, and you’re done. No more writer’s block! No more outlines, or worrying how to organize your thoughts! That might be okay for a very basic report, like what I described comparing features of tech hardware. But when you start from scratch with your own document, you’re not just leveraging AI’s impersonal, sprawling training data; you’re using your own—everything you’ve experienced, heard, read, and dreamt of. It’s your own personal muse, not the generic Internet one.

Honestly, for anything loftier than a rote technical document—that is to say, anything designed to edify, persuade, or entertain—haven’t you seen for yourself how AI can fail? Like, you’ll get this chipper invitation to a family reunion and it’s using corny phrases like “drum roll please” and joking about your family’s dance moves, and it just seems generic and clichéd? That’s all AI can do. It doesn’t know you or your family or friends well enough to say anything truly clever, and all the polish you want to give its rough draft won’t help. Your invitation will never have real style, along the lines of, “L— gets dibs on the guest room (which she may still anachronistically refer to as “her” “bedroom”) and its magnificent new king-sized guest bed. If you’re nice she might invite you to a slumber party there. Other guests can fight over the legendary Futon of Sand down in the home office. Beyond that, we have two large sofas for those interested in the college-esque party-‘til-dawn experience. We would not be offended if one or more parties were to seek a motel/hotel/AirBNB/VRBO, especially given the relatively small number of bathrooms here (i.e., one). Regarding rumors that the men are encouraged to pee in the backyard, this is true, but please stick to the planting beds and the fountain.” See how much better that is?

Now, you might be thinking, “Wait, I’m not a blogger and I wasn’t an English major. Cranking out an email or an essay may be easy enough for Dana, but I just want to get this task done and checked off.” But stop and think for a moment: what would you like to be good at, in life? Please tell me the answer isn’t just “typing good prompts into AI.” Wouldn’t you like to be articulate, interesting, and capable of thinking on your feet? Because what are you going to do at a cocktail party, or a job interview, or a non-virtual work meeting, when you don’t have a chatbot to help you, and that’s the habit you’ve let yourself fall into? The reality is, we get good at thinking by struggling to do it, for ourselves, the old fashioned way.

So let’s not undervalue written communication by outsourcing it to AI. The best case scenario is that it’ll do an inferior job, replacing what could have been original thought with a pile of trusty clichés and/or stealthily plagiarized, slyly anonymized content. The worst case scenario is that it’ll actually get good enough that you never have to write for yourself again, and your brain can atrophy to the point that you’re not even a thinker anymore … just a chatbot operator.

Because you don’t care

Gosh, I guess I drifted into high-and-mighty, pompous, full-on pontification there, and I feel pretty sheepish about it! Fortunately, I’m realistic enough to sense you snickering, and I know you’re going to turn right around and keep on using AI for whatever you can possibly think of. That being the case, check back next week because I’m going to catch you up on the latest AI technologies and how much they’ve improved since my last check-in. Whether your chatbot of choice is ChatGPT, Gemini, or Copilot, I’ll have you covered. Until then, I’ll be getting back to what I really enjoy in life: kerning glyphs.

Other albertnet posts on A.I.

—~—~—~—~—~—~—~—~—
Email me here. For a complete index of albertnet posts, click here.

Tuesday, April 30, 2019

In Defense of Multitasking


Introduction

It’s pretty widely acknowledged that most of us multitask. At the same time, we’re lately bombarded with warnings about how ineffective and even harmful multitasking is. Neither multitasking nor these warnings look like they’ll subside anytime soon. So what’s going on here? Are people just dense and/or stubborn, or are the naysayers full of crap? Neither, I’ll argue. Both the behavior and the warnings are partially correct.

What is multitasking?

I think this question is the crux of the matter. Those who warn against multitasking too often do so without defining what they’re even talking about. This article on Monster.com declares that “Multitasking makes you less productive,” “Multitasking makes you less effective,” and “Multitasking can slow down your brain,” but doesn’t ever say what multitasking is. This article in Forbes says, “A study at the University of London found that participants who multitasked during cognitive tasks experienced IQ score declines that were similar to what they’d expect if they had smoked marijuana or stayed up all night.” Pretty specific consequences, but again the precise multitasking behavior isn’t described whatsoever. Imagine an article saying that “drinking caused test subjects to be unable to walk in a straight line or speak clearly” without saying how much was drunk and of what. And yet “drinking” in this context is no more general than the term “multitasking.”

This article on Health.com at least gives a few examples: “We all do it: Texting while walking, sending emails during meetings, chatting on the phone while cooking dinner.” The problem is, these examples don’t add up to a specific type of behavior. Let’s apply this to my earlier example: “We all do it. Sharing a Heineken with our spouse. Having a glass of wine with dinner. Lining up eight shots on the bar and downing them one after another in the span of just a few minutes.”

In other words, I find fault with any article that implies all multitasking behaviors are equivalent. Sending emails during a meeting, I would argue, is more difficult than chatting on the phone while cooking dinner. It’s pointless to lump these activities together as a single behavior that should be avoided. To advise anybody on the effectiveness of multitasking, we need to define it better.

So what is multitasking, really?

At its most basic, multitasking is doing more than one thing at a time. I mean, duh. So, walking while chewing gum is multitasking. Singing in the shower is multitasking. Listening to music while driving is multitasking. So is knitting while watching instructive calculus videos at khanacademy.org. This last example is from real life … I caught my daughter trying to do this the other day. (I hope she did better on the test than on the scarf.)

The problem arises, I think, from the promise of modern technologies that, we believe, can endlessly increase our productivity. We can have multiple tabs open on our browsers, can play background music on our laptops, and can carry on multiple concurrent chats in separate windows. In fact, the term multitasking originated in the computer realm, according to the OED (as described here). When we use this term to describe human behavior, it’s somewhat metaphorical, as though the human brain worked just like a computer’s CPU. To the extent it doesn’t, we fall down on the job.

The temptation to do two things at once is perfectly reasonable: we don’t have time to do everything, so we need to be as efficient as possible. It doesn’t make sense to abandon this impulse entirely, just because it’s said to be ineffective and/or dangerous. Instead, we should simply be more careful about exactly what we try to double up on.

Multitasking I totally support

First off, the phone can be a great multitasking device—so long as you use it as a phone. All kinds of things can be done while having a telephone conversation. My favorite such activity is doing the dishes. This is such a brain-dead simple operation, I’m this close to being able to do it in my sleep. That’s why it’s so boring. So whenever I decide to phone up a friend or family member, I like to put on my headset and head into the kitchen. At least 99% of my brain power goes into the conversation, and at the end the dishwasher is loaded and the kitchen is clean. Should I really stop doing this just because every time someone multitasks, God kills a kitten?

I’m not saying any phone conversation can be carried out while housekeeping. When I’m on a work call, I need to concentrate more. That doesn’t mean I don’t multitask, though; I like to take notes on my laptop during the call, which not only helps me remember what was discussed, but actually increases my focus. This only works, of course, because I can touch-type. (Writing down notes actually distracts me, probably because it’s slower so I fall behind.)

Where people get in trouble, I’ve found, is when they try to sneak a peek at other incoming information during a boring conference call. First they’re just scanning their inbox, then they’re reading their email, and soon enough someone on the call asks them a question and they reply, “Could you provide a little more context around exactly what you’re asking?” which is code for “I totally didn’t hear a word you said and would like another try.”

So what about the Health.com example, chatting on the phone while cooking dinner? I’ve totally done that! If I’m just shooting the shit with my brother, while making a barebones pasta dinner for my kids, there’s almost no way I’m going to screw up. Worst case scenario, a pot boils over or I temporarily forget the spinach in the microwave. This is in no way similar to the dire consequences of trying to text while driving, even though both get lumped into this insanely general category called multitasking.

Sure, sometimes this benign multitasking will backfire. The other day a phone conversation took an unexpectedly intense turn while I was making pour-over coffee, with this unfortunate result:


Sure, that was a bit of a mess, but does it mean going forward I should just sit in a chair with my hands in my lap every time I talk on the phone?

How to choose your multitasks

The trick to multitasking, I think, is to make sure you only pair cognitively difficult tasks with brainless ones. Singing in the shower is pretty obviously a safe pairing because neither task demands your full attention. Where things get tricky is when both activities seem simple—boring, even—but they are nonetheless too complicated to actually do simultaneously.

For example, driving isn’t particularly exciting, but it’s very demanding cognitively. Texting is such a humdrum, everyday activity, it’s tempting to think it’s brainless—but it’s not. Needless to say, texting while driving is a dangerously stupid combination. The problem is, you simply can’t watch the screen and the road at the same time. You have to go back and forth between the two, which is much harder than many people seem to think. They try to run a mental process that keeps track of how long they’ve looked away from the road, but texting draws them in and subverts this process. Next thing you know, their urgent message—”whats up lol”—has gotten them in an accident.

So to draw the line between reasonable and unreasonable multitasking, you should ask yourself whether you’re truly doing two things at once—singing and soaping, for example—or just shifting your attention back and forth between two points of focus—say, the video and your knitting, or your screen and the road. If your multitasking involves that constant shifting of focus, then you really aren’t being efficient or effective. You’re merely interleaving two tasks, and adding a third focus-management process on top of them. Your performance actually drops.

Case study

After I watched my daughter trying to knit while watching the calculus video, I had her do a little multitasking game with me. (I learned it in a class I took recently on executive function.) All you do is write out, by hand, the sentence “Multitasking is worse than a lie” and then, below this on the page, you write out all the numbers from 1 to 27. You time this activity with a stopwatch. Here’s the result my daughter and I got:


Writing the sentence and then the numbers took us 23 seconds. (Actually, I was a second or two slower than my daughter. She’s a born competitor.)

Then, you do the same task, except that you write the sentence and the number sequence simultaneously—or, to put it more accurately, you interleave the tasks. That is, you write a letter, then a number, then the next letter, then the next number, and so on until you’re done. Here’s how that came out for my daughter and me:


The end result is pretty much the same—both the sentence and the number strings are complete—but the operation took us more than twice as long, at 48 seconds. Also, I didn’t do as good a job … somewhere along the line I dropped one of the numbers and only got up to 26. As you can see, neither task is difficult, but both require your complete attention if you’re to do them efficiently.

Not so fast

It’s actually an oversimplification to divide all activities into “requires focus” and “doesn’t require focus.” For example, in general I’d say listening to an audio book while driving is a safe activity, but not always. My family enjoyed listening to Lemony Snicket while driving through rural Oregon, but I once tried and failed to listen to Wallace Shawn’s one-man play The Fever while driving southbound on I-880. Wallace Shawn is the highly intellectual guy who had dinner with Andre (and should have titled his play My Dinner Without Andre), and I-880 is a hellish stretch of freeway between Berkeley and Silicon Valley that features high-speed bumper-to-bumper traffic as early as 6:00 a.m. I didn’t crash my car, but had to save The Fever for later.

Similarly, chatting on the phone while cooking isn’t always a reasonable combination. What if it’s a delicate discussion, and/or you’re trying out some really tricky new recipe? There’s no conversation so casual that I could maintain it while trying to follow an instruction like this: “When nearing 234 degrees, there is a fine overall bubbling with, simultaneously, a coarser pattern, as though the fine bubbled areas were being pulled down for quilting into the coarser ones.” Similarly, just making toast might be too much for me if a loved one is croaking out his dying words over the phone.

I think the trick to multitasking is to pause and question yourself honestly: are you really increasing efficiency by combining these two activities, in this particular instance? Is it truly the case that nothing is lost? If you and your spouse are carrying on a conversation while walking your dog, the answer to this internal query may well be yes. But other situations should reasonably lead you to question your behavior. Does the friend who’s trying to talk to you really not care that you’re only pretending to listen while you futz with your phone? Is the angry motorist honking and flipping you the bird really the one who’s out of line? Is there actually any point in attending a conference call in which you miss 90% of what is discussed?

My conclusion: feel free to multitask … just keep yourself honest.

--~--~--~--~--~--~--~---~--
For a complete index of albertnet posts, click here.