My Space

明系魔法吟唱之6 -- 民(科)用广义 Curry-Howard 证明搜索与程序合成器

Thu, 20 Aug 2026 16:18:37 +0800

书接上回： 明系魔法吟唱之5 – 我要说的事，你们千万别害怕

距离上一篇文章已经过去五个多月，这段时间里 AI 的玩法也发生了翻天覆地的变化。回想上半年，多少神棍（AI 导师）扬言软件开发已经被 ai 彻底解决， 99% 程序员都可以裁掉，甚至扬言软件开发已经进入黑灯工厂时代。各大技术分享会议的议题也只剩下了 AI 一个主题，大厂高 P 架构师们满世界宣传 AI 是如何给自己研发部门提效的，交付量增加了多少，工期一再缩短。甚至不乏有水货架构师自信地将提交次数和代码行数的巨幅增长当作提效的证据，在演讲中展示，似乎觉得代码行越多越好。但进入到下半年后，却又有冷却的迹象，甚至我在的最神棍的群也少有人讲这些神话了。昂贵的 token 烧了，代码量膨胀了数倍，开发每人每天都有几十次提交，最终交付的功能却没有变多，甚至质量愈有持续加速下滑的趋势。裁掉的开发，解散的团队节省下来的开支甚至远超 API token 账单（coding plan 不用看这句，plan 订阅开发企业商用项目属于违反协议的滥用行为）

明系魔法吟唱之5 -- 我要说的事，你们千万别害怕

Mon, 23 Mar 2026 20:00:00 +0800

书接上回： 明系魔法吟唱之4 – 精细化AI鞭策术：FP 的伟大复兴？

本文要推翻以人为本的软件工程方法

软件工程的核心原则：关注点分离、模块化、可验证性等理论依然是成立的。我要推翻的是围绕这些原则建立的大部分规则、工具和度量指标：它们以人类为模型设计，且只以人类为模型设计。——已经不适合这个版本了.jpg

AI编码代理规则文件全维度横向对比评测报告

Fri, 13 Mar 2026 12:00:00 +0800

AI编码代理规则文件全维度横向对比评测报告

核心前提

两个项目都是 AI-native 项目——代码由AI编码代理编写、修改、阅读和调试，但 AI-native 成熟度路径不同：

渐进式（Linewise）：多租户后端API服务（Scala 3 / http4s），历经多代模型演进（Claude 3.7→4.6），早期人类参与度约50%，随模型能力提升逐步降低人类介入，规则文件随项目一起演化积累。主要服务作者自己的agent。
原生式（OpenClaw）：开源自主AI代理平台（TypeScript / Node.js），从第一行代码起即由agent编写，创建者使用多agent并行工作流（5-10个agent并发），规则文件从项目诞生之初即作为agent的执行规范存在。250K+ stars、1000+贡献者，规则需同时服务创建者和大量外部贡献者的agent。

评测对象：

OpenClaw AGENTS.md 与 My Claude.md 规则横评

Thu, 12 Mar 2026 20:30:00 +0800

评测对象

OpenClaw：https://raw.githubusercontent.com/openclaw/openclaw/refs/heads/main/AGENTS.md
My（下文即 Linewise）：https://gist.githubusercontent.com/mingyang91/475a9750c5609ff5dfe59a5de1a09b6e/raw/51116ffd45c1f711039699c24cb0a7528b7febdf/Claude.md
项目定位补充依据：OpenClaw README.md；Linewise 的项目定位以规则文件自身及仓库结构说明为准

评测方法与判定图例

本文默认两个项目都是 AI-native 项目：代码的编写、修改、阅读、调试主要由 AI 编码代理完成，人类负责需求、反馈注入、最终审查与高风险动作确认。
本文不预设“渐进式 AI-native”或“原生式 AI-native”哪条路径更优，只评估：规则文件是否能支撑 agent 长期、高质量、一致地自主执行。
评测时先做两层前置判定：
- ✗ 不适用：该子项不属于项目合理需求范围，不计入分母。
- ✗ 未委托：该子项对项目可能有意义，但规则文件没有把该职责委托给 agent，不计入分母。
- ✓ 已委托：该子项既适用又已交给 agent，才进入 1-10 分打分。
图例：✓ 已委托｜8/10 表示“该项适用且已委托给 agent，评分 8 分”；✗ 不适用 与 ✗ 未委托 后均附一句理由。
对目标架构的尊重：
- OpenClaw 按 多 agent 并行 / 大量外部贡献者 agent 的目标架构评估。
- My 按 高能力主 agent 深入单仓库长期演进 的目标架构评估。

Part 1 — 基础画像

OpenClaw

项目定位：开源自主 AI 代理平台，覆盖 CLI、桌面端、移动端、插件、消息通道、GH 维护与发布链路。
规则文件角色：面向 maintainer 与外部贡献者 agent 的仓库级执行手册。
核心设计理念：优先防止 agent 在真实 GitHub、真实 Git、真实发布链路中“高置信度做错事”。
结构特征：覆盖 triage、PR truthfulness、build/test、coding style、release channel、GHSA、安全提示、1Password 发布、插件发布 fast path、多 agent Git 安全等。
一句话总结：它更像一套面向复杂开源仓库的 AI 维护操作系统。

My

项目定位：多租户 Scala 3 / http4s 后端 API，强调 tagless-final、cats-effect、Doobie、PostgreSQL schema isolation、Vertex AI、Quartz 与多租户安全边界。
规则文件角色：面向高能力主 agent 的强类型后端开发与演进规范。
核心设计理念：通过类型系统、分层边界、typed error、编译器与工具链，把 agent 的错误从运行时前移到编译期与签名层。
结构特征：围绕 refactoring philosophy、tagless final、flat for、typed error、schema isolation、RAC、OpenAPI、Metals、deploy impact reporting 展开。
一句话总结：它更像一套面向成熟后端存量代码的 AI 结构化演进宪法。

基础对比结论

OpenClaw 的强项是 广覆盖、强 runbook、强并发协作安全、强外部流程防错。
My 的强项是 深架构约束、强类型驱动、强渐进式重构、强后端正确性约束。
如果把两者硬放在同一赛道比“谁更全”，结论会失真；更准确的说法是：两者分别在不同 AI-native 工程阶段和执行架构上做到非常成熟。

Part 2 — 量化评测表

维度总览

注：下表分数仅基于“适用且已委托”的子项平均；参考均分仅用于帮助阅读，不代表脱离场景的绝对胜负。

明系魔法吟唱之3.14 -- Agent 规则文件评测：我的 vs OpenClaw

Thu, 12 Mar 2026 20:00:00 +0800

Claude 的完整评测报告见：AI编码代理规则文件全维度横向对比评测报告
Codex 的完整评测报告见：OpenClaw AGENTS.md 与 My Claude.md 规则横评

使用提示词

你是AI编码代理能力评测与软件工程研究专家。请对以下两份AI编码代理规则文件进行全维度横向对比，输出量化评测报告与规则制定者能力画像。

Ming's Spell Compendium #4 -- The Art of Whipping AI Grunts: FP's Great Comeback?

Wed, 11 Mar 2026 20:00:00 +0800

This is a cultural adaptation — not a literal translation — of the original Chinese article. Recurring coined terms: grunts = AI agents doing the coding labor; boss = the human; whip-iler = a portmanteau of “whip” + “compiler” (the compiler that whips misbehaving grunts back in line).

Previously on… Ming’s Spell Compendium #3 – AI Programming: The Next Chapter

Times Have Changed

Let’s be honest: in more and more projects, the primary author of the code is already AI. Your coworkers have quietly subscribed to Cursor pro plans or OpenAI’s Codex. They toss requirements at the AI every morning, then spend their valuable working hours scrolling Reddit, day-trading meme stocks, nursing their phones back to full charge, ~~and quietly tanking their own projects~~. The human role is shifting from “writing code” to “feeding PRDs to the AI, pretending to review AI code, occasionally deploying some good old workplace gaslighting (‘You don’t want the job? There’s plenty of AI that do.’), and having the AI ghost-write your performance reviews and passive-aggressive emails.”

明系魔法吟唱之4 -- 精细化AI鞭策术：FP 的伟大复兴？

Wed, 11 Mar 2026 20:00:00 +0800

英文文化适配版： AI-Native Coding Style (English cultural adaptation)

书接上回： 明系魔法吟唱之3 – AI 编程的下一章

时代变了，大人

事实上越来越多的项目中，代码的主要作者已经是 AI 了，你身边的同事已经悄悄买了 glm coding plan 甚至中转站的 Codex 套餐，每天上班需求扔给 AI 后，自己则聚焦于：把尿喝白，把股炒红，把电充绿，~~把事办黄~~。人类的角色正在从"写代码"转向"把产品经理的 PRD 扔给 AI，装模作样 Review AI 代码，适当的调用一下 pua skills（你不干有的是 AI 干。），以及让 AI 代写工作总结和回怼邮件"。

明系魔法吟唱之3.1 -- 我的Claude规则文件分享

Tue, 10 Mar 2026 23:37:43 +0800

观前提醒

该文件为我个人自用的CLAUDE.md规则文件，维护生产项目已有一年时间，从 Cursor + opus 3.7 时代至现在Claude-Code + opus 4.6时代。

请注意：该文件也仅可用于 Claude code opus 4.6，我不是对 codex 和 gemini 有偏见，OpenAI 的 25k USD credits 今年6月份就要过期了，它（gpt-5.4-xhigh/codex-5.3-xhigh）要是真有自媒体和AI教父们宣传的那么牛逼plus，我能把这些credits放过保质期？

Ming's Spell Compendium #3 -- AI Programming: The Next Chapter

Mon, 09 Mar 2026 20:00:00 +0800

This is a cultural adaptation — not a literal translation — of the original Chinese article.

Conflict of interest disclosure: This is not investment advice. I’m not shilling any AI tool or API reseller. Everything here comes from ~$20K worth of token-burning personal experience. Different project types and different coding tastes may lead to different conclusions.

Previously On…

Ming’s Spell Compendium #2 – You Terrifying Upright Apes Are Underestimating Yourselves

In the last installment, we established: AI’s knowledge reserves dwarf any individual’s, but that knowledge is hard to awaken; your ability to discern quality sets the ceiling on output quality; the trigger for better results is always your own growth, not AI’s spontaneous breakthrough.

明系魔法吟唱之3 -- AI 编程的下一章

Mon, 09 Mar 2026 14:00:00 +0800

英文文化适配版： AI Programming: The Next Chapter (English cultural adaptation)

利益声明：本文不构成投资建议，不推荐任何 AI 工具购买或中转平台推广。所有内容均来自本人约 2 万美金 token 的实践经验。不同项目类别、不同编码品味可能会得出不一样的结论。

Ming's Spell Compendium #2 -- You Terrifying Upright Apes Are Underestimating Yourselves

Tue, 24 Feb 2026 08:37:43 +0800

This is a cultural adaptation — not a literal translation — of the original Chinese article. Some Chinese cultural references have been swapped for Western equivalents that hit the same emotional note.

Previously on… Ming’s Spell Compendium #1 – One Year of Vibe Coding: A Cold Hard Look

Foreword

Humans, you’re selling yourselves short.

How Much Can AI Amplify You?

Last year (2024), my working hypothesis was: even with AI, you can’t dramatically exceed the user’s own ability. If AI’s training data represents the sum total of human knowledge, then the current crop of agentic evangelists would have you believe that professional expertise has become a worthless commodity in this era — because AI can write code like Linus, write novels like Hemingway, etc.

明系魔法吟唱之2 -- 恐怖直立猿们，你们低估了自己的智慧

Tue, 24 Feb 2026 08:37:43 +0800

英文文化适配版： You Terrifying Upright Apes Are Underestimating Yourselves (English cultural adaptation)

书接上回： 明系魔法吟唱之1 – Vibe Coding 一年实践后的冷思考

前言

人类，你们过于低估自己了。

AI 能放大你多少？

去年（2024）我有个判断是，即便有 AI，也不能大幅超越使用者的能力。如果 AI 的训练知识是全人类知识的总集，现在 agentic 导师们宣传的是在这个时代专业技能变成了唾手可得的不值钱的东西，理由是 AI 可以模仿 Linus 来写代码，也可以模仿大文豪作家写小说，等等。

Ming's Spell Compendium #1 -- One Year of Vibe Coding: A Cold Hard Look

Fri, 06 Feb 2026 13:44:21 +0800

This is a cultural adaptation — not a literal translation — of the original Chinese article. Some Chinese cultural references have been swapped for Western equivalents that hit the same emotional note.

Foreword

Over the past year I’ve burned through more than $10,000 in API tokens across Google, Anthropic, and OpenAI. So everything in this article is based on hands-on experience with the strongest models available — Opus 4.6, Codex-5.3-xhigh, Gemini 3 Pro — used without budget constraints.

明系魔法吟唱之1 -- Vibe Coding 一年实践后的冷思考

Fri, 06 Feb 2026 13:44:21 +0800

英文文化适配版： One Year of Vibe Coding: A Cold Hard Look (English cultural adaptation)

前言

最近一年我在 Google/Anthropic/OpenAI 三家烧了超过 1 万美金的 token 账单。所以本文内容基于 opus4.6、codex-5.3-xhigh、gemini3-pro 等最强模型不限量使用所表现出来的编码能力进行评价。

Improving the Display of Data Lists: Designing a Real-Time Event Subscription Architecture

Sat, 15 Apr 2023 00:31:35 +0800

Many data systems use polling refresh to display lists, which can cause a delay in updating content status and cannot immediately provide feedback to users on the page. Shortening the refresh time interval on the client side can lead to an excessive load on the server, which should be avoided.

To solve this problem, this article proposes an event subscription mechanism. This mechanism provides real-time updates to the client, eliminating the need for polling refresh and improving the user experience.

Implementing Version Management of File Trees in PostgreSQL

Sun, 19 Mar 2023 20:37:00 +0800

Overview

In the previous post, we discussed how to implement a file tree in PostgreSQL using ltree. Now, let’s talk about how to integrate version control management for the file tree.

Version control is a process for managing changes made to a file tree over time. This allows for the tracking of its history and the ability to revert to previous versions, making it an essential tool for file management.

With version control, users have access to the most up-to-date version of a file, and changes are tracked and documented in a systematic manner. This ensures that there is a clear record of what has been done, making it much easier to manage files and their versions.

Implement the file tree in PostgreSQL using ltree

Sun, 19 Mar 2023 18:18:18 +0800

Background

A file tree is a hierarchical structure used to organize files and directories on a computer. It allows users to easily navigate and access their files and folders, and is commonly used in operating systems and file management software.

But implementing file trees in traditional RDBMS like MySQL can be a challenge due to the lack of support for hierarchical data structures. However, there are workarounds such as using nested sets or materialized path approaches. Alternatively, you could consider using NoSQL databases like MongoDB or document-oriented databases like Couchbase, which have built-in support for hierarchical data structures.

浅谈资源安全

Sun, 21 Aug 2022 12:12:43 +0800

起因

这个月（2022年8月）于Rust二群与某人辩论，因为某人坚持认为 Rust 的所有权 Ownership 机制仅仅是等同于垃圾回收 Garbage Collection ，而我认为 Ownership 还解决了另一个困扰无数码农的问题：资源安全

Hello World

Mon, 17 May 2021 00:00:00 +0800

Welcome to Hexo! This is your very first post. Check documentation for more info. If you get any problems when using Hexo, you can find the answer in troubleshooting or you can ask me on GitHub.

Quick Start

Create a new post

1

$ hexo new "My New Post"

More info: Writing

Run server

1

$ hexo server

More info: Server

Generate static files

1

$ hexo generate

More info: Generating

Deploy to remote sites

1

$ hexo deploy

More info: Deployment

AC + AP Enterprise WiFi6 practice

Fri, 14 May 2021 12:09:40 +0800

Rethink CDC system design

Fri, 14 May 2021 12:07:42 +0800

Webhook system design - base ZIO

Fri, 14 May 2021 09:42:33 +0800

Goals

Sending event message by http post
Recording success/error response from third-party reply.
It should re-send message after third-party reply error or down.

Features

Delivery (HTTP POST)
Success / Error Record
Re-send in the case of third-party failure.
Run in multi-process environment (e.g. Kubernetes)
Metrics of backlog message
Policy of record automatic archive
Prevent sent too fequencly after massive event generated.(throttle)

Results

After I migrated my legacy playframework project to zio, what I learned from it.

Thu, 13 May 2021 18:37:55 +0800

Foreword
What is R
What are the problems caused by DI tools?
Current Situation
Evolution Stage 1
Evolution Stage 2
Evolution Stage 3
Conclusion
References

Foreword

On April 17, 2020, I start a huge project to migrate the Future[T] from legacy playframework project to ZIO. Three months later, after tens of thousands of lines of code modification, the migration was a complete success. In September, I used this experience as the background to share in the Chinese Scala Meetup community with the title “Introduction to ZIO”. In this share, I explained a fanatic imageation, 在这次分享中，我展望了一个美好的愿景，借由 ZIO 的类型参数 R 提供的抽象能力来实现代码的可移植性，和提高可测试性。但想在遗留项目中实现这个愿景并不容易，主要挑战来自遗留项目的代码耦合，和开发者的思维惯性。如今，这个愿景已经达成。我会在这篇 Post 中与你分享我的进化之路。