91–100 of 120 posts
Rather than inventing sophisticated chat bots, couldn't he have just had a well organised web page? If the question were where is assignment two / when is assignment due. The examples given seem like a "high tech" (possibly unreliable) solution to a low tech problem.
I was a student in this class, and had at least one question on the forum answered (correctly) by Jill. I can see this technology being hugely useful for teachers who conduct large lecture classes in any subject on a regular basis. That said, I'd be even more excited if Jill had the ability to synthesize new answers to questions through some type of case-based reasoning. This would require Jill receiving feedback on…
Do you know what kind of classification method it is using at the moment?
Earlier quoted context omitted.
> I would love to know the psychology behind this phenomenon. Laziness. It's usually faster to ask someone a question than to look up the answer. I used to do this on IRC when learning a new programming language and it saved me a lot of time. If you want an even faster answer, you guess the wrong answer and wait for someone to correct you ( https://meta.wikimedia.org/wiki/Cunningham%27s_Law ).
> Laziness. It's usually faster to ask someone a question than to look up the answer. :( My common answer is "If you're too lazy to read the documentation, I'm too lazy to cut & paste it into the email". Followed by them complaining about how I'm an asshole...
Eventually I LMGTFY. He stopped asking.
Anyone know whether they used watson APIs to create this bot or used the original watson codebase (with IBM collaboration)?
Anyone have technical details about this story? What kind of bot used, languages, algorithms, etc?
Earlier quoted context omitted.
Similarly, I know people who are incapable of communicating information via email and insist that they must talk on the phone or in person. Situation 1: "Hey can you call me?" Sure, what do you need to talk about? "The status of the Spark server." Okay. Find a quiet place, place the call, debug connection problems so we can hear each other. So what do you need? "Is the Spark server up?" Yes. "Okay, thanks, bye." Situ…
To be fair, that is one hell of a poorly written email. HemingwayApp flags 2 of the 3 sentences as hard or very hard to read.
I can show you writing a lot worse than that!
Earlier quoted context omitted.
To be fair, that is one hell of a poorly written email. HemingwayApp flags 2 of the 3 sentences as hard or very hard to read.
You honestly think it's very poorly written? You can't get any meaning from it, and believe that to be true even if you knew the context? You don't even have enough for a clarifying question? I can show you writing a lot worse than that!
May I suggest running it through HemingwayApp[1] yourself and seeing that this particular email is objectively hard to read?
Write emails (and internet comments) like the reader is a drunk 7 year old. That's about as much attention as they're giving your email.
Earlier quoted context omitted.
You honestly think it's very poorly written? You can't get any meaning from it, and believe that to be true even if you knew the context? You don't even have enough for a clarifying question? I can show you writing a lot worse than that!
I can get some meaning out of it. If I knew the context, I could get more. May I suggest running it through HemingwayApp[1] yourself and seeing that this particular email is objectively hard to read? Write emails (and internet comments) like the reader is a drunk 7 year old. That's about as much attention as they're giving your email. [1] http://www.hemingwayapp.com/
You also haven't explained what makes it horrible rather than so-so, which is important, since it's fairly easy to make it worse. You really can't just count words and dots and call it a day.
And if someone isn't going to read an email, but ask you to repeat it verbally, they really don't belong in an office environment. I'm sure that doesn't describe you!