This whole “open into” thing is a crutch.
Make dot great and get rid of the modes!! You can do it!! Org chart be damned.
Pick a single mental model and run with it - particularly for consumer
@justinskycak This is something I def wish I internalized earlier.
Learning compounds; trying compounds; habits compound.
Who cares if you think it’s unimportant now - just make sure you truly go 100% all the time. 1% better each week etc
@davidsven I look at this and wonder how @rabbit_hmi might have had a different reception if v1 was for kids. The form factor is sweet
They even had the right color - orange - just like Yoto which came later
All comes back to “writing is thinking”
Be deliberate about what types of thinking you are delegating!
How to translate boilerplate a -> b : probably fine
How to fill out a form with info you already know : probably fine
What should we do next & why : 😥
We instituted an official AI Writing Policy at @Clay.
Massive thanks to @sophiebits on our engineering team who wrote this.
Originally this was just for eng, but other teams found it so helpful we expanded it company-wide.
Here are the four guiding principles:
1. You must stand behind every idea and sentence
It is your responsibility to make sure that the entire document is representative of your own thoughts before you share it.
2. Writing is thinking
Spending time on the writing process teaches you more about your topic. If you circumvent this process, you will walk away with a poorer understanding of the subject matter.
3. More time should be spent writing a document than consuming it
If you generate a document from a short prompt then ask your readers to go through the longer output, you are disrespecting their time. They can talk to ChatGPT themselves if they want to.
4. Longer is not better
AI makes it easy to generate long docs, and it loves padding them with sentences that say nothing. If you're producing docs from a short prompt, consider just sharing the prompt.
You can read (and borrow) the full policy below. Hopefully we all communicate a bit more clearly now :)
Trying to use the new @SlackHQ message blocks & data tables. Either I’m doing something wrong or the UX seems off.
Rows seem to side scroll individually instead of the whole table. Why? Basically impossible to compare values
Tables should be tables! Help!
@RobertJBye Much better - keep scaling so this works across multiple remotes & ideally across accounts (work and personal switching is also annoying)
I was a super energetic / distractable kid who was pretty good but not incredible in school.
When I had some of these conversations with a doc, I explicitly remember that framing: “well everything seems to be going OK, so is this really a problem?”
Well… imagine what could be if I could actually focus!!
@AlexH_Johnson Another pressure point: at some point one of the models/agents will go off the rails and do something unintended, there will be real consumer harm, and then we’ll see lawsuits
totally agree. The banks themselves may go on the offensive too, even if they take a beat to act.
I am definitely confused why a lot of these agentic takes assume companies are just going to let someone come destroy their business model by adversarially abusing their products with agents.
Unless there are laws that force openness/agent connectivity, we will see the same thing folks like Resy have done - block actions / ToS violations.
Companies also may go to the model / agent providers directly and pitch for stronger protections.
It’s hard for me to imagine meta&muse/oai/ant etc truly want to arms race / go to war here - particularly if these consumer use cases are very expensive to operate and consumers don’t want to pay for them.