Sept 2023, https://blog.sbensu.com/
For more like this one, see Friction logs
Summary
The document I tested things in is:
Argentina trip
Highlights
- The AI assistant manages to be tastefully integrated yet front and center:
- It doesn’t get in the way of other interactions
- It is always one keystroke away
- It plays well with most of the text I wrote
- It guides me towards how to use it:
- The prepared prompts are comprehensive and tell me blessed use-cases (summarize, brainstorm, generate, etc)
- It has open ended prompts too
- The “follow up” action flow is very well done!
- The way it constraints the AI options once you select text is very well done
- I was looking for “Rewrite with” in the options before I realized I could simply type that directly
- After understanding the AI blocks, I wish there were more of them!
- Meetings
- ✅ Summarize meeting
- Meeting attendees
- Project or topics this refers to
- Product or engineering reviews
- ✅ Action items
- Main authors and direct responsible individual
- Word count / reading time
- Jargon, acronym explainer, vocabulary, index of terms, etc
Problems
Custom prompts
I didn’t realize that you could use totally custom prompts until 10 minutes in. The design of the type-ahead suggested to me that I was picking from a set of predefined options. I didn’t realize that I could enter anything and press enter to have it work!
- Find analysis of why here
When running a custom prompt over an AI block, it generated a new set of text below, instead of editing the AI block
- “Reorder the action items in order of importance”.
See here
Explain this
“Explain this” doesn’t fully work like the other selection actions:
- I want to read that explanation if somebody else wrote that text and I don’t understand it (maybe the AI did)
- But I would never want to Replace or Insert below with that explanation. It says “The text”! For it to “integrate” well with the text, it should be an explanation that you can inline. I bet that you can change the prompt for it to explain as-if the author was explaining inline.