Note to everyone writing blog posts: Please start your post with one or two sentences explaining what you're posting about.
What is Duet? I have no idea even after skimming the article.
Edit: first google result is https://www.duetdisplay.com
What is Duet? I have no idea even after skimming the article.
Edit: first google result is https://www.duetdisplay.com
Is it not obvious that this is an Anthropic-made "personal-assistant-type harnesses"?
But I wrote this comment because the article was frustrating for me to read. One single sentence would've made it much less confusing:
Look, I really didn’t want to like **Claude** Duet, **Anthropic's new personal AI assistant**. I don’t want to be an Anthropic fanboy and ...
I'm also known to flag this kind of shortcoming in all technical documentation I review, and it annoys a lot of people that I do. I've put my judgement to the test already a few times in team meetings when someone objected this specific remark. Many times I could prove that there are always a few people in the room that would've benefited a lot from such a simple clarification. They just didn't speak up or ask, because they thought they were the only ones that didn't know a specific term.My intention is also not to be rude, just creating some awareness for this issue.
In fact, the choice not to explain things tells me a lot about the shared knowledge of a niche when I'm looking in from the outside. I don't mind the extra digging to decode it and the implied familiarity gives me information about its importance.