produnis@discuss.tchncs.de to Programmer Humor@lemmy.ml · 1 year agowe are safediscuss.tchncs.deimagemessage-square181fedilinkarrow-up11.76Karrow-down133
arrow-up11.72Karrow-down1imagewe are safediscuss.tchncs.deprodunis@discuss.tchncs.de to Programmer Humor@lemmy.ml · 1 year agomessage-square181fedilink
minus-squarestarman2112@lemmy.worldlinkfedilinkarrow-up11·1 year agoLegitimately could be a use case “Attend this meeting for me. If anyone asks, claim that your camera and microphone aren’t working. After the meeting, condense the important information into one paragraph and email it to me.”
minus-squareotp@sh.itjust.workscakelinkfedilinkarrow-up15·1 year agoHere is a summary of the most important information from that meeting. Since there were two major topics, I’ve separated them into two paragraphs. It is a good morning today. Everyone is thanked for their time. Richard is looking forward to next week’s meeting. The rest of the information was deemed irrelevant to you and your position.
minus-squareMajorHavoc@lemmy.worldlinkfedilinkarrow-up6·edit-21 year agoHoly cow! You’ve done it! You could wrap this (static text block) in a web API and sell it. Edit: /s, I guess. But that text really is easily an 80% solution for meeting summaries.
Legitimately could be a use case
“Attend this meeting for me. If anyone asks, claim that your camera and microphone aren’t working. After the meeting, condense the important information into one paragraph and email it to me.”
Here is a summary of the most important information from that meeting. Since there were two major topics, I’ve separated them into two paragraphs.
The rest of the information was deemed irrelevant to you and your position.
Holy cow! You’ve done it! You could wrap this (static text block) in a web API and sell it.
Edit: /s, I guess. But that text really is easily an 80% solution for meeting summaries.