Readit NewsDead Comment
I read Clear’s book, though, and like it. Neither book has new ideas, but they both present old ideas in useful ways.
1) Amen 2) I wonder if this is isolated to junior dev only? Perhaps it seems like that because junior devs do more AI assisted coding than seniors?
These are a good set of principles for any company (or individual) can follow to guide them how they use AI.
I'm one of the loudest voices about the so-far unsolved security problems inherent in this space: https://simonwillison.net/tags/prompt-injection/ (94 posts)
I also have 149 posts about the ethics of it: https://simonwillison.net/tags/ai-ethics/ - including one of the first high profile projects to explore the issue around copyrighted data used in training sets: https://simonwillison.net/2022/Sep/5/laion-aesthetics-weekno...
One of the reasons I do the "pelican riding a bicycle" thing is that it's a great way to deflate the hype around these tools - the supposedly best LLM in the world still draws a pelican that looks like it was done by a five year old! https://simonwillison.net/tags/pelican-riding-a-bicycle/
If you want AI hype there are a thousand places on the internet you can go to get it. I try not to be one of them.
That may be true for something like a HUD or where we're really overwhelmed with info that is fast and reaction time is paramount.
But you can read a hackernews thread one line at a line and never get overwhelmed, right? I literally have never felt overwhelmed looking at the threads (which are also organized into local groups already etc).
I read it for pleasure and engagement, it's not something I want AI to automate away.
And when you say "continue the conversation there", do you mean use AI to write comments? If so, then this is the opposite of what makes HN HN.
https://app.hncompanion.com/item?id=46962996
This post has 500+ comments with various viewpoints and you see the summary on the right side.
You are right that most of the time threads are organized into local groups. But in the above example, there are many comments that relate to the same topic, but are not under the same parent comment. HN Companion's summary surfaces this into a topic "Limitations of Current AI Models" which shows comments from up and down the post.
You can click on the author name in that topic in the summary panel, it will take you directly to the comment. This is what we meant by "continue the conversation there", i.e you are now in the main HN experience, so you can navigate to child/parent/sibling comments (through the link buttons or keyboard navigation).
We definitely don't want AI to write comments. Happy to elaborate if you need.