01
ZhangYvJing's
Daily Brief
00
Film / Book Chapter
First Man
First Man (2018) · Damien Chazelle
今天适合看《First Man》,因为它更像一次生活和判断方式的校准,能把注意力从持续输入里稍微抽出来,重新放回你真正想怎样生活和做事上。
The Beginning of Infinity
The Beginning of Infinity · David Deutsch
Chapter 1: The Reach of Explanations
A broader chapter for sharpening what counts as a good explanation, useful when daily inputs are full of claims, demos, and partial narratives.
01
Insight
今天的输入更像几股不同语气的材料同时挤在一起:社区链接在暴露工程和产品环境里的真实焦点,长视频在把这些焦点放回更完整的语境里,研究材料则提醒人热度和可落地性并不总是同一件事。如果先不急着做结论,至少可以把这几条线索放在一起看:Hacker News 的 Deflock Casa Grande;Hacker News 的 Donate to GrapheneOS;Hacker News 的 Substack writers, you need a website;Hacker News 的 A walk through of the DeltaNet family of linear attention variants;Hacker News 的 Steel Bank Common Lisp version 2.6.7;Hacker News 的 Kimi K3 Architecture Overview and Notes。真正值得注意的不是单条内容本身,而是它们共同指向了什么、彼此漏掉了什么。
03
Hacker News
02
GrapheneOS 推出多种捐赠渠道,支持信用卡、币币、以及银行转账等方式。 捐款将直接用于付费研发、采购工作站、测试设备、调试线板、服务器域名及法律费用,'value' 维修成本与运营费用。 这将让社区捐赠者能够按自身偏好与成本效益进行支持,并为项目持续运作提供稳定的资金来源。
03
近期许多作家把 Substack 当作作品的“家”,却忽视了其仅是分发工具而非网站。 这背后的原因是 Substack 能快速聚集受众,却缺乏对 SEO 的控制、页面自定义和长尾内容维护。 另外,平台的政策可随时调整,导致内容所有权被收归平台,作者只能成为租户。 因此,写作者必须把自己的域名当作首要目标,以保证内容的永久可访问性。
04
05
06
07
《Delayed Gratification》发布新一期,宣布将以慢节奏取代快速新闻。其内容聚焦过去三个月的回顾,强调质量、智慧与启发,冲击了传统快报模式的即时性与碎片化。此变革将迫使记者调整采编节奏,提升深度报道的需求,并影响媒体的成本结构和读者体验。
08
Claude Mythos Preview AI模型在实验中首次揭示了针对后量子签名方案HAWK和轮次缩减AES的数学攻击路径。攻击源自模型在无人工干预情况下识别出算法内部此前未被发现的对称结构 Revolution,突破了先前假设的安全阈值。此发现不同于以往仅揭露实现缺陷的案例,标志着加密算法本身已被 AI Quit 警备检视。虽然目前未影响任何生产系统,但对标准化组织、密码学研究者以及安全评估人员意味着需重新校准漏洞挖掘流程,降低预研成本并强制纳入 AI 驱动的安全审计规范。
09
iPhone 升级计划已结束,取而代之的是全新的 Apple Upgrade 租赁方案。新方案支持按低月租方式租赁 iPhone、iPad、Mac 或 Apple Watch,并在租期结束时轻松升级或退回设备。因而用户将以更低的月付成本、可随时升级、且一次性付款风险下降,从而在使用硬件时获得更多业务灵活性。
10
Zig 编译器新增增量编译功能,只重新编译自上一次构建后修改过的函数和声明,并直接用生成的字节替换输出二进制文件,从而让重构能够在毫秒级完成。该实现依赖于先把每个源文件独立转换成无类型 SSA 表示(ZIR),并在文件级别缓存生成结果;随后在语义分析阶段把代码拆解为若干“单元”,记录每个单元的类型、常量值以及对其它ಬ同的依赖,从而在任何依赖项变更 aprovalyzed 受影响的单元。此改进将加速 Zig 开发者的迭代周期,减少多次编译所需的时间与资源开销,改变他们在项目更新时的工作节奏与构建策略。
04
YouTube
01
Full episode: https://www.youtube.com/watch?v=QbdbAhaJoCQ Me on twitter: https://x.com/dwarkesh_sp
02
Full episode: https://www.youtube.com/watch?v=OS1NZLgKM2c Me on twitter: https://x.com/dwarkesh_sp
03
Decagon builds the customer support agent that answers when you email a brand, and making that agent good for a specific enterprise is the forward deployed job. It splits in two: one side configures the agent brain, the instructions and the handoff rules for when a human should take over; the other works like product engineering, figuring out what a new enterprise needs and anticipating the requests that have not been made yet. Sunny Rekhi's point is that the line between forward deployed and product is thin, because a customer ask is often just a product feature waiting to be built. What cha
04
At Palantir, forward deployed started as a literal description: you were deployed, physically, at the customer's site, and the onboarding project was keeping the platform from falling over. Natalie Meurer's dirty secret is that the title never settled after that. It stretched across DevOps, data integration, ontology work in Slate and then Foundry, and solution architecture, until forward deployed engineering meant so many different jobs that the label stopped meaning much. Every company hiring for it, whether they call it forward deployed, customer, or deployed engineering, is describing a sl
05
It's Friday night, an enterprise sales rep needs an SAP S4 HANA integration to hit quota, and the reflexive Forward Deployed answer is yes. Leo Mehr's first principle is to pause instead: always be scoping. Saying yes to everything buries the team and often does not even serve the customer, so the job is to weigh what actually matters against the rest of the queue and decide with that context. Ramp's FDE function looks different from its Palantir origins, pointed at enterprise customers, but the discipline is the same: scope hard before you roll up your sleeves and ship. The second half is wh
06
Most of the coding agent market quietly optimizes for token usage; Cognition's deployed engineering team measures the opposite, the outcomes a customer can actually see, and reports something like an 82% reduction on the work they targeted. Jia Wu's argument is that you measure before Devin ever lands, then again once it is fully activated inside the customer, so the value is a real delta and not a vanity number. The way that value shows up is not linear: one team using the agent is a step function, a whole enterprise using it is parabolic, because the products Cognition builds and the custome
07
From building no-code products at Airtable to leading Core Product Engineering at OpenAI, Akshay Nathan has spent much of his career trying to make the power of software accessible to people who do not write code. In this episode, Akshay joins swyx and Vibhu to unpack the launch of ChatGPT Work, why Codex unexpectedly took off among nondevelopers inside OpenAI, and the company’s broader plan to bring useful agents from software engineers to knowledge workers and eventually everyone. We go deep on the shared agent harness behind Codex and ChatGPT Work, why OpenAI brought the experiences togeth
07
Papers
01
本文解决多模态分类在真实场景下全部或任意模态缺失的挑战。作者提出 Co‑Learning 框架,强调模态间协作而非单纯融合,分别设计了基于 feature‑level 与 decision‑level 的两种推断策略,可无先验缺失模式地应对“任意缺失”情况。对 Agent/AI 产品而言,这意味着即便传感器掉线、隐私限制导致某些输入消失,模型仍能保持高准确率,降低对完整数据集的依赖,提升系统鲁棒性。
02
03
在分布式推理管线中,作者揭示了“网络驱动精度崩溃”这一新型攻击——通过波形化负 Instantiate 负载诱导慢路径资源争用,使正常用户的高精度推理被延迟并最终 souci 被丢弃,导致整体准确率急剧下降。 他们在自动驾驶边缘‑云多层追踪管线中模拟 4 000 条 Yo‑Yo burst 请求,证明 p99 延迟从 92 ms 至 2 s,平均 HOTA 降 7.0 分,并显示不同视频区间可导致 2–18.7 分的精度波动。 这表明仅凭工作负载形态即可破坏推理质量,提示工程师需关注路由、合并、调度与资源隔离的安全性。
04
为陷阱离子量子计算机生成高速алара搬运编译器,作者利用 Claude Opus 4.7/Claude Fable 5 直接从文本规格生成完整 Python 代码,并通过前置编-kloc 迭代扩展到线形、含交叉点和任意连通结构。结果显示,LLM 产出的编译器在搬运步骤上可比手工编写降幅高达 76 %(线形)且对大规模电路更优,开发周期从数月压缩至天。
05
解决的核心问题是:大型语言模型预训练时,传统的统一数据处理方案无法针对每个样本自适应,导致无效或过度处理。DataOrchestra 通过一个“orchestrator”为每个数据块决定是丢弃、保留还是清理,然后自动挑选多种下游操作(如程序化编辑或 LLM 重写),并为每一步生成具体指令,让工具模型执行。对 Agent/AI 产品工程师而言,这提供了按需调度预处理、显著提升训练效果且降低算力成本的思路,值得在实际模型快速迭代中参考。
06
多轮长期规划是基础模型代理的核心却难以把控:训练使用无序网络数据,难以拆解规划能力的获得与整合。作者先构建可控的多轮环境,系统分三阶段探究:预训阶段通过 CoT 状态转移构建显式世界模型、分析数据长度及质量对长远泛化的影响;后训阶段用 GRPO 与 OPD 区分通用规划模式与任务专用知识,并评估不同后训适用区;हाल में Multi‑Teacher On‑Policy Distillation (MOPD) 进一步实现跨环境规划模式融合与持续学习。对于从事 Agent 或 AI 产品工程的醒悟者,这套流程可直接指导数据采集、后训策略和多老师融合,显著提升代理在长时序任务中的规划稳定性与迁移能力。
07
解决医学影像模型黑箱导致临床信任缺失的问题,利用 Kolmogorov‑Arnold 网络(KAN)天然的插值拆分,生成可解释的 KAN‑Map 热图并将其作为上下文注入 Vision‑Language Models(VLM),从而提升自然语言解释的真实性和显著性图像归因的准确度。对于需要在 Agent/AI 产品中集成可解释医疗诊断的工程师来说,它提供了一种从数学可解释单元直接生成可视化与文本解释的完整流程,能显著提升系统透明度与落地可信度。
08
ClinFusion 解决多模态医学 LLM 在视觉学习与评估上的瓶颈,支持 2D、3D 图像的统一编码与临床逻辑判断。它采用分层组合的 Cascade Spatial‑Aware Locality Fusion 视觉编码器,并用 MedIF‑Bench 与 ROI‑grounded 的报告评估,预训练后在 24 个 benchmark 上超越主流开源与商用模型。对 Agent/AI 产品工程师来说,可直接将其高精度、多模态推理与检索工具结合,快速构建安全可信的医学决策系统。
08
Issue Monitor
Ready now—Actionable issues
Needs review—Awaiting a fresh check
Data statusCheck statusLive status unavailable






