Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

I made a site to explain System One thinking (Jev is an example of this)! We make fast judgments all day, some models can too. The guide explains how to use those quick judgments in software. In my typical way, it leverages interactive animations, and Night Owl 🦉

40,021 Aufrufe • vor 16 Tagen •via X (Twitter)

14 Kommentare

Profilbild von Sarah Drasner
Sarah Drasnervor 16 Tagen

▶️ Site here:

Profilbild von Martin Laker Ockovsky
Martin Laker Ockovskyvor 16 Tagen

Sarah, you are amazing

Profilbild von Javier Leandro Arancibia
Javier Leandro Arancibiavor 16 Tagen

The interactive animations make the concept land - feeling a fast judgment happen beats reading a definition of one. Lovely guide.

Profilbild von Sarah Drasner
Sarah Drasnervor 16 Tagen

Thank you!

Profilbild von Joel Nishanth
Joel Nishanthvor 16 Tagen

This is awesome @sarah_edo

Profilbild von Sarah Drasner
Sarah Drasnervor 16 Tagen

Hey thanks

Profilbild von K.O.O
K.O.Ovor 16 Tagen

Thank you Sarah

Profilbild von Pedro Filho
Pedro Filhovor 16 Tagen

wow, that's super neat!

Profilbild von Darin
Darinvor 16 Tagen

I love Night Owl theme so much.

Profilbild von Sarah Drasner
Sarah Drasnervor 16 Tagen

Thanks! I’m glad it’s useful

Profilbild von Darin
Darinvor 16 Tagen

The font. The colors. The spacing. I would build an entire platform with this design.

Profilbild von chris corriere
chris corrierevor 16 Tagen

reminds me of inner/outer loop in cascade control

Profilbild von Joao Salgueiro
Joao Salgueirovor 16 Tagen

Looks awesome!!!

Profilbild von CTO Field Kit
CTO Field Kitvor 16 Tagen

“System One thinking” is a useful lens for tool design. The strongest descriptions also state the expected output, so humans and models can tell when the call succeeded.

Ähnliche Videos

New Tools for a New Era. Coding agents like Claude and Cursor have dramatically reduced the time it takes to go from idea to functional software. But the experience of designing and refining with them sucks. One reason for this is that while the terminal is an incredible tool for communicating direction with language, it is a terrible tool for defining and exploring visual and interactive objects. Here is one idea for how we might fix a small part of that. In the old world, when you wanted to create a transition or animation in your app, you would type some code, refresh your local server, and click to run your animation. It probably wasn't right, because after all no one can know what 'cubic-bezier(0.3, 0.05, 0.45, 1)' really feels like when you read it. You need to see it. Feel it. Interact with it in a real world context. So you'd edit some values, save, refresh, and keep guessing and checking until it felt right. Today, you can write a quick, single-use tool that's a visual studio for designing animations. You can then configure some components and containers common in all apps, and explore different animations in real time, adjusting key properties, and getting it just right. Then, you can copy a highly detailed prompt (or export a skill containing all your animations) that captures your intent and direction with perfect clarity. Paste this into your terminal and your agent instantly implements it everywhere. To me, this is an improvement over the old world, and a better way to work in today's. I'm extremely excited to see the ways in which our ability to rapidly create software will shape how we design software tomorrow. Feedback, ideas, and critiques welcome!

joshpuckett

82,950 Aufrufe • vor 9 Monaten