New skill: /apple-design
Apple’s WWDC videos are a goldmine of knowledge. I’ve combed through my favorite ones and came up with 17 design and motion principles.
Use them to review existing work or when working on something new to get it right.
https://t.co/jCwhthpi20
“Loop engineering” is a hot buzzphrase after mentions of it by Boris Cherny (Claude Code’s creator) and Peter Steinberger (OpenClaw's creator) went viral on social media. Loops are now a key part of how we get AI agents to iterate at length to build software. In this letter, I’d like to share my 3 key loops, shown in the image below, for building 0-to-1 products. These loops guide not just how I build software, but also how I decide what software to build.
Agentic coding loop: Given a product specification and optionally a set of evals (that is, a dataset against which to measure performance), we can have an AI agent write code, test its work, and keep iterating until the code is bug-free and meets its specification. This idea of closing the loop took off around the end of last year, and it has been a game changer in enabling coding agents to work longer productively without human intervention. For example, over the weekend, I was building an app for my daughter to practice typing, and my coding agent could easily work for around an hour, using a web browser to check what it had built multiple times before getting back to me, without needing my intervention.
The engineering loop executes quickly. Every few minutes, the coding agent might build and test a new version of the software. I hear frequently from developers who are finding new ways to engineer more effective engineering loops. This is an active area of invention!
Developer feedback loop: In this loop, a developer examines the current product and steers the coding agent to improve it. Last year, a lot of developers (including me) were acting as the QA (quality assurance) function for our coding agents, manually finding bugs and then asking the agent to fix them. But with coding agents much more able to test their own code, the amount of time we need to spend on this function has decreased significantly. This allows us to make higher-level product decisions, such as what key features to offer, where the UI needs improvement, and so on.
The developer-feedback loop operates over time intervals between tens of minutes and hours — that's how frequently a developer might review a product and give feedback. In the case of the typing app, I changed my mind a few times about the visual design, what cat costumes she can unlock as she learns (she loves cats), and the user flow for a grown-up to log in and steer the child's learning experience.
When a developer has a clear vision for what to build, it is still a lot of work to translate that vision into a specification for a coding agent to implement. Further, after the developer has seen an implementation, they might update (or perhaps clarify) the spec to steer it toward what they want. If you find that the system repeatedly runs into certain problems, building a set of evals for the agent becomes useful.
AI-native teams are increasingly using AI to help shape product direction, for example, automating the gathering and analysis of usage data, summarizing written and verbal customer feedback, or carrying out competitive analysis. However, for pretty much all the products I’m involved in, I see humans as having a significant context advantage over current AI systems — we know a lot more than the AI system about the users and the context the product has to operate in — and thus humans play a critical role. Many people describe this human contribution as “taste,” but I prefer to think of it as humans having a context advantage, since that gives us a clearer path to helping AI systems get better. This also speaks to why this step can’t be automated: So long as the human knows something the AI does not, human-in-the-loop is needed to to inject that knowledge into the system.
External feedback loop: This includes a wide range of tactics like asking a few friends for feedback, launching to alpha testers, or putting the code into production with A/B testing. These tactics are usually slow, rarely taking less than hours and sometimes taking days or even weeks. This data informs the developer vision, which in turn continues to drive the detailed product spec, which in turn drives the coding agent.
With coding agents speeding up software development, more engineers are starting to play a partial product management role. For many engineers who are growing into this role, the hardest part is shaping the product vision and striking a balance between building (bridging the gap between vision and spec) and getting user feedback to evolve the vision. It is important to do both!
I will write more about how to do this in future posts, but for now, I find it encouraging that engineers are playing an expanded role (just as product managers and designers now do more engineering).
[Original text: The Batch]
原文的评论中有人说提了这篇文章:《Inside the Transformer: The Life of a Token》
https://t.co/sFDLVz8oHz
如果看完了原帖这篇文章,可以当这篇文章的进阶版,可以更深的了解,文章详细追踪一个 Token 在现代 Transformer 中的完整前向传播过程,有很多实战实现细节。
图做的很好,而且很丰富,很多细节,结合真实模型讲解,干货很多,但是难度高一些,适合有一定基础的朋友
How to setup persistent Codex memory in Obsidian
1. Copy the below prompt into Codex. The prompt instructs Codex to create the memory folders in Obsidian
2. Copy the below custom instructions. They instruct Codex to use Obsidian Codex memory to save memories
That's it!
推荐Anthropic 13 门免费课程,还附带证书
我按 12 周排好顺序,简单到困难一步一步学
第 1–2 周|基础
1. Claude 101
上手 Claude 的日常使用,是后面所有课的前置。
https://t.co/8bdokywcqp
2. AI Fluency: Frameworks & Foundations
人机协作的四原则,建立怎么跟 AI 合作的心智模型。
https://t.co/1kmj6lhzgQ
第 3–4 周|接 API
3. Building with the Claude API
旗舰课 8 小时,从基础调用打到生产部署。
https://t.co/kD0wbhhvkb
第 5–6 周|MCP 协议
4. Introduction to Model Context Protocol
工具、资源、提示三要素入门,把外部工具接到 Claude。
https://t.co/tSTbHR7KOv
5. MCP: Advanced Topics
用 Python 深度构建 MCP server 和 client。
https://t.co/DV8iX8kSMz
第 7–8 周|Claude Code 与 Skills
6. Claude Code in Action
配 CLAUDE.md、Hooks、CI 集成,把它变成日常工具。
https://t.co/poSvymIGCR
7. Introduction to Agent Skills
写、配���、分发可复用的 Skills,agent 的积木。
https://t.co/htcluL5rTg
第 9–10 周|上云
8. Claude with Amazon Bedrock
在 AWS 上跑 Claude,IAM 与企业账号调用模式。
https://t.co/ai3OvOaleU
9. Claude with Google Vertex AI
在 GCP 上跑 Claude,与 Vertex 其他服务串联。
https://t.co/1jQdRfaxVR
第 11–12 周|角色专项
10. AI Fluency for Students
学生怎么把 Claude 当导师而不是作弊器。
https://t.co/ksFCTi8yOk
11. AI Fluency for Educators
教师怎么把 AI 融入课堂与作业设计。
https://t.co/8r22qINF2q
12. Teaching AI Fluency
怎么把四原则教给别人,培训师工具包。
https://t.co/PUoCqEHYyW
13. AI Fluency for Nonprofits
公益组织在预算和合规下怎么落地 AI。
https://t.co/hkkOrn4SRB
全免费,全官方。先 mark 再开学
你也可以看看下面我关于Agent记忆的爆文👇