Scala on My Space

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 代写工作总结和回怼邮件"。

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 中与你分享我的进化之路。