Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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 görüntüleme • 16 gün önce •via X (Twitter)

14 Yorum

Sarah Drasner profil fotoğrafı
Sarah Drasner16 gün önce

▶️ Site here:

Martin Laker Ockovsky profil fotoğrafı
Martin Laker Ockovsky16 gün önce

Sarah, you are amazing

Javier Leandro Arancibia profil fotoğrafı
Javier Leandro Arancibia16 gün önce

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

Sarah Drasner profil fotoğrafı
Sarah Drasner16 gün önce

Thank you!

Joel Nishanth profil fotoğrafı
Joel Nishanth16 gün önce

This is awesome @sarah_edo

Sarah Drasner profil fotoğrafı
Sarah Drasner16 gün önce

Hey thanks

K.O.O profil fotoğrafı
K.O.O16 gün önce

Thank you Sarah

Pedro Filho profil fotoğrafı
Pedro Filho16 gün önce

wow, that's super neat!

Darin profil fotoğrafı
Darin16 gün önce

I love Night Owl theme so much.

Sarah Drasner profil fotoğrafı
Sarah Drasner16 gün önce

Thanks! I’m glad it’s useful

Darin profil fotoğrafı
Darin16 gün önce

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

chris corriere profil fotoğrafı
chris corriere16 gün önce

reminds me of inner/outer loop in cascade control

Joao Salgueiro profil fotoğrafı
Joao Salgueiro16 gün önce

Looks awesome!!!

CTO Field Kit profil fotoğrafı
CTO Field Kit16 gün önce

“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.

Benzer Videolar

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 görüntüleme • 9 ay önce