Notably, Claude flags some differences: apprenticeships, material scarcity, career progression, and guild certification. These differences might point to capabilities to put into agentic coding tools.
I call this mapping move “@metaphorize”; I’ve released it as part of my skill library, Future Tokens, which you can find on my Substack if you’re interested.
“@rhyme” is a metaphor-finding skill. Claude thinks film production, air traffic control, and a surgery team are slightly better metaphors for agentic coding than Rembrandt’s workshop is, while orchestra conductor is slightly worse.
That is ... kind of incredible. I feel like you've subjected my little blogpost to more analytic power than is used for some F500 product launches. I love it beyond words. I already had Future Tokens on my radar, but now I'm _definitely_ going to dive in.
I’m enjoying your blog!
Here’s a conversation with Claude, mapping all of the structure of “Rembrandt’s workshop” to the structure of “Agentic software development”: https://claude.ai/share/a6ed0b94-7e12-412e-a726-54ae3a56d3fb
Notably, Claude flags some differences: apprenticeships, material scarcity, career progression, and guild certification. These differences might point to capabilities to put into agentic coding tools.
I call this mapping move “@metaphorize”; I’ve released it as part of my skill library, Future Tokens, which you can find on my Substack if you’re interested.
“@rhyme” is a metaphor-finding skill. Claude thinks film production, air traffic control, and a surgery team are slightly better metaphors for agentic coding than Rembrandt’s workshop is, while orchestra conductor is slightly worse.
That is ... kind of incredible. I feel like you've subjected my little blogpost to more analytic power than is used for some F500 product launches. I love it beyond words. I already had Future Tokens on my radar, but now I'm _definitely_ going to dive in.