Email or username:

Password:

Forgot your password?
Simon Willison

On the one hand, I'm very sympathetic to the argument that "AI" is an over-hyped buzzword that is rapidly losing all meaning, if it ever had any (beyond being a combination of science-fiction and an academic discipline from the 1950s)

On the other hand though, I'm building a feature where LLMs help a user build a SQL query using an English-language question and I need to decide what label to put on that button, it's hard to come up with anything that's as clear as "Use AI to write this query"

36 comments
Simon Willison

"Get help writing this query" implies a human support mechanism (or a link to a help desk / manual), which this isn't

I need a widely understood shortcut for "this button will get the computer to do a weirdly useful trick that needs a widely agreed upon name..."

I think "AI", at least in terms of UI micro-copy, may be by far the best option at this point

Anyone seen any UI elements that do this kind of thing and use some other widely understood term for it?

Tom Armstrong

@simon I don't rate the chances of it catching on, but something like VS Code's "Try to infer the type of parameters from usage" feels like it's in the right vein.

"Try to infer the correct query based on natural language"? It's not exactly catchy 😜

Jon A. Cruz

@simon "AI" as the button and "spicy autocomplete" as the tooltip

Glyph

@simon I think you should avoid “AI” and “✨” purely for branding purposes. LLMs have a stink on them thanks to indiscriminate deployment by desperate companies hitting their growth ceilings. instead call it something like “autogenerate query” or “English to SQL” or “ask a question about your data”

frew

@simon I think we in tech are a weird subculture that effectively doesn’t matter to the real world. I’d use AI and ✨ and the real life end user will get it. Tech people will be annoyed but tech people have resting annoyed face and that is our chosen burden.

Simon Willison

@frew that's more or less where I am right now, I think "AI" increasingly means so thing useful to end-users, at least as a UI term

Tom Bortels

@simon

AI is the mechanism, not the thing. How it does it's job is largely irrelevant to the end user.

When I want help at the library - I don't talk to the "person" - I talk to the "librarian".

So: "Wizard".

Windows has had things like the "Network Setup Wizard" for literally decades. We know it means "here let me help you do this specialized task". Co-opt the term.

That or "assistant". But "wizard" has a pre-established meaning in this context.

Simon Willison

@tbortels Wizard is actually pretty good, I worry that it carries a huge amount of baggage though - I would almost never select the "wizard" option in a piece of software I was using

Tom Bortels

@simon

Well - that baggage is the context you're looking to exploit. "Wizard" means I push this button and something not a person walks me thru it.

As for you never selecting the "Wizard" option: I'll say this in response, that I say to a lot of the very talented folks I talk to: you are not the norm. You're a weird edge case, an outlier, a wild card - talented. This is awesome, but of the issues it causes is you're probably not a great representative sample of your users. Most of them don't think like you or know what you know, which is part of why you're making tools for them and not the other way around. And - that's fine!

Lol, if it makes you feel any better, I don't usually do wizards either. i wank to know the options and how it works. But I know that's the exception, not the rule.

@simon

Well - that baggage is the context you're looking to exploit. "Wizard" means I push this button and something not a person walks me thru it.

As for you never selecting the "Wizard" option: I'll say this in response, that I say to a lot of the very talented folks I talk to: you are not the norm. You're a weird edge case, an outlier, a wild card - talented. This is awesome, but of the issues it causes is you're probably not a great representative sample of your users. Most of them don't think...

Paul Moore

@simon @tbortels Maybe that's true, but you can say *exactly* the same thing about the term AI. I'd never click a button that said AI, for the same reasons you give for Wizard.

Neil Kandalgaonkar

@simon @tbortels In UX, Wizard generally refers to a series of screens that guide you through complex options

nngroup.com/articles/wizards/

Now, the average user may not know that, so perhaps “Wizard” could still work, but I think something like

“✨Suggest query”

might get across what you want, and give the user the right mindset to carefully evaluate what the AI does

Andrew Snare

@simon Putting my UX hat on, why does it need a button at all? The ideal interaction could be just to do it live?

Or something like Show/Preview/Generate SQL/Query.

Bridget Almas

@simon why not “predict my query” or something to that effect?

Honza Javorek

@simon Something like „magic wand“ from Photoshop-like software? It was magic back then so they called it magic wand. The name says nothing about the feature, but now everybody still knows what exactly it does. Naming is strange.

nickalt

@simon "Generate query ✨". Sparkles have become an informal standard to indicate AI magic: nngroup.com/articles/ai-sparkl

Kevin Conner

@simon The text doesn't matter so long as it's in an aurora-toned gradient. Jokes aside I think "Generate" is understood and doesn't oversell it.

Almad

@simon I think it depends on the audience. For genpop, I think the ship has sailed, and avoiding the term “UI” is like insisting on “Download for GNU/Linux” as an OS name.

Yes, it’s technically correct, but not user friendly.

Prem Kumar Aparanji 👶🤖🐘

@simon "use system to translate your instructions to SQL query" is wordier

Lars Wikman

@simon "Guesstimate!" or "Vibes!"

A current-gen version of "I'm feeling lucky"?

Timo Zimmermann

@simon ignoring all arguments for or against the “AI” label - why not just call the button “generate” or “generate query”? It’s clear what it’ll do and the implementation shouldn’t be something that concerns the user.

DELETED

@simon
"Set fire to the planet, because you couldn't be bothered to learn SQL" is probably overly verbose and hostile isn't it 😂

I'm being snarky, but I think any goal outside of learn SQL, for interacting with SQL systems, will ultimately increase user surprise and frustration, which I think is a core part of what we want to build UI's to avoid.

I lso read some terrifying statistic about AI taking up all the power by 2027 and so I'm extra anti-AI lately.

@simon
"Set fire to the planet, because you couldn't be bothered to learn SQL" is probably overly verbose and hostile isn't it 😂

I'm being snarky, but I think any goal outside of learn SQL, for interacting with SQL systems, will ultimately increase user surprise and frustration, which I think is a core part of what we want to build UI's to avoid.

jr conlin —〰—

@simon

Yeah, but that sounds like “crafting a solution” rather than solving a problem.

The button should offer the user a way to help, and unless the sole thing your app does is create SQL code, you can probably do better, like “What would you like to find?” or “Help me look for…”

Simon Willison

@jrconlin this is for my Datasette app, which is very open about letting users directly execute SQL - I want to give them a feature to help them figure out the query syntax for more complex things datasette.io/content?sql=selec

m_eiman

@simon automagic english-to-sql conversion

Jeff Graham

@simon remember when Google had the "I'm feeling lucky" button? Current gen AI feels very on brand for that.

Michael Henriksen

@simon I was just thinking something along the lines of “assistive generation” to communicate that it assists you getting to what you want, and that it's machine generated. However, when I looked up “assistive” it seems to typically refer to disability aids, so it might not be the best fit.

Tom Morris

@simon automated assistance?

Also prior art to potentially be inspired by: MongoDB’s online admin tool has an LLM to help users generate queries. It’s… fine for really simple queries.

Dr. Juande Santander-Vela

@simon "Propose query implementation." That still leaves the human in charge of verifying if it works.

Petr Viktorin

@simon “Generate” (or “autogenerate”)?
To the end user it doesn't matter that the heuristics use many floats rather than few ints/pointers. Traditional autocorrect/autocomplete (and other tools that deal with human language) are also often wrong. If the engine actually works, no one should care what's inside.

postweber

@simon Grafana has graphical query builders for some languages. You could have an SQL/Plain English toggle.

Go Up