This piece really nails something important about the CLI being the most efficient interface for agents. The hidden insight here is that terminal fluency is actually becoming less about memorizing commands and more about understanding the architecture of what you're trying accomplish. I've noticed when prototyping with Claude Code that having even basic mental models of file systems and process management helps me catch potentila failures before they cascade. It's kinda like the difference between knowing driving rules and understanding traffic flow.
Interesting stuff. Between this and Ethan Mollick's post yesterday, I've chosen to set aside time each week to experiment with coding agents, which I hadn't explored previously. I think the implied technical barrier (even if low) turns a lot of folks off, even those working in the policy space. That's certainly a mistake.
I'm curious about this point:
"I would no longer be surprised if we saw AI in the macroeconomic statistics by the end of this year, both on the upside (growth, productivity) and downside (labor market dislocation)."
Is the implication here that you would have been surprised by this, or didn't expect it a year ago? Does this change your policy recommendations or thoughts about near term governmental action?
It doesn't change my policy recommendations especially; I always expected AI to effect macroeconomic statistics eventually, it just would have surprised me if e.g. o3 or Claude 3.5 were noticeable.
This piece really nails something important about the CLI being the most efficient interface for agents. The hidden insight here is that terminal fluency is actually becoming less about memorizing commands and more about understanding the architecture of what you're trying accomplish. I've noticed when prototyping with Claude Code that having even basic mental models of file systems and process management helps me catch potentila failures before they cascade. It's kinda like the difference between knowing driving rules and understanding traffic flow.
Love this, such a good piece! Gonna go have a play with Claude Code now
Interesting stuff. Between this and Ethan Mollick's post yesterday, I've chosen to set aside time each week to experiment with coding agents, which I hadn't explored previously. I think the implied technical barrier (even if low) turns a lot of folks off, even those working in the policy space. That's certainly a mistake.
I'm curious about this point:
"I would no longer be surprised if we saw AI in the macroeconomic statistics by the end of this year, both on the upside (growth, productivity) and downside (labor market dislocation)."
Is the implication here that you would have been surprised by this, or didn't expect it a year ago? Does this change your policy recommendations or thoughts about near term governmental action?
It doesn't change my policy recommendations especially; I always expected AI to effect macroeconomic statistics eventually, it just would have surprised me if e.g. o3 or Claude 3.5 were noticeable.
Dean, have you ever by chance read Greg Bear’s “Blood Music”? It’s what popped into my head when I read this post this morning.
I haven't! Will check it out.
I have no clue how to code but this is an interesting primer on these tools
Dean, are you able to share Github links to any of these projects that might contain prompt sources or the resulting artifacts?