Maggie Appleton 写设计、人类学和智能体界面时，习惯先画清楚隐喻，再谈工具。把「Programming Portals」整理成可阅读的中文笔记：问题在哪、界面默认会把人带去哪、落地时该改什么。原站导航、评论回响和广告已去掉。

The Context

In the mid-1980s the world of computer interfaces cracked in two Specifically, in 1984 42ya when Apple’s Macintosh became the first GUI-based computer to gain market traction. Honourable mentions: Xerox Star and Apple Lisa , leaving a gaping divide between two opposing paradigms.

MS-DOS CLI interface – Source: Betawiki On one side of the divide sat the CLI, or command-line interface . This was a blank, black input screen where you typed a set of memorised commands and keywords to make the computer do things for you. Commands like mkdir my_project and touch plans.txt did the work of the “Create new folder” and “New document” buttons. Everything was made of text and navigated with a keyboard.

The Joys of Text and CLIs

On the other side was the brand new world of the GUI or graphical user interface . A place where every available feature was visibly laid out before you in selectable menus and hierarchical sets of buttons. Real-world metaphors gave physical shapes to abstract functions. Users no longer had to memorise long lists of commands. You could see all the functions a programme was capable of without reading the manual.

Most of us consider GUIs as an enormous leap forward in computing accessibility and usability. Design patterns like direct manipulation , point and click interactions, visibility of system status , wizards , and overlapping windows all made computers far easier to use and drove the rise of personal computing throughout the rest of ’80s and ’90s. The history of this is too long and detailed to get into, but this video on the history of GUIs from Crash Cours

The Pattern

Windows XP: the peak of 1990's GUI glory – Source: Computer Wiki Scroll forward a few decades and we now live in an overwhelmingly GUI world. At least most of us do. That crack in the interface world wasn’t a division in time, with CLIs in the past and GUIs in the future. It was a crack in the population of computer users. It created two distinct categories: end users and programmers .

End users are the 99%. They’re all the regular folk who interact with computers through the carefully designed GUI applications built for them by teams of designers, developers, and product managers. They have little control over what actions and affordances are made available to them.

1. HyperCard

Programmers are the tiny, elite subsection of the population who control what computers can do. To add some nuance to this, programmers are not alone in controlling what the computers can do. We also have VCs doling out cash, C-suite leaders and product managers directing the vision, and designers orchestrating the user experience. But if the programmers refuse to build it, it’s not going to exist. They are the final touch point and nexus of control betwee

Programmers had good reason to stick with text-based CLIs. While GUIs gave us many gifts, they come with a set of tradeoffs. Ones that are particularly troublesome for the type of work programmers do. CLIs are better for…

2. Fermat

I’m distracting you though. This isn’t an extended and tiresome debate about whether GUIs or CLIs are the superior interface choice. It’s clear each has its place depending on the context and task at hand.

It’s about that gaping divide. When we confined end users to the GUIs and hid the command line away from them, we took away access to powerful primitives and the flexibility to write custom code the way programmers can. Their experience of how a computer works and what it can do diverged dramatically. They have no control over how the system works or what functions are available Outside of emailing customer support or stacking one more feature request onto

3. Notion, before it was Notion

If a regular user in 1980 46ya wanted to write a small programme to automate part of their workflow, the tools to do so were ready at hand. They could chain together small, composable UNIX commands in the same environment they do everything else in.

If someone wants to try that nowadays, they’ll need to enter a strange and unfamiliar environment: the terminal. They’ll have to learn to navigate it with an unfamiliar language and set of commands. If they want to augment or interact with any third-party software – aka. all the software they have ever known – they’re in for a rough awakening. They now need to download an IDE, install homebrew, install node or python, troubleshoot $PATH errors, navigate AP

值得单独记下的观察

• Query for specific properties and data of elements within the interface
• Reference objects within the environment as variables
• Run functions that change how objects are displayed
• Run functions that change how objects behave
• Run calculations with the available data

落地时建议先做的 5 件事

1. 先写清这个工具在强化思考还是在替人思考。
2. 默认交互不要只会谄媚：该追问、该给反例、该要求证据。
3. 智能体界面要露出推理步骤，而不是只给一个光滑答案。
4. 知识发布用可生长的笔记，而不是一次性营销长文。
5. 改产品前先画隐喻：用户以为自己在做什么，系统实际在做什么。

和智能体产品怎么接

龙虾PRO做 OpenClaw 落地时，最该从这类笔记里拿走的是「别把聊天框当唯一界面」。数字员工要能追问、能验证、能把过程摊开，而不是只负责说好话。

本文侧重全链路风控方法论。落地时请用自身业务单据做回放验证，不要把示例阈值直接当生产策略。 相关：风控体检 · 方案资源