跳到正文
10月20日周二
  1. meng shao47

    邵猛将给孩子做的键盘打字游戏 Keyboard Island 开源到 GitHub,此前已部署在 ChatGPT Sites。游戏由 Codex 生成,含 36 关起步、后增至几十关与无限模式,并加入按键音乐、头像实时拍摄入画、积分装饰小屋等孩子提出的需求。因有用户反馈无法访问并询问实现方式,他公开源码供交流。

    引用meng shao@shao__meng

    昨天我老婆问我 App Store 怎么付费,看了一下才知道她要给儿子买一个打字 App,收费 128 块。。 这。。小孩和女人钱这么好赚?? 我说等我半个小时,打开 Codex,把打字游戏的需求输入进去,一个 Goal 跑起来,20 分钟就做好部署到 ChatGPT Sites 了。花了几分钟看了一遍,还不错,顺手再加了一个实时拍摄人像,让头像作为游戏主角的功能,30 分钟准时交活儿。 效果怎么样呢?我第一版做了 36 关,儿子一连玩了 18 关 😁😁😁,我边看他玩,边看有什么问题,边让 Codex 改,顺便增加了几十关,和无限模式。。 以后儿子再有什么想玩但花钱的游戏和应用,自己做就行了,大家感兴趣可以看这: https://keyboard-island-doudou.groovy-river-7567.chatgpt.site

  2. WorkBuddy26

    我们发布了很多功能。这一个是因为我们自己确实需要才做的。 如果你在多个屏幕上同时盯港股和美股持仓,它能帮你减少干扰。

    引用Tencent Cloud International Developer@tenctcloud_Intl

    Quotes, positions, open orders—too many tabs? Build an investment assistant for Hong Kong and US stocks with WorkBuddy + Futu MCP + Hy4 preview. The walkthrough covers setup, permissions, account checks, and tracking orders, with prompts you can reuse. 👇 https://x.com/i/article/2112200966141575169

  3. Thomas Wolf56

    Thomas Wolf 转发 @JackBoylan_98 的演示:Fish Audio 的 Drama-3 被添加进开源 speech-to-speech 项目,作者克隆了自己的声音,可通过说话直接让模型耳语、大笑、叹气或表现担忧,并感谢 @andimarafioti 的演示与采样建议。PR 与配置见 https://github.com/huggingface/speech-to-speech/pull/725。

    引用Jack Boylan@JackBoylan_98

    added Fish Audio’s Drama-3 to speech-to-speech 🎭 cloned my voice. now I can ask it to whisper, laugh, sigh or get worried, just by talking. cheers to @andimarafioti for the demo + sampling tips! PR + setup: https://github.com/huggingface/speech-to-speech/pull/725

  4. Muse30

    世界上最温和的速成课 @JJEnglert:个人智能体的又一个绝佳用例:备考 我正在准备一项技术认证,已经把所有的备考考试/资料都训练给了我的 @Muse 智能体。 然后,我让它全天随机给我推送突击问题,并跟踪我的进度。 在几周都找不到整块时间坐下来学习之后,这个方法对我非常有效:一天中每小时大约一两个问题,且避开我正在开的会议(它知道我的日历)。 强烈推荐!

    引用JJ Englert@JJEnglert

    Another fantastic use case for personal agents: study prep I'm preparing for a technical certification right now, and I've trained my @Muse agent on all of the prep exams / materials. Then, I have it sending me random pop questions throughout the day, tracking my progress. After weeks of not being able to find hours to sit down and study, this method has worked very well for me: about a question or two each hour of the day, outside of the meetings that I am in (it knows my calendar). Highly recommend!

10月19日周一
  1. meng shao71

    Addy Osmani 分享其团队在 Agent 时代重构代码审查的做法:当 Claude 编写了 Claude Code 约 90% 的代码、6 月到 9 月合并 PR 数量翻倍以上且回滚率下降超过 40% 时,瓶颈从写代码转向证明代码可用。

    引用Addy Osmani@addyosmani

    Give your agent a way to verify its work. This can dramatically improve the quality of output. With this process in place, Claude Code was able to write 90%+ of its code itself. When generating software at a faster rate than you can review it, the bottleneck shifts to proving that it works. @bcherny and team invested enough in verification, we've been able to move fast while maintaining stability. Code reviews aren't going away, but you need to think of it differently. One human reading through line-by-line is no longer going to work as a gate, it needs to evolve into a multi-layered verification system, built with fast deterministic feedback loops for your agents. This is where e2e tests, feature maps (as @poteto has been advocating), property tests and multi-agent adversarial reviews come in. These all provide opportunities to catch errors early and fix them before things get out of hand. You don't have enough eyeballs for the amount of code being written so your focus needs to be on product intent, risk assessment and evaluating evidence rather than reviewing code. Delegate the code checking work to your automated tests, scale your approvals based on risk, and turn your test failures into living evaluations. This approach helps maintain speed without losing reliability. Let the agents do what they do best and let you focus on what makes you irreplaceable: judgement, direction, and ownership. We tried to capture how we handle code review and verification in this writeup. Hopefully it's helpful.

10月18日周日
  1. meng shao62

    作者分享斯坦福 CS336 第 10 讲「Inference」,由 Percy Liang 主讲,讲解训练完的模型如何又快又准地生成响应。

    引用meng shao@shao__meng

    Stanford、CMU 和 MIT 三所顶级大学的 5 门 AI 课程之外,再分享两门更偏理论和基础的课程。 CS336: Language Modeling from Scratch Stanford AI 课程链的顶点实现课,由 Percy Liang 与 Tatsu Hashimoto 联合执教,从零亲手构建一个完整的语言模型。 CS221: Artificial Intelligence: Principles and Techniques Stanford AI 的本科主干入门课,由 Percy Liang 执教,用统一的数学框架(学习、搜索、MDP、博弈、贝叶斯网络、逻辑)把整个经典 AI 领域走一遍。 这两门课程都来自 Stanford 大学,讲师都有 @percyliang (@stanfordnlp 教授,@togethercompute 联合创始人)。 CS336 课程地址 https://cs336.stanford.edu/ https://www.youtube.com/playlist?list=PLoROMvodv4rMqXOcazWaTUHhq-yembLCV CS221 课程地址 https://stanford-cs221.github.io/autumn2025/ https://www.youtube.com/playlist?list=PLoROMvodv4rMeDqwS1yFl3j3sR_-MQNEN

  2. meng shao67

    作者整理 Stripe 首席设计官 Katie Dill 在 Lenny's Summit 演讲的要点,讲如何用 AI 规模化扩展意图、品质与艺术性。

    引用Katie Dill@lil_dill

    If we only use AI to make the things that we already make, just faster, then we're definitely missing out on the most interesting part. From my talk at @lennysan’s Summit, here are four ideas for raising the ceiling, not just the floor: - Have a point of view [5:38] - Encode your standards into the machine [9:07] - Don't confuse done with good [12:21] - Unleash creativity and artistry [16:19] Full talk here: https://youtu.be/GLvFTMtw4Jk?si=-5TsYAjoFtgJBUS4

  3. Addy Osmani69

    Addy Osmani 分享 Anthropic 团队的代码审查经验,指出给智能体提供验证手段可显著提升产出质量,Claude Code 已能自己写 90% 以上的代码。他认为当生成速度超过人工审阅能力时,逐行人工审查不再可行,应转向由 e2e 测试、property 测试和多智能体对抗式审查构成的多层验证体系,人聚焦产品意图、风险评估和证据评估,并按风险分级审批。

    引用ClaudeDevs@ClaudeDevs

    Claude 编写了 Claude Code 约 90% 的代码。 从六月到九月,合并的 PR 数量翻了一倍多,而回退的占比下降了 40% 以上。 我们撰文介绍了我们如何改变代码审查来实现这一目标,以及如何采用它: https://claude.dev/blog/solving-code-review-at-anthropic/

    推荐理由:作者以 Anthropic 团队实践为基础,给出让智能体自证工作、把人工审阅改为多层验证体系的具体思路。

10月17日周六
  1. meng shao51

    博主 @samuel_ys92 用 AI 爬取融资规模 1000 万美元以上的 AI 公司、上市互联网公司、量化公司和 neo labs 的 AI 岗位,按北京、上海、杭州、深圳等城市地区聚类,网址 https://jobs.dinq.me,完全免费开放使用。正值秋招季,作者欢迎用户体验并提出需求。

    引用Sam Gao@samuel_ys92

    北京上海杭州深圳的AI岗位在哪? 我花了5天时间, 用AI爬取了融资规模1000万美元以上的AI公司, 上市互联网公司, 量化公司和一些neo labs的AI岗位, 并按照城市地区进行聚类. 正值秋招季, 欢迎大家体验使用, 完全免费! 网址: https://jobs.dinq.me 如果有任何想法和需求欢迎联系我!

  2. meng shao76

    作者解读 Anthropic 关于 Claude Code 代码评审重构的博客:Claude 写了约 90% 的代码,2026 年 6 月到 9 月合并 PR 翻倍以上而 revert 率下降超 40%。

    引用ClaudeDevs@ClaudeDevs

    Claude 编写了 Claude Code 约 90% 的代码。 从六月到九月,合并的 PR 数量翻了一倍多,而回退的占比下降了 40% 以上。 我们撰文介绍了我们如何改变代码审查来实现这一目标,以及如何采用它: https://claude.dev/blog/solving-code-review-at-anthropic/

    推荐理由:原文拆解了 Anthropic 重构代码评审的七层防线和收敛问题的具体解法,对引入 AI reviewer 的团队有可迁移的做法。

  3. meng shao66

    作者解读 Grok Bot 团队的 Lauren @poteto 提出的信任 AI Agent 工作成果的四层“倒金字塔”框架,主张精力按投入从多到少依次投向代码库改进、静态分析、文字性指导和人工审查。

    引用lauren@poteto

    how do you trust your agents' work more? copy this post/link and give it to your @bot or agent! 1. codebase improvements: this is just good software engineering - better architecture, stronger types and invariants, clear boundaries. agents love to copy what exists and take the shortest path, so make the easy thing the right thing. categorically eliminate problems through code and you won't need to think about it again. 2. static analysis: lint rules, tests, CI, verification (eg TLA+). very token efficient ways to catch issues ahead of time. 3. prose: comments, rules, AGENTS.md, skills - anything that can't be enforced and requires agent judgment. use it minimally, but do use /create-verification-skill. 4. human review: the hardest to scale. at the rate agents land code, it's pretty much impossible to thoroughly review every PR, so spend that effort on the highest leverage point, designing an environment where agents do the right thing by default. this forms an inverse pyramid: you want most of your effort at the top, least at the bottom. codebase improvements are deterministic, making it more token efficient, and lets you sleep more soundly at night. install https://github.com/cursor/plugins/tree/main/pstack and create a new Project: 1. look through my slack/chat messages and code review comments where i've given feedback on PRs, code, architecture 2. use /recall on my past transcripts to learn how i steer agents 3. /poteto-mode use /correct and /architect on past commits to find the most common pitfalls agents fall into, then propose a plan to rearchitect the code i own so it's more agent friendly. answer open questions with prototyping rather than defer to me, and back the plan with real data. 4. before you begin, use /sharpen + /in-your-own-words and confirm this prompt with me

  4. OpenAI Developers47

    以下是我们 OpenAI 的工程师如何使用 Codex 深入我们的代码库、找出需要关注的地方,并逐步清理维护积压:

    引用Rodrigo Roim@rrroim

    Software maintenance is changing. A few months ago, I had to tell Codex exactly where to look for dead code. Now it can find candidates in Slack, check them against production telemetry, and draft cleanup PRs. Here’s how we do this at OpenAI. https://developers.openai.com/blog/maintaining-software-with-the-gpt-6-family

  5. Dongxi 东锡 NLP74

    Anthropic 介绍其 Code Review 实践,Claude 编写了约 90% 的 Claude Code 代码,6 月到 9 月合并 PR 翻倍以上、回退占比下降超过 40%。

    引用ClaudeDevs@ClaudeDevs

    Claude 编写了 Claude Code 约 90% 的代码。 从六月到九月,合并的 PR 数量翻了一倍多,而回退的占比下降了 40% 以上。 我们撰文介绍了我们如何改变代码审查来实现这一目标,以及如何采用它: https://claude.dev/blog/solving-code-review-at-anthropic/