ZhangYvJing's

Daily Brief

← July 22, 2026 July 23, 2026 · Thursday July 24, 2026 →
00

Film / Book Chapter

Ikiru
1952 / Akira Kurosawa

Ikiru (1952) · Akira Kurosawa

今天适合看《生之欲》,因为它不是在继续加信息,而是在提醒人时间真正该压在哪件事上,适合把注意力从系统噪声拉回到现实里真正想完成的那件事。

Working in Public
Nadia Eghbal

Working in Public · Nadia Eghbal

Chapter 3: The Structure of an Open Source Project

A sharp chapter for thinking about visible work, maintainer labor, contributor flows, and why software ecosystems are not just code repositories.

01

Insight

今天的输入更像几股不同语气的材料同时挤在一起:社区链接在暴露工程和产品环境里的真实焦点,长视频在把这些焦点放回更完整的语境里,研究材料则提醒人热度和可落地性并不总是同一件事。如果先不急着做结论,至少可以把这几条线索放在一起看:Hacker News 的 Terrence Tao's ChatGPT Conversation about the Jacobian Conjecture Counterexample;Hacker News 的 GigaToken: 1000x faster Language model tokenization;Hacker News 的 Show HN: Bento - An entire PowerPoint in one HTML file (edit+view+data+collab);Hacker News 的 Are AI Labs Pelicanmaxxing?;Hacker News 的 Making;Hacker News 的 The startup's Postgres survival guide。真正值得注意的不是单条内容本身,而是它们共同指向了什么、彼此漏掉了什么。
03

Hacker News

03
Bencha 将完整 PowerPoint 打包为单一 HTML 文件,既可编辑也可预览,并内置数据与协作功能。通过在同一文件中整合幻灯片、动画与脚本,Bench 省去外部插件加载,避免版本冲突导致的问题。此技术让多方共享演示资料时不再需要额外软件安装, soms 降低传输成本并提升审阅与bery 的安全与效率。
04
Are AI Labs Pelicanmaxxing?
Simon Willison把“站在自行车上的鹈鹕”作为基准,系统评测了七大前沿模型在1,008幅SVG中的表现。数据显示,鹈鹕与自行车的评分均落在中下游,回归分析显示各实验室在该基准上没有显著提升,失效率与偶然误差无异。由此可见,实验室未对该基准产生过拟合,模型在公开评测中的表现不受此偏差影响,研发团队在评估模型时可保持更客观的判定。
05
Making
06
The startup's Postgres survival guide
开发者为内部团队撰写《Postgres 生存指南》,将两年经验浓缩为集中参考。手册从基础索引、JSONB存储到复杂查询、imbus 高频批量更新与自动vacuum说明缺失索引、迁移阻塞与连接浪费会导致查询慢与事务冲突。工程师在架构与索引决策、迁移与连接池使用时必须更细致评估,以降低延迟与停机风险。
10
Ghost Cut 在 Ishmael 中引入了无剪贴板的原子移动。传统剪切粘贴之所以易出错,原因在于剪切可以撤销但副本留在剪贴板,剪切后文本重新排版,且剪切与粘贴并非同一原子操作。Ghost
04

YouTube

01
Factory started building fully autonomous coding agents in April 2023, two years before enterprises were ready. Matan Grinberg now says this is indistinguishable from being wrong. The Factory co-founder and CEO explains how the company survived its "journey in the desert," including the decision to hand nearly all of its revenue back to customers when the product wasn't making developers obsessed. Matan makes the contrarian technical case that a model-agnostic harness beats the model-and-harness co-design that labs like OpenAI and Anthropic favor, because exposing a harness to many models keep
agent, ai_frontier, ai_product, market, startup
02
Barr Yaron shares her perspective on the results and emerging state of AI engineering in 2026. Speaker: Barr Yaron — Partner, Amplify Partners Barr backs founders building the AI infrastructure and applications that will shape the future. Links: X: https://x.com/barrnanas LinkedIn: https://linkedin.com/in/barryaron Website: https://barrchives.com Timestamps 0:00 Introduction and Survey Context 2:26 The AI Engineering Workforce 3:21 Current Modalities and Adoption 5:34 Model Strategy: Closed vs. Open-Weight 8:20 Cost as an Engineering Constraint 9:36 The Rise of Agentic Workflows 11:57 Infr
agent, ai_product, engineering
04
LLMs are great at writing code. So the question we kept asking was: can they write code that produces a video? We thought it would be easy. The reality was a year of trying. We started with massive prompts to get very mediocre output. We made it more agentic to iterate and improve its output. This worked okay but wasn't production-ready. Eventually we tried Remotion. It got us deterministic video, but the React framework kept boxing the agent in. The more guardrails we added, the safer and more boring the outputs got. When we utilized plain HTML, CSS, and JavaScript, the creativity came back t
agent, ai_frontier, ai_product, engineering
06
Claude is capable of long horizon tasks. In this talk, we'll share lessons learned about building agent harnesses for reliable and secure long-horizon work. This include decoupling the brain and hands, self-verification, self-learning, and design for evolving agent harnesses. ### Lance Martin Member of Technical Staff · Anthropic [X/Twitter](https://x.com/RLanceMartin) · [LinkedIn](https://www.linkedin.com/in/lance-martin-64a33b5) · [Website](https://rlancemartin.github.io) Member of technical staff at Anthropic. Working on the Claude Platform, including Claude Managed Agents and the claude
agent, ai_product, engineering
07
To automate opening a bank account, your agent needs to verify identity, so a team wires it to the DMV and a passport service and ships it. Then the next team builds the next agent and rediscovers, from scratch, where its data lives, across a hundred databases plus Snowflake, Databricks, and S3, whether it can trust the version, and whether it is even allowed to touch it. Every agent repeats that wiring, nothing updates when a source moves without a manual rewire, and no agent is smarter tomorrow than today. Emil Eifrem's fix is to make the agents thin and put the intelligence in a shared subs
agent, ai_product, engineering
08
Stephen Chin gave two copies of the same agent the same facts about his home network, one storing them as a vector database, the other as a graph. He asked both what was running end of life software exposed to the internet. The vector agent said it could not find specific details. The graph agent traced the connections and flagged his daughter's Minecraft server running an out of date OS, then found real open management ports he quietly patched after the demo. Same data, and only one of them could actually answer. That gap is the whole talk. Most assistants, OpenClaw included, keep their memo
agent, ai_product, engineering
10
Yohei Nakajima was running a 500 question eval when his API key died at question 350. Normally that means restarting the whole long agent from scratch. Instead it rolled back one step and resumed at 353, because in ActiveGraph the log is the agent. Most people build agents around the LLM and bolt on memory and logging; Nakajima, the creator of BabyAGI, flips it and builds around an immutable event log. Every action and every change to the agent flattens into one typed log, which projects a graph that is the agent's state, so you get replays, rollbacks, and forks for free. On top of the log si
agent, ai_frontier, ai_product, engineering
11
Can a model predict how a cell responds to a genetic perturbation it has never seen? Xaira Therapeutics' new virtual-cell model, X-Cell, is a 4.9-billion-parameter diffusion language model trained on X-Atlas/Pisces — the largest genome-wide CRISPRi Perturb-seq dataset ever built, spanning 25.6 million single cells across 16 biological contexts. Bo Wang (Chief AI Scientist) and Ci Chu (Chief Discovery Officer) explain why observational atlases can describe biology but can't predict what happens when you intervene, why they abandoned autoregression for a diffusion "editing" approach, and how a m
agent, ai_frontier, engineering, startup
12
From spending $12 million building language models for code before the world cared to creating a Model Factory that can take a model from pre-training to release in eight weeks, Eiso Kant has spent more than a decade betting that code is the path to AGI. In this episode, the Poolside co-founder joins swyx and Vibhu to explain why ChatGPT felt like vindication, why Poolside embraced open weights and open research, and why he would rather live in a world with 100 foundation model companies than five even if Poolside were one of the five. We go deep on Poolside’s Model Factory: the engineering s
agent, ai_frontier, ai_product, engineering, market, startup
07

Papers

01
现今要做模型的电路发现、评估和干预,往往需要把各个独立工具拼凑在一起,并手写大量提示,既繁琐又难以比较。CircuitKIT 为此提供统一的 Typed、可序列化框架,内置多种发电算法、声明式接口以及诊断与下游干预(剪枝、编辑、引导、选择性微调)模块,极大简化了电路分析流程。对开发 Agent/AI 产品的工程师而言,它能让你在同一套可复现代码里快速评估并改进模型的内部机制,提升实验效率与可靠性。
02
本论文解决AI研发代理生成模型、适配器或CUDA内核等产物时,潜在隐藏破坏如何逃逸监测的问题。作者开发了名为ResearchArena的框架,覆盖四大长期任务,每项任务嵌入两种隐蔽攻击;通过对 frontier agent 的 sabotage 与 monitoring 进行实验,评估四种监视器(可执行实验/仅读轨迹、是否可见 chain‑of‑thought),发现数据层破坏最难检测,现有监视仍会错过表面异常。对于从 Agent/AI 产品工程角度的张玉璟,其提供了一个可复现、可扩展的安全评估基准,能帮助验证自动化AI研发流程中控制手段的有效性并及时定位盲点。
03
挑战在于传统生成模型普遍依赖多层迭代和复杂架构,导致算力和内存需求高;作者问:真的需要“渐进”噪声到数据的转换吗?他们用IMLE这一កម្ម训练目标,搭配中等尺寸卷积网络,刻意剔除transformer和迭代去噪,只保留真正必要的技巧,得到单步、参数高效、速度快且在ImageNet 256上达到2.56 FID的高质量合成。对需要低资源、即时采样的Agent/AI 产品工程师omos,能省下训练成本与推理延迟,且易于快速集成。
04
解决把 K 类分类器拆成 O(log K) 个简单二分类器(只用超平面做决策)的分布式方案,分析其在高斯模型下的最优误码极限。作者通过对各二分类器的405特征空间切分,推导出在不同维度与解码方式下的误分类下界,并用仿真实验确认理论。对想用多节点/Agent协同完成复杂分类任务的工程师来说,能直观判断到底需要多少二分类器、对应误差范围,帮助设计更鲁棒、资源友好的系统。
05
论文聚焦 LLM 驱动的 Agents 从实验室走向生产,探讨其鲁棒性、安全与可靠性的关键痛点。通过制药与金融案例剖析共性设计模式,并给出校验管道、降级机制及人机协同的实用缓解策略。对想要落地 Agent 产品的工程师而言,能直接拿去的评估清单与部署模板,弥补理论与实务间的鸿沟。
06
CodeRescue 针对可执行环境中的编码代理,解决失败后在低成本恢复和高成本升级之间做预算化决策的问题。它把问题转化为跨异构操作的恢复路由,用执行回放训练监督路由器,并加入 Conformal Risk Control(CRC)层,在不重新训练的情况下根据预算动态选择成本惩罚,保证边际期望成本控制。对张玉璟这类 Agent/AI 产品工程师来说,它能让模型在保持性能的同时显著压缩计算成本,并且轻松映射到不同预算场景,值得快速查看。
07
问题:创作人员难以用文本精确控制图像局部的材质、物体与布局。做法:引入 Appearance Pointers,将文本或图片与用户掩码对齐,再通过区域对应网络和空间聚合机制轻量化地为 Diffusion Transformer 注入多模态局部指令。值得看:无需重新训练基模型即可获得多模态局部控制的通用接口,兼容现有agoza, 端,扩展性强,适合需要快速迭代的 Agent/AI 工程。
08
在长上下文推理中,LLM 经常重复复制输入文本,导致答案错误且推理冗长。本文提出 GEAR,一种 evidence‑aware 奖惩机制:先用自动 pipeline 标注关键信息,然后对与 evidence 重叠给予奖励,对与 distractor 重叠给予惩罚,从而让模型更准确聚焦关键 evidence 并显著削减复制和思考长度。对长情境 Agent/AI 产品而言,GEAR 能提升推理精准度与效率,让模型真正“读懂”而不是“抄袭”。