wayy

5 ms·

1. 1.▲
   A PR with multiple bots talking to each other(github.com)

   3 points by wayy 7mo ago|1 comments
2. 2.▲
   by wayy 7mo ago

   I came across this PR with many different systems kicking off AI reviews, comments, and changes. You can also see human devs chiming in. This is the future of how people will work, with more and more of the tasks handled by various AI. Fasc
3. 3.▲
   Show HN: 83 browser-use trajectories, visualized(trails-red.vercel.app)

   7 points by wayy 8mo ago|1 comments
4. 4.▲
   by wayy 9mo ago

   It seemed to me the author was simply sharing his own lived experience, which happens to be a bit contrarian to the popular hype around LLMs. It may seem courageous for some but I can see a world where the author didn't think twice abo
5. 5.▲
   by wayy 10mo ago

   everybody loves building agents, nobody likes debugging them. agents hit the classic llm app lifecycle problem: at first it feels magical. it nails the first few tasks, doing things you didn’t even think were possible. you get excited, star
6. 6.▲
   Show HN: Learn Chinese by partially translating things you'd normally read

   4 points by wayy 1y ago|0 comments
7. 7.▲
   Show HN: Linden – Self-healing Playwright scripts at scale

   5 points by wayy 1y ago|1 comments
8. 8.▲
   by wayy 4y ago

   Thanks for pointing this out - we didn't consider how important stackoverflow comments could be. Will look into including as a source.
9. 9.▲
   by wayy 4y ago

   Ah we only put the option for detailed comment on negative feedback (try clicking the x and a form will pop up). Will also give that option for positive feedback in the future.
10. 10.▲
    by wayy 4y ago

    Thanks for trying it out! We can definitely be clearer on our focus for programming related queries. We usually don't display code snippets for non-programming questions but definitely still tuning a couple things there. We're not
11. 11.▲
    by wayy 4y ago

    The answer is based on the contents of the websites returned by the search engine + other some sources.
12. 12.▲
    by wayy 4y ago

    What is the correct/expected answer to that query?
13. 13.▲
    by wayy 4y ago

    We think the solution is simply having good sources and answer transparency. If you mouse over part of the answer, we try to show you the source of that sentence. Obviously this system is early and will improve over time, but if can easily
14. 14.▲
    by wayy 4y ago

    You're right - there are so many good sources not often surfaced by a cursory web search like books and experts. Adding better sources is something we're improving on. A simple next step we're looking into is to expand source
15. 15.▲
    by wayy 4y ago

    Interesting, we are trying to wrangle with the nondeterminism but sometimes it can't be helped as Bing itself can produce different results. Always actively working on the model though. The citing sources feature can definitely be impr
16. 16.▲
    by wayy 4y ago

    If you can't find the information yourself via a web search, it's going to be difficult for the model to find the answer too... for now ;)
17. 17.▲
    by wayy 4y ago

    You can leave feedback on individual search results via the check and X buttons below the answer. Leaving feedback e.g votes on each code snippet is on the roadmap.
18. 18.▲
    by wayy 4y ago

    Exactly, we use some information from traditional search engines as input to our model.
19. 19.▲
    by wayy 4y ago

    Thanks for trying it out - we're still quite early so the model isn't going to be perfect + we're focused on programming related queries at the moment. What is your use case? Are most of your searches related to history?
20. 20.▲
    by wayy 4y ago

    The answers are explicitly based on information found on the web instead of some knowledge found within the model parameters.
21. 21.▲
    by wayy 4y ago

    yep, it's super interesting to watch how cheap and plentiful compute starts to change the way we live
22. 22.▲
    by wayy 4y ago

    We're always actively exploring different prompting - a general question answering prompt most definitely won't work for all searches. Finding what people agree on and disagree about in e.g a reddit thread could be very useful.
23. 23.▲
    by wayy 4y ago

    The p50 time is around 2s end to end not under load. Bear with us as we scale our systems!
24. 24.▲
    by wayy 4y ago

    If you mouseover the answer paragraph, you'll see the relevant url / search result. You can click to go to that source.
25. 25.▲
    by wayy 4y ago

    Thanks for pointing this out - determining when code snippets are relevant is something we're actively working on.
26. 26.▲
    by wayy 4y ago

    Thank you so much for writing this up - this is extremely useful feedback. What you've described here is a use-case we're aware of called "recalling forgotten details," where "the developer knows what she’s doing, b
27. 27.▲
    by wayy 4y ago

    Thanks for the perspective - we're working on improving our functionality for troubleshooting.
28. 28.▲
    by wayy 4y ago

    Thanks for the feedback. I agree that the animations can get old if you're using the search every day. We'll look into simplifying.
29. 29.▲
    by wayy 4y ago

    Thanks for trying it out! We've gotten some solid feedback about the UI and will be working to improve it. Could you tell us a bit more about what you were trying to do and how it was confusing for complex queries?
30. 30.▲
    by wayy 4y ago

    We empirically find that most developer searches fall into a few categories consistent with this paper [0]. The author explains these categories nicely in her blog post [1]. It sounds like you're describing 4/6 of these categories