Puran
TIL Photos Reading Weekly Current Shelf Search Stats
  • 30 Days · 30 AI Papers

    30 Days · 30 AI Papers

    从深度学习到现代大模型:一份以研究问题和技术演进为主线的 30 天论文阅读计划

    版本:2026-10-21 · 阅读对象:希望构建 AI/LLM 知识体系、具备软件工程基础的学习者

    目标与使用方法

    这不是“30 天读完 30 篇全文并复现所有实验”的课程。目标是建立四条可以相互连接的技术脉络:模型范式(8)/ Infra 与数据(6)/ 语言模型(9)/ 多模态(7);读完可以独立回答每篇论文当年解决了什么、为什么有效、影响了后续什么。

    每天 45–75 分钟:① 10–15 分钟看 Abstract、Introduction 和 Conclusion;② 20–35 分钟理解关键架构图、1 个关键公式和实验;③ 10–20 分钟记录自己的解释。李沐视频为按需补救材料,不要求视频从头看到尾。高难度论文可先读核心图/实验,公式推导留给二刷。

    难度是相对本计划的主观估计:入门 / 进阶 / 挑战。经典指在谢青池分享涉及的研究脉络中;补充指为延伸至现代 LLM 而增加,并不代表质量高低。视频仅在李沐官方已录制清单核对过才附上。GPT-1/2/3 共用一条李沐串讲视频。

    配套参考

    • 李沐官方论文精读仓库 · 李沐:如何读论文(6 分钟)

    • 谢青池《Let’s Dive into Papers Together》完整视频:模型范式 19:35 · Infra 与数据 1:52:58 · 语言模型 2:21:29 · 多模态 3:08:08

    • The Bitter Lesson — Rich Sutton(可作为 Day 12 的短文补充)

    第一段:基础架构与语言模型起点

    从 CNN、Embedding、Seq2Seq、Attention 到 GPT/BERT,建立模型“学什么、如何表示和如何计算”的直觉。

    Day 论文 · 原文 方向 难度 当天要回答的问题 李沐视频
    01 AlexNet (2012) 模型范式 入门 为什么数据、GPU 与 CNN 的结合成为深度学习突破的转折点? 精读视频
    02 Word2Vec (2013) 语言模型 入门 词语如何变成有语义关系的向量? —
    03 GAN (2014) 多模态 进阶 生成器和判别器的对抗训练如何产生新样本? 精读视频
    04 Neural Machine Translation with Attention (Bahdanau) (2014) 模型范式 进阶 Seq2Seq 的固定长度表示有什么瓶颈,Attention 如何改进? —
    05 ResNet (2015) 模型范式 入门 为什么残差连接能让更深的网络更容易训练? 精读视频
    06 Sparsely-Gated Mixture-of-Experts (2017) 模型范式 挑战 为什么可以增加模型容量,却不等比例增加每个样本的计算? —
    07 Attention Is All You Need (2017) 模型范式 挑战 Self-Attention、多头注意力和位置编码怎样组成 Transformer? 精读视频
    08 GPT-1 — Improving Language Understanding by Generative Pre-Training (2018) 语言模型 进阶 为什么自回归语言模型可以通过预训练迁移到下游任务? 精读视频
    09 BERT (2018) 语言模型 进阶 双向表示学习和 GPT 的自回归训练目标有何不同? 精读视频
    10 GPT-2 — Language Models are Unsupervised Multitask Learners (2019) 语言模型 入门 规模化预训练如何开始表现出无需任务微调的能力? 精读视频

    阶段验收:不看笔记,用一张草图讲清楚:Embedding → Seq2Seq/Attention → Transformer → GPT/BERT。

    第二段:规模化与大模型能力

    连接内存与并行、Scaling、In-context Learning、生成模型、对比学习和指令对齐。

    Day 论文 · 原文 方向 难度 当天要回答的问题 李沐视频
    11 ZeRO (2019) Infra 与数据 挑战 优化器状态、梯度和参数怎样分片,才能训练大模型? 精读视频
    12 Scaling Laws for Neural Language Models (2020) Infra 与数据 挑战 模型参数、数据和计算量如何影响预测损失? —
    13 GPT-3 — Language Models are Few-Shot Learners (2020) 语言模型 进阶 为什么可以仅靠 Prompt 中的例子学习新任务? 精读视频
    14 DDPM — Denoising Diffusion Probabilistic Models (2020) 多模态 挑战 为什么逐步加噪和反向去噪能够构成生成过程? —
    15 Vision Transformer (ViT) (2020) 多模态 进阶 如何将图片切成 Patch,并用 Transformer 处理? 精读视频
    16 CLIP — Learning Transferable Visual Models from Natural Language Supervision (2021) 多模态 进阶 图像与文字如何通过对比学习建立共同的表示? 精读视频
    17 LoRA (2021) 模型范式 进阶 为何可以冻结基础模型,仅训练低秩增量完成微调? —
    18 Latent Diffusion Models (Stable Diffusion) (2021) 多模态 挑战 为什么在潜空间扩散可以显著降低图像生成成本? —
    19 Chain-of-Thought Prompting (2022) 模型范式 入门 示范中间推理步骤在什么条件下改善复杂任务表现? 精读视频
    20 InstructGPT — Training Language Models to Follow Instructions with Human Feedback (2022) 语言模型 进阶 SFT、奖励模型、RLHF 怎样使模型更符合人类指令? 精读视频

    阶段验收:解释模型规模、数据、计算预算与 Loss 的关系;区分 Pre-training、In-context Learning、SFT 与 RLHF。

    第三段:现代系统、多模态与推理

    连接 Chinchilla、训练数据、Agent 方法、开放模型、万卡训练、后训练和推理模型。

    Day 论文 · 原文 方向 难度 当天要回答的问题 李沐视频
    21 Chinchilla — Training Compute-Optimal Large Language Models (2022) Infra 与数据 进阶 固定计算预算下,应怎样平衡模型大小与训练数据量? —
    22 LAION-5B (2022) Infra 与数据 入门 大规模图文对如何获得、过滤,并支撑开放多模态训练? —
    23 ReAct (2022) 模型范式 入门 模型怎样交替生成推理、行动与观察,调用外部环境? —
    24 DiT — Scalable Diffusion Models with Transformers (2022) 多模态 进阶 为什么可以用 Transformer 替换扩散模型的 U-Net 骨干? —
    25 LLaMA — Open and Efficient Foundation Language Models (2023) 语言模型 进阶 为什么充分训练的中等规模模型也可能非常有竞争力? —
    26 LLaVA — Visual Instruction Tuning (2023) 多模态 进阶 如何连接视觉编码器与语言模型,并进行视觉指令微调? —
    27 The RefinedWeb Dataset (2023) Infra 与数据 进阶 网络数据经过过滤、去重后,为何能成为高质量预训练语料? —
    28 MegaScale (2024) Infra 与数据 挑战 万卡训练中的计算、通信、存储与故障怎样协调? —
    29 Tülu 3 (2024) 语言模型 挑战 完整的开放后训练如何衔接 SFT、DPO 与可验证奖励 RL? —
    30 DeepSeek-R1 (2025) 语言模型 挑战 R1-Zero、R1 与蒸馏分别怎样形成和传播推理能力? —

    阶段验收:面对一份新 LLM Technical Report,定位架构、数据、训练、后训练、评测、Infra 的内容并提出有根据的问题。

    每日阅读卡片(复制 30 份)

    Day XX · Paper · 日期:
    一句话:这篇论文试图解决 ______。
    旧方法的瓶颈:
    核心思路(附自己画的简图):
    关键证据:最能支持结论的图、表或实验:
    局限 / 不确定之处:
    它继承了什么、影响了什么:
    今天我能脱稿解释的一件事:
    

    完成标准和复盘

    每日完成标准:能用三分钟、自己的话讲明白动机、方法、证据和影响;不把“读懂所有公式”当成每日强制任务。每 10 天画一次四条主线的关系图。

    注意:30 篇按学习路径而非完全按论文发表先后编排;部分文章是技术报告或预印本,年份按原始公开时间标注。四条主线是为了方便理解,不是彼此独立的研究分类。

    30 天之外的下一轮候选:Sequence to Sequence Learning with Neural Networks、Knowledge Distillation、AlphaGo Zero、FlashAttention、DPO、HELM、AlphaFold 2、DeepSeek-V3。它们都值得单独深入,但不要求加入本轮每日任务。

    → 9:32 PM, Oct 21
    Also on Bluesky
  • 如果一個肌群【只挑一個動作練】

    三健客首選 CP值最高動作│健人訓練│ 2020ep27

    一个肌群只练一个动作(含备选动作版)

    肌群 主推荐动作 备选动作 核心原因
    胸 上斜哑铃卧推 杠铃卧推 上胸难练、轨迹自由、刺激完整
    二头 上斜哑铃弯举 坐姿哑铃弯举、W 杠弯举 同时刺激二头+肱桡肌
    小腿 跳绳 不练 小腿+协调+心肺+足踝稳定
    大腿 高杠深蹲 深蹲、后脚抬高蹲 全面、功能性强
    臀 臀推 硬举、Cable 后踢腿 臀大肌刺激直接
    肩 坐姿哑铃肩推 杠铃肩推、侧平举 前束中束都能练到
    三头 绳索下压 W 杠下压、直杠下压 简单稳定、刺激强
    背 引体向上 无(全员一致) 几乎无法替代
    腹 悬吊举腿 腹肌轮、下腹抬腿 上下腹一起练

    这期视频真正想表达的核心,其实不是:“哪个动作最强”

    而是:当时间有限时,优先练:

    • 复合动作
    • 功能性高动作
    • 覆盖范围广动作
    • 机械张力高动作
    • 最适合自己身体条件的动作

    他们最后也特别强调:没有绝对标准答案。

    One exercise per muscle group guide-en&10;A fitness chart outlines various exercises for different muscle groups, with illustrations, target muscles, and benefits, accompanied by Chinese text.
    → 8:47 AM, May 23
    Also on Bluesky
  • The Most Trivial Prompt in the World

    用「GPT Image 2」畫廢圖

    「請用笨拙、最潦草、最徹底可憐的方式重畫附圖。用白色背景讓它看起來像是有人用滑鼠在小畫家裡畫出來的。它應該跟原圖有點像但又不太像,大致對得上但又用某種令人困惑、尷尬的方式偏掉,帶著那種低品質、一格一格畫素的感覺,真正凸顯出這張圖糟糕到多荒謬。算了,隨便你怎麼畫吧。」

    原文:「Redraw the attached image in the most clumsy, scribbly, and utterly pathetic way possible. Use same color, and make it look like it was drawn in MS Paint with a mouse. It should be vaguely similar but also not really, kind of matching but also off in a confusing, awkward way, with that low-quality pixel-by-pixel feel that really emphasizes how ridiculously bad it is. Actually, you know what, whatever, just draw it however you want.」

    A group of children wearing school uniforms walk along a tree-lined sidewalk, accompanied by two adults carrying bags.
    → 11:31 PM, May 9
    Also on Bluesky
  • AI Future 大会参会感想

    整体氛围热闹,但我作为旁观者,更多是从中退后一步,思考"人与AI"这个核心命题,反而让原有的技术焦虑淡化了一些。

    印象最深的两个演讲:

    罗振宇:人是AI时代的产品 AI让实现门槛极低,“你会什么、你能做什么"的价值正在被替代。真正稀缺的,反而是"你自己是什么”——一个人的独特性、丰富性和魅力。给自己出题、持续行动,让自己变得不可替代,而不是活成一件被使用的工具(君子不器)。

    李继刚:人与AI的关系 他从历史脉络出发,指出文明与技术的发展,本质上是对人类能力的延伸,但同时也是一种截断。当下的变化在于:我们从世界的"经历者"退变成了"确认者"——AI压缩了我们与世界之间的摩擦,也顺带压缩了我们的判断力和思考过程。但有一样东西AI无法压缩:体验本身。站在世界之外能拿到好结果,却失去了那段经历。

    两个演讲其实指向同一个方向:在AI时代,真正值得守护的,是那个只属于自己的、无法被替代的内在。

    大会更详细的内容可以参考:

    • 罗振宇、张鹏、王力行等齐聚一堂,AIFUT大会Day1上午场的全面总结来了。
    • 从傅盛的龙虾到汗青的加速主义,AIFUT大会Day1下午场总结都在这了。
    • 卡兹克的 AIFUT:聊了一天「人还能干什么」
    • AIFUT day1:若AI代替了一切,我们还剩下什么
    → 8:22 PM, Apr 9
    Also on Bluesky
  • AI Startup Survival Rules: Melvin Chen's Strategic Blueprint and Lovart's Practice

    Introduction

    3 hours and 44 minutes of conversation, one core question: How can AI startups survive in a game dominated by tech giants?

    Lovart founder Melvin Chen’s answer is surprisingly clear—it’s not about capital, not about data, but about cognition, speed, and building your kingdom in places the giants “don’t care about.”

    In this deep conversation with Luo Yonghao, Chen systematically articulated survival rules for startups in the AI era. These insights come not just from his 10 years of practical experience across major internet companies, but from Lovart’s exploration in the AI design tools space.

    Why is this article worth reading?

    If you’re starting or planning to start a company in AI, or building AI products, this article will help you clarify:

    • The three strategic pillars of AI entrepreneurship
    • The true philosophy of “AI Native” products
    • The three internal drivers founders must have
    • Predictions about the future of the design industry

    Podcast Information:

    • Title: Lovart Founder Melvin Chen × Luo Yonghao! Let Me Shake the World, Then Walk Away | Melvin Chen: Let Me Shake the World, Then Walk Away
    • YouTube: www.youtube.com/watch
    • BiliBili: www.bilibili.com/video/BV1…

    Executive Summary

    💡 Core Insight: AI entrepreneurship isn’t about competing with giants on capital and data—it’s about building your kingdom with cognition, speed, and conviction in places they “overlook.”

    This brief deeply analyzes AI design tool Lovart founder Melvin Chen’s core strategic thinking on how early-stage AI startups can achieve long-term survival and development. This strategic framework aims to avoid direct capital and data consumption wars with tech giants, instead carving out unique survival space through precise positioning and capability building.

    Core strategic elements include:

    🎯 Three Strategic Pillars

    1. Identify “Real Needs”: Reject fleeting viral ideas, focus on solving persistent, high-value “professional needs.” Products should simulate high-value human-to-human communication patterns.

    2. Avoid Direct Giant Competition: Adopt two strategies—occupy the “upstream” of workflows (like Midjourney to Photoshop), avoid becoming easily replaceable downstream plugins; and serve “new audiences” or “new needs”, explore markets giants haven’t covered yet.

    3. Build Independent Moats: Transcend the mere “wrapper” model relying on base models, build defensive barriers through post-training, unique application logic, and creating high switching costs (like communities or unique workflows).

    🌱 “AI Native” Product Philosophy

    True AI Native products have core experiences that “simply cannot exist” without AI, not just incremental improvements to existing software (like going from 60 to 80 points). The design philosophy is to create brand-new, AI-driven workflows and interaction modes.

    💪 Founder’s Internal Drive

    Founders must possess three internal qualities:

    • Cognition: Insight into market opportunities earlier than giants
    • Speed: Fastest iteration in the AI era
    • Belief: 100% commitment to directions giants see as only 10% likely to succeed

    🔮 Industry Future Predictions

    Chen predicts AI will replace over 80% of designers who have skills but lack unique taste and creativity. Top designers’ value will rise, not fall. This judgment is based on the assumption that fully generalized artificial intelligence (Full AGI) won’t be achieved in the next 5-10 years.


    Chapter 1: Entrepreneurial Survival Architecture in the AI Era

    Chen outlined a blueprint for AI startups aimed at long-term development, with core principles of avoiding giant crushing and building sustainable business models. This blueprint contains three interconnected strategic points.

    1.1 Identify “Real Needs”: Solve Professional and Persistent Problems

    To build an enduring company, not a short-term project to be sold, products must solve a persistent “real need,” not chase viral gimmicks.

    What are real needs?

    • ❌ Fleeting trends: AI-generated childhood photo albums, AI love letters—fun but unsustainable
    • ✅ Persistent needs: Let clients communicate directly with “AI designers”—solves real business pain points

    Three Principles:

    1. Professional needs first: Strategic focus should be on “professional needs,” even if target users aren’t professionals in the traditional sense. This means your product solves a problem with professional standards and value.

    2. Reject fleeting trends: Must reject those “clever” ideas that only trend for a few months—they can’t provide long-term value or form a sustainable business foundation.

    3. Simulate human communication: A successful AI product should be able to replicate high-value human communication patterns. For example, Lovart’s design philosophy simulates the process of clients and designers collaborating and communicating in a shared visual space (like a whiteboard).

    1.2 Avoid Giants: Find New Territory Upstream

    Chen believes startups cannot survive in direct “vicious competition” with tech giants because the latter have absolute advantages in capital and data. Therefore, must adopt differentiation strategies.

    Strategy Description Case Analysis
    Occupy workflow “upstream” Position product at workflow’s starting stage, not downstream. Downstream tools (like specific feature plugins) easily get absorbed or replaced by platform owners. Midjourney’s success lies in being upstream of Photoshop. Users first generate core ideas in Midjourney, then enter Photoshop for refinement. This upstream positioning maintains independent value even when surrounded by giants.
    Serve “new audiences” & “new needs” Explore new user groups or unmet new needs that giants currently ignore. Rather than improving old experiences from “60 to 80 points,” create an AI-native experience “from 0 to 1.” Canva’s success didn’t come from stealing Adobe’s professional designer users, but serving “new audiences” without professional skills but with social media posting needs. Similarly, Lovart aims to serve “clients” (marketing managers), letting them communicate directly with “AI designers” to meet their own professional design needs.

    1.3 Build Moats: Independent Capabilities Beyond “Wrappers”

    To avoid “being destroyed by model evolution,” startups must transcend being merely base model “wrapper” applications and build unique, hard-to-replicate defensive barriers.

    • Transcend base models: While startups use base models like GPT or Midjourney, must perform post-training on top and build high-level application logic to provide unique user experiences.

    • Create high switching costs: Long-term value lies in building ecosystems users find hard to leave. Can be achieved through building communities or creating unique workflows (like Lovart’s infinite canvas). Even if giants later add similar AI features, high migration costs effectively retain users.

    • Tactical advantage of “nobody cares”: Startups should focus on businesses big companies “don’t care about” or “don’t quite believe in.” When an opportunity seems only 10% likely to succeed to big companies, startups can invest 100% belief and speed to execute. By the time the giant (Final Boss) realizes its feasibility, the startup has already completed upgrades and built solid defensive fortifications.


    Chapter 2: Defining “AI Native”: Product Philosophy of a New Species

    Chen gives a clear definition of “AI Native” products: their core experience simply cannot exist without AI technology, not just incremental improvements from adding AI features to existing tools.

    2.1 Fundamental Existence vs. Incremental Improvement

    Grafting AI features onto “old world” software (like adding AI text processing to Notion or Feishu) doesn’t constitute AI Native. The core experiences of these software already existed—AI just improves them from “60 to 80 points.” True AI Native products have existence premised on AI capabilities.

    2.2 Workflow Positioning: Upstream Strategic Advantage

    A key part of AI Native strategy is occupying the “upstream” of workflows, not “downstream.”

    • Upstream exemplars: Tools like Midjourney and Liblib succeed because they’re at the starting point of creative workflows.

    • Downstream risks: If your product is positioned as a plugin or downstream editor for giant platforms like Photoshop, you’re highly likely to get absorbed or crushed by platform owners.

    2.3 Serving New Audiences and New Needs

    AI Native products should focus on previously unmet needs due to technical limitations or entirely new user groups. Lovart’s goal is to serve “clients,” letting them communicate directly with “AI designers”—this is a typical new need catalyzed by AI.

    2.4 Interaction-Native: Restoring Human-to-Human Communication

    A true AI Native product should fully leverage its hardware device characteristics and simulate natural interaction modes, not dogmatically understanding “native.”

    • Infinite Canvas: Lovart uses infinite canvas because it simulates natural human behavior of brainstorming and visual alignment on whiteboards—this is considered AI Native interaction design.

    • Touch Edit Feature: This feature lets users point at an object on screen (like a cup) with their finger, then tell AI in natural language how to modify it. This perfectly replicates the scene of clients giving designers revision feedback—behind it is advanced AI image understanding capability.

    2.5 “Super Hybrid”: Recombinant Innovation

    Chen describes AI Native products as a “super hybrid” that combines:

    • Old world elements: Canvas, layers, editing tools
    • New world AI: Generative models, understanding capabilities, interaction modes
    • New species: Faster, better, lower learning cost

    Key is recombination: Not creating entirely new components, but combining existing elements in novel ways to create unprecedented experiences.


    Chapter 3: Founder’s Internal Drive: Cognition, Speed, and Belief

    Chen emphasizes that in the AI era, a startup’s core moat isn’t just technology—it’s the founder’s three internal qualities.

    3.1 Cognition: Insight Opportunities Early

    Founders must have the ability to insight into market changes and potential opportunities earlier than big companies. This forward-looking cognition is the prerequisite for seizing time windows.

    3.2 Speed: The Only Requirement in the AI Era

    As base models destroy past engineering barriers, value creation points shift to rapid iteration of user interaction and vertical needs. In the AI era, “speed is all you need.”

    3.3 Belief: Bet on Low-Probability Futures

    Founders must dare to invest 100% belief in directions that seem “low probability” (like 10% success rate). Big companies, due to rational decision-making, often choose higher success rate projects (like 80%), which precisely leaves disruptive innovation space for startups. Before a direction becomes consensus, the founder’s firm belief is the key force driving the team forward.


    Chapter 4: Outlook on Design Industry and Future

    Based on his understanding of AI development, Chen makes clear predictions about the design industry and even human-AI relationships.

    4.1 Design Industry Disruption: 80% of Practitioners Will Be Replaced

    He predicts AI will replace over 80% of designers, especially those “with only skills, no ideas, no taste.” These homogenized, execution-based design tasks will be efficiently completed by AI.

    At the same time, top designers who can provide “soul,” unique aesthetics, and creative direction to AI will become more valuable and more expensive.

    4.2 Judgment on AGI: Core Value of Human Taste

    Chen’s strategic judgment is based on a core assumption: Fully General Artificial Intelligence (Full AGI) will not be achieved in the next 5-10 years.

    He believes that as long as AI remains at the stage of “infinitely approaching humans” but not yet comprehensively surpassing humans in emotion and creativity, human taste and intervention will always be the final deciding factor distinguishing mediocre from excellent results—this is also the core of human value.


    Core Concept Analogies

    Analogy Description
    Planting a special fruit tree in a giant forest AI entrepreneurship is like surviving in a forest of giants. The fruit must be something people need daily (real need), the planting location can’t be under giant trees’ shadows (avoid giants), but find new soil (new audiences). Finally, must root deep, unique roots (independent moat) to withstand storms.
    Traditional car vs. Tesla Adding AI features to old software is like adding a small motor to a fuel car—it improves but essence unchanged. AI Native products are like Tesla—design revolves around batteries and software (AI core) from the start. Without this core, its unique architecture and features couldn’t exist.
    Grinding levels in a game AI entrepreneurship is like playing a high-risk game. Early must quickly “fight small monsters” (serve niche needs) to level up. If you attract “Final Boss” (tech giant) attention too early, you get insta-killed. Only by quickly leveling and building “solid fortresses” (community and unique workflow moats) can you win final victory.

    My Reflections

    After listening to this conversation, my biggest takeaway is: AI-era entrepreneurship isn’t about competing on technology—it’s about competing on cognition.

    Why This Conversation Matters

    In the current frenetic atmosphere of “AI entrepreneurship = wrapping GPT,” Chen’s thinking appears exceptionally clear. He didn’t talk about how to quickly raise funding or do viral marketing, but focused on a fundamental question: When you can’t compete with giants on resources, what gives you the right to exist?

    The answer to this question isn’t “more advanced algorithms” or “more flashy features,” but rather:

    • Have you solved real needs others don’t understand or overlook?
    • Have you occupied a workflow position that can’t be easily replaced?
    • Have you built stickiness that makes users hard to leave?

    Rethinking “Real Needs”

    Chen’s definition of “real needs” made me reflect on many product directions. Are we too easily attracted by surface heat, ignoring those seemingly unsexy but truly persistent needs?

    Lovart’s choice to serve “clients” rather than “designers” is very clever positioning. It’s not making a “better design tool,” but solving a completely different problem: how to let people who don’t understand design also obtain professional-level communication ability.

    This is truly AI Native—not because it uses AI models, but because AI makes a previously impossible scenario possible.

    About “80% of Designers Will Be Replaced”

    This judgment seems cruel, but think carefully—every technological revolution in history was like this. Photography replaced portrait painters, but photographers became a new profession. Computers replaced human calculators, but programmers became a new profession.

    Key isn’t “replacement,” but “evolution.” If you’re just an executor, you’ll indeed be replaced. But if you can provide unique aesthetics, creativity, and judgment, AI will become your most powerful amplifier.

    The Power of Belief

    The part about “belief” moved me most. Big companies rationally calculate probabilities, choosing 80% success rate safe directions; but what entrepreneurs must do is precisely those things with only 10% success rate but enormous value once successful.

    This asymmetry is exactly where entrepreneurial opportunities lie. When no one believes, you execute with 100% belief. By the time it becomes consensus, you’ve already built insurmountable advantages.


    Final Advice:

    Don’t fear giants. As Chen said, in those places with “only 10% success rate,” lies your greatest opportunity. While big companies are still watching from the sidelines, you’ve already built your kingdom with speed and belief.

    This is the entrepreneurial rule of the AI era: in places others don’t see, with speed others can’t match, do things others dare not believe.

    → 10:14 PM, Jan 13
    Also on Bluesky
  • TIL: Customizing Claude Code Models

    There are two ways to customise the models used by Claude Code.

    1. Simple alias

    This is a quick setup using environment variables for the API token and base URL.

    On macOS, edit your shell configuration file: vim ~/.zshrc.

    Add the following aliases:

    alias claude="$HOME/.claude/local/claude"
    
    export PATH="$HOME/.claude/local:$PATH"
    alias kimi="ANTHROPIC_AUTH_TOKEN=<api-key> ANTHROPIC_BASE_URL=https://api.moonshot.cn/anthropic claude"
    
    export PATH="$HOME/.claude/local:$PATH"
    alias bigmodel="ANTHROPIC_BASE_URL=https://open.bigmodel.cn/api/anthropic ANTHROPIC_AUTH_TOKEN=<api-key> claude"
    
    export PATH="$HOME/.claude/local:$PATH"
    alias minimax="ANTHROPIC_BASE_URL=https://api.minimaxi.com/anthropic ANTHROPIC_AUTH_TOKEN=<api-key> claude"
    

    This approach is lightweight and convenient when you only need to switch endpoints or tokens quickly.

    2. Full Configuration via Environment Settings

    This method allows you to configure Claude Code with complete, reusable environments.

    Steps:

    1. Create a settings JSON file for each model
    2. Define aliases to launch Claude Code with those settings

    Create Model Settings Files

    Under the ~/.claude directory, create a models folder to store configuration files for different models.

    bigmodel.json

    {
        "env": {
            "ANTHROPIC_AUTH_TOKEN": "<api-key>",
            "ANTHROPIC_BASE_URL": "https://open.bigmodel.cn/api/anthropic",
            "API_TIMEOUT_MS": "3000000",
            "CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC": 1
        }
    }
    

    kimi.json

    {
        "env": {
            "ANTHROPIC_BASE_URL": "https://api.moonshot.cn/anthropic",
            "ANTHROPIC_AUTH_TOKEN": "<api-key>",
            "ANTHROPIC_MODEL": "kimi-k2-thinking-turbo",
            "ANTHROPIC_DEFAULT_OPUS_MODEL": "kimi-k2-thinking-turbo",
            "ANTHROPIC_DEFAULT_SONNET_MODEL": "kimi-k2-thinking-turbo",
            "ANTHROPIC_DEFAULT_HAIKU_MODEL": "kimi-k2-thinking-turbo",
            "CLAUDE_CODE_SUBAGENT_MODEL": "kimi-k2-thinking-turbo"
        }
    }
    

    minimax.json

    {
        "env": {
            "ANTHROPIC_BASE_URL": "https://api.minimaxi.com/anthropic",
            "ANTHROPIC_AUTH_TOKEN": "<api-key>",
            "API_TIMEOUT_MS": "3000000",
            "CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC": 1,
            "ANTHROPIC_MODEL": "MiniMax-M2.1",
            "ANTHROPIC_SMALL_FAST_MODEL": "MiniMax-M2.1",
            "ANTHROPIC_DEFAULT_SONNET_MODEL": "MiniMax-M2.1",
            "ANTHROPIC_DEFAULT_OPUS_MODEL": "MiniMax-M2.1",
            "ANTHROPIC_DEFAULT_HAIKU_MODEL": "MiniMax-M2.1"
        }
    }
    

    Add Aliases to Use the Settings

    Edit ~/.zshrc again: vim ~/.zshrc.

    alias cc-kimi="claude --settings $HOME/.claude/models/kimi.json"
    
    alias cc-bigmodel="claude --settings $HOME/.claude/models/bigmodel.json"
    
    alias cc-minimax="claude --settings $HOME/.claude/models/minimax.json"
    

    This approach is ideal when you need fine-grained control, consistent defaults, or multiple model profiles.

    → 11:33 PM, Dec 23
    Also on Bluesky
  • 2025-09-22 TIL: Microsoft Copilot Studio and Process Framework for Microsoft Semantic Kernel

    2025-09-22 TIL: Microsoft Copilot Studio and Process Framework for Microsoft Semantic Kernel

    💻

    I heared Microsoft Copilot Studio before, but I didn’t realize it’s similar to the Agent Builder that we want to build and support. Woooo, how can i miss that? Copilot Studio is a grphical, low-code tool for building agents and agent flows.

    A collegue shared me the Process Framework for Microsoft Semantic Kernel, which provides a robust solution for automating complex workflows. Each step within the framework performs tasks by invoking user-defined Kernel Functions, utilizing an event-driven model to manage workflow execution.

    → 10:12 PM, Sep 22
    Also on Bluesky
  • TIL: Hanzi related

    Render Hanzi writer character data, stroke animations or stroke quizzes. Hanzi Writer

    • chanind/hanzi-writer: Chinese character stroke order animations and practice quizzes

    skishore/makemeahanzi: Free, open-source Chinese character data

    • Learn Chinese one stroke at a time

    HSK levels related

    • Word Lists - HSK东西
    → 11:25 PM, Jul 22
    Also on Bluesky
  • TIL: Claude Code's loading messages

    I was attracted to the word loading indicator when Claude Code is working on a response. For example, jiving, whirring, channelling, conjuring, pontificating, concocting, discombobulating…

    After searching from the web, I found this topic Claude Code’s loading messages which resolved my curiousity.

    …found out that Claude Code will actually call the API and ask Claude Haiku to generate this single word based on your input. It does this as you type so it’s ready to go when you submit (and it will make many calls for each prompt).

    For those interested, here’s the full system message for the request. It will send you input in a separate user message.

    Analyze this message and come up with a single positive, cheerful and delightful verb in gerund form that's related to the message. Only include the word with no other text or punctuation. The word should have the first letter capitalized. Add some whimsy and surprise to entertain the user. Ensure the word is highly relevant to the user's message. Synonyms are welcome, including obscure words. Be careful to avoid words that might look alarming or concerning to the software engineer seeing it as a status notification, such as Connecting, Disconnecting, Retrying, Lagging, Freezing, etc. NEVER use a destructive word, such as Terminating, Killing, Deleting, Destroying, Stopping, Exiting, or similar. NEVER use a word that may be derogatory, offensive, or inappropriate in a non-coding context, such as Penetrating.

    This is what the official docs have to say about it:

    Haiku generation: Small creative messages that appear while you type (approximately 1 cent per day).

    → 11:13 PM, Jul 22
    Also on Bluesky
  • TIL: iOS App not using full height of the screen

    TIL: iOS App not using full height of the screen

    Problem:
    iOS app is not taking the whole height of the screen.

    Reason:

    “where I removed … the launch screen”
    All iOS apps MUST have a launch screen storyboard, even if the rest of the app is done without storyboards.

    Solution:

    1. Go to the target’s build settings
    2. Search for Launch Screen (Generation)
    3. Turn the value to Yes
    → 10:59 PM, Jul 15
    Also on Bluesky
Page 1 of 6 Older Posts →
  • RSS
  • JSON Feed
  • Lucky
  • Archive
  • About