-
Self-Organization Doesn’t Just “Happen” ― How the Work of Managers and Engineers Is Changing
in ブログIn my last post, I introduced the “five role archetypes” that Boris Cherny presented. After finishing that piece, one thing kept nagging at me, so here’s the follow-up. How Claude Code Is Reshaping “Job Roles”――Anthropic’s Five Role Archetypes The Thing That Nagged Me: One Line in the Replies As I mentioned last time, in the…
-
How Claude Code Is Reshaping “Job Roles”: Anthropic’s Five Role Archetypes
in ブログHow It Started: A Translated Post on X A post I came across on X caught my eye recently: a user named Xiaohu had translated a Chinese post into Japanese (posted August 3, 2026, https://x.com/xiaohu/status/2084089717814129048). In short, it claimed that on average 90% of the code inside Anthropic is now written by Claude Code, and…
-
An English Concise Overview of Spec-Driven Development ― Released on Zenodo
in エルブズIntroduction A few weeks ago, I wrote two posts on this blog: “What is Spec-Driven Development — its three technical elements, four principles, and seven processes,” and “Spec-Driven Architecture: extending Spec-Driven Development into management.” Following that thread, I’ve now published an English-language concise overview of the methodology on Zenodo. This post is a short report on that. The…
-
What Is Spec-Driven Development? — Three Technical Elements, Four Principles, and Seven Processes
Introduction A while ago I wrote a piece called “Management-as-Code: A Spec-Driven Architecture for the Organization.” It was an attempt to extend spec-driven development to how a company is run. But in writing it, I realized something. I had never properly written a single article about spec-driven development itself — the foundation. In English, “Spec-Driven…
-
Management-as-Code: A Spec-Driven Architecture for the Organization
Introduction Two months have passed since I published Spec-Driven Development: A Practical Introduction (『仕様駆動開発 実践入門』, Nikkei BP). Many people have picked it up, and now and then I hear pointed criticism. The criticism that stings most is this: “Aren’t you actually not doing spec-driven development?” Whether one “is doing” spec-driven development is a hard thing…
