Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Like Clippy but for the CLI

github.com

Post reply on HN
Print view View original

21–30 of 41 posts

Re: Like Clippy but for the CLI

#21

Post by rigid »

Grimblewald wrote: post #20
imgabe wrote: post #11

It’s weird to me that everyone is describing their AI helper as “Like Clippy for X!” Did we all forget that everyone hated Clippy?

I loved clippy, and found it super helpful. Granted, I was a child and fascinated with the idea of artificial intelligence, which clippy was the closest thing to at that point in time. It was a useful tool, and it's at times irrelevant suggestions got me exploring things I would never have learned through school or casual exposure. All in all it was a fun, quirky, at times useful and all around great tool, just not f…

Good example of software supporting teachers in education. Fascinating kids for hours without any teacher time.

We need a clippy for math. :-)

Re: Like Clippy but for the CLI

#24

Post by zweifuss »

imgabe wrote: post #11

It’s weird to me that everyone is describing their AI helper as “Like Clippy for X!” Did we all forget that everyone hated Clippy?

Clippy, if activated, always added an unnecessary step in accessing the help file. Clippy was in part bad, because the help file had a mostly useless index, leading to no or wrong answers for Clippy. The content in the help file was additionally less than accurate, it lacked usage examples and a FAQ section that could have been used for recognizing and offering a solution to a question.

The difficult part of creating an assistant is recognizing the users' problems and offering solutions. It's the kind of experience a company can acquire with years of tech support or lots of lab testing. Then it would have to compile that knowledge in an expert system and give it away essentiality for free.

Companies that prioritize development and/or support over documentation shouldn't try to create an assistant for the same reasons. But if you have great documentation, a great support knowledgebase, and support scripts, creating an assistant out of it will someday become as easy as keeping a Juypter notebook running.

Re: Like Clippy but for the CLI

#25

Post by jkaptur »

zweifuss wrote: post #24
imgabe wrote: post #11

It’s weird to me that everyone is describing their AI helper as “Like Clippy for X!” Did we all forget that everyone hated Clippy?

Clippy, if activated, always added an unnecessary step in accessing the help file. Clippy was in part bad, because the help file had a mostly useless index, leading to no or wrong answers for Clippy. The content in the help file was additionally less than accurate, it lacked usage examples and a FAQ section that could have been used for recognizing and offering a solution to a question. The difficult part of creating…

Clippy was hated whether he was right or not. Consider the most popular catchphrase "It looks like you're writing a letter..."

In my experience, Clippy was never wrong about that - precision and recall were absolutely perfect - but people do not appreciate being interrupted, particularly at the precise moment their work has begun.

The hard part of creating an assistant is not coming up with some stuff to suggest, it's coming up with a time, place, and manner to make those suggestions so that users might be open to them.

> creating an assistant out of it will someday become as easy as keeping a Juypter notebook running.

Absolutely true, but if you intend for that assistant to proactively inject itself into people's lives, get ready to be held to an unimaginably high bar of quality.

Re: Like Clippy but for the CLI

#26

Post by jmull »

tempaway334751 wrote: post #18
imgabe wrote: post #11

It’s weird to me that everyone is describing their AI helper as “Like Clippy for X!” Did we all forget that everyone hated Clippy?

if [[ $input == dear* ]]; then echo "It looks like you're writing a letter"

Exactly!

That, and it was obscure how it could be fully disabled.

Re: Like Clippy but for the CLI

#28

Post by zweifuss »

jkaptur wrote: post #25
zweifuss wrote: post #24

Earlier quoted context omitted.

Clippy, if activated, always added an unnecessary step in accessing the help file. Clippy was in part bad, because the help file had a mostly useless index, leading to no or wrong answers for Clippy. The content in the help file was additionally less than accurate, it lacked usage examples and a FAQ section that could have been used for recognizing and offering a solution to a question. The difficult part of creating…

Clippy was hated whether he was right or not. Consider the most popular catchphrase "It looks like you're writing a letter..." In my experience, Clippy was never wrong about that - precision and recall were absolutely perfect - but people do not appreciate being interrupted, particularly at the precise moment their work has begun. The hard part of creating an assistant is not coming up with some stuff to suggest, it'…

You could check "Don't show me this tip again". That's why I don't remember it as the main problem with Clippy. I agree that it was a bad idea in the first place to interrupt a user's action. Finding the right time and manner to offer a suggestion is a hard problem even for a human being.

Re: Like Clippy but for the CLI

#30

Post by Minor49er »

tambourine_man wrote: post #29
phito wrote: post #27

First time I see a CLI tool written in PHP, not sure how I feel about this...

There are plenty of them. I feel like you should broaden your view.

Precisely. Not to mention that with PHP 7/8 improving a lot of the language, chances are that we are going to see way more PHP CLI projects popping up
Post reply on HN