5 ms·

The description of the steps you took is super helpful feedback - thanks! Hello performs best on "how-to" questions at the moment. We're still working to improv

by wayy 4y ago

The description of the steps you took is super helpful feedback - thanks! Hello performs best on "how-to" questions at the moment. We're still working to improve troubleshooting type queries.

gbro3n 4y ago
No problem. Good luck with the project.
CodeSgt 4y ago
That'll be a difficult adaptation for potential users to make. I think most of us have been conditioned to phrase our queries a certain way to achieve the best results from Google. Then again maybe that's just me.
- wayy 4y ago
  You're right in that moving away from Google is a huge behavioral change. While our model does prefer natural language queries, what I was really referring to are the different categories of developer searches. Ad-hoc how-tos are a type of search where the developer knows what to do but not exactly how e.g "how to set a cookie in fastapi." Troubleshooting searches are things like copy-pasting a compile error, or "why is X behavior not working."
  - yojo 4y ago
    I may not be representative, but the vast majority of my Google searches are troubleshooting. If I need to know how an API works, I go straight to the docs. Put another way, troubleshooting is a several times per week task for me, and doing something net new is a once a month task which may not result in a search query. You’re going to have a hard time staying on my radar focusing on the less frequent case. Possibly the traffic patterns are different for more junior devs, but my hazy recollection of my early career is spending most of my time troubleshooting.
    - wayy 4y ago
      Thanks for the perspective - we're working on improving our functionality for troubleshooting.
harrisonjackson 4y ago
Is the assumption you are making that most developers would go to search first? rather than when they hit a blocker or error?
- wayy 4y ago
  We will support troubleshooting type searches in the future. It's just not available right now.

by wayy 4y ago

The description of the steps you took is super helpful feedback - thanks! Hello performs best on "how-to" questions at the moment. We're still working to improve troubleshooting type queries.

gbro3n 4y ago

No problem. Good luck with the project.

CodeSgt 4y ago

That'll be a difficult adaptation for potential users to make. I think most of us have been conditioned to phrase our queries a certain way to achieve the best results from Google. Then again maybe that's just me.

wayy 4y ago
You're right in that moving away from Google is a huge behavioral change. While our model does prefer natural language queries, what I was really referring to are the different categories of developer searches. Ad-hoc how-tos are a type of search where the developer knows what to do but not exactly how e.g "how to set a cookie in fastapi." Troubleshooting searches are things like copy-pasting a compile error, or "why is X behavior not working."
- yojo 4y ago
  I may not be representative, but the vast majority of my Google searches are troubleshooting. If I need to know how an API works, I go straight to the docs. Put another way, troubleshooting is a several times per week task for me, and doing something net new is a once a month task which may not result in a search query. You’re going to have a hard time staying on my radar focusing on the less frequent case. Possibly the traffic patterns are different for more junior devs, but my hazy recollection of my early career is spending most of my time troubleshooting.
  - wayy 4y ago
    Thanks for the perspective - we're working on improving our functionality for troubleshooting.

harrisonjackson 4y ago

Is the assumption you are making that most developers would go to search first? rather than when they hit a blocker or error?

wayy 4y ago
We will support troubleshooting type searches in the future. It's just not available right now.