@TreeOfTr
Joined May 2026
been waiting to see this street for years and finally made it happen!!! SO BEAUTIFUL!!!
44
165
76
7,404
704,637
Tree retweeted
one of the best places in NYC to work remotely is the roof deck of the NY Public Library on 40th
182
342
65
10,703
555,815
Tree retweeted
Replying to @Acyn
Such a level of stupidity, ignorance, and complete lack of understanding of how the world works, never ceases to astonish me. Dear fellow Americans, don't elect complete morons again, particularly if they are also narcissistic, lying psychopaths (in addition to being pedophiles, rapists, atrocious business people, and convicted criminals)
63
102
8
1,824
63,489
Replying to @Nostre_damus
2
17
845
27,203
we published a blog on hugging face at possibly the worst time yesterday lol congrats to the HF team on the big news! 💚 here's a fine-tuning tutorial showing how to • fine-tune a tiny LFM2.5-350M model • in 100 GRPO steps using TRL • for better structured outputs blog: huggingface.co/blog/grpo-wit… colab: colab.research.google.com/gi…
Super happy to share our intention to join forces with NVIDIA in a $12,930,300,000 acquisition 💛💚 10 years after starting Hugging Face, open-source AI is at an inflection point. Thanks to the community, we’ve shown that it can be a complement, and even an alternative, to closed-source APIs. But for it to happen at larger scale, it needs more compute, more support, more collaboration and more visibility. That’s why we went to talk to Jensen, who offered to do exactly that with us. In addition to doubling down on NVIDIA’s massive contributions to open-source AI (I called them the “King of American open-source AI” earlier this year), they’ve committed to strongly supporting Hugging Face and our mission while keeping the platform open, independent and compute agnostic. The founders and the team are all staying to keep pushing this mission forward. Together, we think we can make open source the default way to build AI, with the goal of empowering 100 million AI builders to own their intelligence rather than rent it. Excited about the next 10 years! 🤗🤗🤗
13
114
7
1,002
52,852
NVIDIA might just have solved the biggest tradeoff in LLMs. Every LLM makes you pick between speed and quality. Autoregressive models like GPT give you quality, but they're slow because they generate one token at a time. Diffusion models do the opposite. They generate whole blocks in parallel, so they're fast, but that speed has always come at the cost of quality. Before we get to NVIDIA's solution, let's understand why diffusion isn't up to the mark in the first place. A diffusion LLM starts with a block of masked tokens and unmasks them over a few passes. On every pass, it reads all the text written so far and predicts the masked tokens in that block together. So the same network is doing two very different jobs at once. It has to understand the context that's already there while also guessing at tokens that don't exist yet. That's one set of weights pulled in two directions, so it never gets good at either. TwoTower fixes this by not forcing one network to do both. It clones a pretrained autoregressive model into two towers. The first is a frozen context tower that reads everything written so far, exactly like the original did. It's never trained, so the model's intelligence stays perfectly intact. The second is a trainable denoiser tower that fills in each new block of tokens in parallel. To stay on track, it constantly cross-attends back to the context tower. The two connect layer by layer, so denoiser layer 5 talks to context layer 5, and so on. That gives the denoiser the backbone's full multi-scale understanding, not just a final summary of it. This results in: ↳ 2.42x higher generation throughput ↳ Keeps 98.7% of the original model's quality ↳ Built on a 30B hybrid Mamba-Transformer MoE backbone ↳ Trained on just ~2.1T tokens, a fraction of the 25T used to pretrain the original Nothing here was trained from scratch. It's an adaptation you build on top of an autoregressive model you already have, and it turns slow one-token-at-a-time decoding into fast parallel block generation, cheaply. So if you're shipping anything latency-sensitive, check this blueprint. You no longer have to choose between the model you trust and the speed you need. Weights and code are all open-source. Link to the paper: arxiv.org/pdf/2606.26493 That said, if you want to go deeper, I wrote a detailed article that explains LLM inference from first principles, step by step. The article is quoted below.
12
78
2
484
57,101
Edward, the creator of LoRA (fine-tuning), wrote a blog post on how to post-train open-source models. I strongly encourage checking this out for anyone who's post-training.
[Must Read] One of the best open-source writeups I've seen on actually doing RL training for knowledge-work agents at scale.
7
58
634
69,185
A lot of hype around OpenAI's Astra model here on my timeline today. Apparently, this goes back to a new article from The Information, which said Astra is a "recurrent depth or looped transformer". It's always interesting to read about new or different approaches (including rumors about what the closed labs may be up to), but let's debunk this a bit. About 2 months ago, I shared the architecture details of Nanbeige, for example, where "Nanbeige4.2-3B is pretrained from scratch on 28T tokens with a Looped Transformer that reuses the layer stack to increase capacity without adding parameters." Yes, that's it. The looped transformer idea is just reusing layers in the transformer block. In the case of Nanbeige, the main idea is to reuse the same 22-layer stack (=transformer block) twice instead of once. So, effectively it extends the 22-layer architecture to 44 layers, but without duplicating the weights. In simple terms, this roughly doubles the size of the model (if we ignore the embedding and output layers for a second). But instead of requiring 2x the storage and RAM to host this model, it stays at the same size since we reuse the components. However, it's almost 2x as expensive in terms of compute, because we run the embedded text through almost 2x as many layers. Why? In the Nanbeige 4.2 technical report, the researchers found that two passes gave the best trade-off and retained about 75% of the token efficiency of a standard architecture. (More passes gave barely any gains but made the training much slower and much more expensive.) While, as far as I know, Nanbeige 4.2 is the first notable open-weight model that adopted this approach, the idea goes back to the NeurIPS paper "Mixture-of-recursions: Learning dynamic recursive depths for adaptive token-level computation". Actually, this paper proposes a mechanism that is a bit more sophisticated by adding a learned router that determines whether each token receives one, two, or more passes. So, easy tokens can exit early while harder tokens receive additional computation. In sum, Astra may be a really good model, but this shouldn't be about this "looped transformer aspect," which is just a tiny architectural tweak. Also, the statement "the new technique works in a way that obscures some or all of the AI's reasoning, otherwise known as 'chain-of-thought'" is not necessarily true with respect to the looped transformer method. It's possible that The Information journalist refers to some other technique or misunderstood the looped transformer method. Reusing layers does not by itself suppress visible chain of thought. It adds computation in hidden states before the next token is emitted, just as ordinary transformer layers do. But based on the information we have, the only plausible interpretation here is that if a model uses more of these recurrent passes, it may need to generate fewer intermediate reasoning tokens. So then more of its computation happens in latent activations that cannot be read as text. But we would get the same effect if we were scaling up the model size, like GPT 5.6 Luna -> GPT 5.6 Sol.
139
588
74
4,107
385,912
Immigrants are not stealing your jobs, they are doing the work that Americans won’t do like hard manual labor on farms. They are not “eating the dogs & cats” as JD Vance said. He later admitted he ‘creates these stories’ to get the attention of media regarding immigration issues.
57
1,062
28
2,009
40,067
Replying to @covie_93
Stupid is as stupid does. They voted their testosterone not their self interest. A story as old as recorded history.
2
5
141
Meta 2026 应届 SWE 现场面经 流程是三轮编码加一轮行为面。 第一轮:环形链表 + 课程依赖图 第一题接近 LC 708:往有序环形链表里插入一个值。验证时面试官给了一个绕回起点的用例,实现有漏洞,当场改掉了。 第二题是定制的课程安排。每门课有一组先修课和学习时长。给定一组目标课,求完成这些课及其全部先修所需的最短总时间。图可能不连通,目标课也不一定落在同一连通分量里。面试官专门问了这一点。 第二轮:回文删除 + 单词拆分 第一题是 LC 680:最多删一个字符,判断能否变成回文。随后改成最多删 k 个,而且要求写出代码,不是口头讲思路。 第二题是 Word Break 变体:词典词可以重复使用,判断整串能否拼出来。面试官还要求把时间复杂度讲清楚。 第三轮:BST 区间聚合 + 稀疏向量点积 第一题接近 LC 938:给定 BST 和数值区间,求区间内节点值之和。两个追问:改成求平均值;同一棵树会收到很多不同区间查询,怎么优化。 第二题接近 LC 1570:稀疏向量点积。追问包括:一边极稀疏、一边相对稠密时怎么处理;不能用哈希表、必须用 `(index, value)` 元组时怎么表示。这一轮对复杂度和数据表示讨论得比较细。 第四轮:行为面 单独一轮,不走简历。题型都是场景:多方意见冲突、接受反馈、项目做到一半发现原方案不行、和同事关系难处、说服经理、deadline 突然提前、承担超出原范围的工作、从更资深工程师那里学到关键东西。追问比编码轮少。 --- 小路简要分析 题目主体是中等难度原题或近原题,真正卡人的是 follow-up:改删除次数、处理不连通图、把求和改成均值、把单次查询改成多次查询、换掉哈希表示。现场要能改代码、讲清复杂度和表示取舍,而不是只报一个标准解。 行为面偏协作和判断,不考项目背诵。准备 6 到 8 个具体故事,覆盖冲突、反馈、方案失败、说服和赶工即可。刷题时把 708、680、Word Break、938、1570 以及图上的拓扑 / DP 变体练熟,并习惯面试官改约束后立刻动手改实现。
Google L4 面试到底考什么? 候选人约 4 年后端经验,实际面试里的题目很有参考价值。 最值得注意的是:没有一道题是 LeetCode / NeetCode 的原题,但做过足够多类似题目后,确实能明显降低难度。 第一道:Two Pointers / Greedy 第一轮技术面是一道比较特别的 Two Pointers / Greedy。 候选人很快找到了一个时间复杂度最优的解法,但空间复杂度还不是最优。 面试官给了一个 Hint。 根据这个提示,候选人进一步解决了一个更难的 Follow-up,而且最终达到了最优复杂度。 这道题很值得注意。 因为它考的是: 你能不能从一个看起来陌生的问题里,识别出正确的算法结构,并继续把解法优化到底。 第二道:Heap Onsite 的第一道题是 Heap。 这次就顺利很多: 看到题目后很快识别出 Heap 的思路,写完代码后继续解释复杂度和实现细节。 Follow-up 也比较直接,很快完成。 这种题其实非常典型。 Google 不一定需要你每一轮都碰到 Hard。 如果一个 Medium 题,你能做到: 理解题意 → 快速识别 Pattern → 写出正确代码 → 分析复杂度 → 处理 Follow-up 已经是非常重要的能力。 第三道:Dynamic Programming Onsite 第二道是 DP。 基础问题同样很快识别并完成。 真正有意思的是 Follow-up。 Follow-up 比较 unusual,候选人短暂卡住,但最终还是自己解决了。 这其实比“刷出一道原题”更接近真实面试。 因为面试官完全可以在你解决基础问题之后,把条件稍微改变。 如果你只是记住: “这道题应该用二维 DP。” 很可能马上失效。 真正需要掌握的是: 为什么这里可以 DP?状态是什么?状态之间是什么关系?为什么这个转移成立? 这三道题放在一起,其实很有意思: Two Pointers / Greedy → Heap → Dynamic Programming 没有特别偏门的算法。 也没有一道是 LeetCode 原题。 但每道题都在考一个东西: Pattern Recognition。 这也是这位候选人对准备 Google 面试最有价值的总结: 他第一轮之前刷了两遍 NeetCode 150。 第一遍不会的题全部标记。 第二遍重点重新做这些题。 一些比较难的题甚至做了第三遍。 之后又刷了 NeetCode 250,并做了大约 80 道 LeetCode Google Tagged。 最后他的结论反而很简单: NeetCode 150 + 真正理解 Pattern,基本够了。 还有一个很重要的细节: 实际面试题比他预想的要简单。 所以如果时间有限,会建议: Medium > Hard 不要花大量时间证明自己能做 Hard。 更重要的是把常见 Medium 做到非常熟。 看到题目后,你应该能够迅速问自己: 这是什么 Pattern? 为什么这个 Pattern 适用? 有没有更优的时间复杂度? 有没有更优的空间复杂度? 如果面试官改变一个条件,我的解法还能成立吗? 所以,如果你正在准备 Google Coding Interview,我觉得最值得练的不是: “我今天刷了 10 道题。” 而是: “我今天真正掌握了一个 Pattern。” 刷题量最终都会忘。 但如果你能做到: 陌生题 ↓ 识别结构 ↓ 想到候选算法 ↓ 证明正确性 ↓ 优化复杂度 ↓ 处理 Follow-up 那才是真正把 LeetCode 刷进了自己的能力里。 Google 面试未必在考你见没见过这道题。 它更像是在问: 给你一道没见过的题,你能不能把它变成一道你见过的题。
18
13
1
91
16,186
Our King has gone mad, is leading us to multiple disasters, and the majority in government is afraid to say so.
32
44
9
346
84,643
Netflix 每周要生成几十万条「为什么推荐这部剧」的解释,人类根本审不过来。 于是他们把 LLM-as-a-Judge 真正放进了生产系统。 这篇论文记录了 Netflix 如何搭建一套 Judge 的完整生命周期:建立人工标准、训练 Judge、上线拦截,再持续监控和更新。 其中一个设计叫 RART。 Judge 除了要判断一条解释能不能通过,还要和人工评审在「为什么失败」这件事上对齐。因为上线后,Judge 给出的失败理由会直接交给生成模型,让它重新修改答案。 理由判断错了,下一轮修改也会被带偏。 上线后,每条解释都会经过「生成 → Judge → 修改」的循环,最多重试 3 次;同时每周再抽取约 300 条结果交给人工复查,用来监测 Judge 有没有随着内容变化逐渐漂移。 最终他们做了 5 周、覆盖数千万 Netflix 用户的 A/B 测试。 加入这套 Judge 之后,用户观看未看过内容的比例提升 0.2%,成功从浏览进入播放的 session 提升 0.3%。 数字看起来不大,但在 Netflix 这个规模下已经很有意义。 现在我开始愿意把 LLM-as-a-Judge 看成一种长期运行的基础设施。 上线时对齐一次远远不够。数据会变、用户会变、生成模型也会变,Judge 自己也需要持续被检查和校准。 未来 Agent 系统里的 evaluator,可能也会逐渐拥有自己的「生命周期」。 📎 arxiv: arxiv.org/abs/2608.18300
10
59
1
295
21,134
🚨Anthropic 重新启动了他们的校园大使计划。 Claude Campus Ambassador 计划正式重新开放申请,今年直接拆成了三条线: 本科生加入 Claude Builder Club,在学校里办 AI workshop、Hackathon、Demo Night,建立 Claude 开发者社区。 研究生加入 Claude Campus Conversations,更偏 AI、教育和社会议题,会组织讨论、展示学生项目,还有机会去 Anthropic 办公室。 博士和博士后则进入 Claude Science,重点是 AI for Science,可以组织科研 workshop,并直接和 Anthropic 的数学、科学团队以及研究员交流。 三条路线都有一个很实在的待遇:3600 美元 stipend。 项目从今年 9 月持续到明年 6 月,9 月 12 日截止申请,全球 18 岁以上学生都可以申请,不过部分研究生和博士项目早期会限制学校范围。 其实最有意思的是 Anthropic 对校园这件事的投入明显变重了。 之前 Campus Ambassador 更像一个学生社区项目,现在已经开始按照本科、研究生、博士分别设计路径。 本科抓开发者,研究生抓 AI 社区和影响力,博士直接抓科研人才。 Claude 这是准备从大学开始,把下一代 AI 用户、开发者和研究员一起养起来了。
Applications are open for the Claude Campus Ambassadors program. This year, we’re expanding opportunities to more students, with three tracks for undergrads, graduate students, and PhDs/postdocs. Apply here: anthropic.com/campus
2
4
1
42
23,106
🚨因为AI的发展突飞猛进,斯坦福软件工程课里85%的内容就过时了。 斯坦福最新公布了2026年秋季课程 The Modern Software Developer,负责课程的教授直接说: 2025年秋季课程里,85%的材料已经过时。 原因很简单,去年11月Claude Opus 4.5之后,Coding Agent的能力发生了一次明显跃迁,软件开发的工作方式也跟着彻底变了。 所以今年课程几乎重新设计。 学生要学的已经不是怎么更熟练地手写代码,而是: Agent Skills 高级Context Engineering MCP Agent-ready代码库 Agentic Code Review 安全 并行后台Agent Software Factory 甚至每个学生都必须直接给真实世界的生产级开源项目提交PR。 目前课程的合作项目包括Browserbase、HeyGen、OpenHands、Milvus、CrewAI、Warp、Vercel、Unsloth、Anyscale等一大批AI项目。 课程的核心是LLM时代,AI-native Developer会成为软件组织里最重要的一类人。 以前大学教你怎么写软件。 现在斯坦福开始教你,怎么管理一群Agent写软件了。 9月22日开课,所有课程和资源都会免费公开。
I’m excited to finally announce the newest edition my Stanford course 𝗧𝗵𝗲 𝗠𝗼𝗱𝗲𝗿𝗻 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿. It has been 9 months in the making. Last November, with the release of Claude Opus 4.5, coding agents experienced a step function improvement in capability. We all felt it. The LLMs were more powerful, could reason for longer, solve harder tasks. This year’s iteration of my course reflects the 2026 metamorphosis of software engineering. My core belief is simple: AI-native developers of the LLM era are going to become the most important members of any software organization. I have designed my course to train this next generation of engineers. 𝗪𝗵𝗮𝘁’𝘀 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁 𝘁𝗵𝗶𝘀 𝘁𝗶𝗺𝗲 𝗮𝗿𝗼𝘂𝗻𝗱 First, 85% of my Fall 2025 class material is being thrown out. The Fall 2026 syllabus reflects the core capabilities AI-native engineers must have: agent skills, advanced context engineering, MCP portals, agent-ready codebase principles, agentic code review, security, parallelizing background agents, software factories, and more. Second, I am going to teach my students how to have software taste. Every student will be required to ship pull requests to production-grade, real-world codebases. The course is collaborating with the top open-source AI repos who will offer support and mentorship to students on how to meaningfully contribute to their projects. This has never been done before in any university course so I am incredibly grateful to our OSS Partners: @browserbase, @HeyGen, @CopilotKit, @semgrep, @OpenHandsDev, @milvusio, @marimo_io, Pi, @crewAIInc, @warpdotdev, @vercel, @cmux, @arizeai, @UnslothAI, and @anyscalecompute. 𝗪𝗵𝗮𝘁’𝘀 𝘀𝘁𝗮𝘆𝗶𝗻𝗴 𝘁𝗵𝗲 𝘀𝗮𝗺𝗲 I’m fortunate to again have AI software engineering leaders and founders as guest speakers to share their learnings from building top coding agent products. Thank you to @leerob from @cursor_ai, @bcherny of @claudeai code, @EnoReyes of @FactoryAI, @silasalberti of @cognition, @0xine of @semgrep, Rajesh Bhatia of @Cloudflare , @amasad of @Replit, and @eladgil. All resources will be available online. All classes will be available to the public. 9/22 on Stanford campus. See you in class.  themodernsoftware.dev/
71
285
9
1,472
275,281
Tree retweeted
To the hacker who attacked me on Sep 1: I haven't had any income for 3 years. the $170k you transferred out is all my savings — the money supports me write my code 16+hrs per day for chasing my dream. I have to move on, I need to provide for my family and keep chasing my dream. I would appreciate it if you could return some of it, for the rest, you won. for the timeline: 1. 6am UTC, you withdrew my funds from @Morpho 2. 9am UTC, you exchanged them into ETH on @base and into BTC, I had a 3-hour window, but I didn't get my alerts about the activities of my account, that is my fault 3. 9am UTC — same time, you hacked all my twitter accounts. I still have no clue how I got hacked. over the past few months, 3 apps were installed on my mac: one from a well-known company, one a well designed OSS project and one developed by my previous colleague's kids. I chose to trust all three. so it's very likely you came in through the supply chain? but even the ACP I was using these days was the official version and pinned. with @claudeai's help, it suggested you may have used osascript + System Events to do the phish for my passwd, then take my @googlechrome sessions. I was heavily developing my desktop app, that is so sad, but you reminded me that the sandbox env for agents is more important than I thought, which leads me to focus more on this part in @crabtalk_ai , thanks for that point.
383
127
58
1,939
589,712
Trump says Americans have too many holidays and that people need to work more days to boost his failing economy
Medicare/Medicaid Administrator Dr. Oz: If we could get the average American want to work one extra year, that's worth $1T to our GDP
2,418
3,059
2,572
17,980
6,327,352
He went from, "Make America Great Again,” to, "You peasants need to worker harder and longer hours to bail out my failing economy.”
Trump says Americans have too many holidays and that people need to work more days to boost his failing economy
136
398
11
2,152
61,543
BREAKING: Trump says Americans have too many holidays and need to work more days to boost his failing economy.
2,977
2,667
1,577
13,857
2,691,122