the share of sessions spent fixing broken code fell by nearly half, from 33% to 19%
这个数据点显示了编程工作模式的重要转变：修复代码的时间占比从33%下降到19%，减少了近一半。这表明随着AI代理能力的提升，用户可能减少了调试时间，转而专注于更高层次的任务。这一趋势与文章中提到的任务价值增长(平均27%)相呼应，暗示AI代理正在将用户从低价值维护工作转向高价值创新工作。然而，文章未解释这种转变的具体原因，可能是AI能力提升，也可能是用户技能提高。
A programming model is an execution model coupled to an API or a particular pattern of code.
Introduce behaviour that is likely to surprise users. Instead have due consideration for patterns adopted by other commonly-used languages.
provide interfaces so you don’t have to think about them
Question to myself: Is not having to think about it actually a good goal to have? Is it at odds with making intentional/well-considered decisions?  Obviously there are still many of interesting decisions to make even when using a framework that provides conventions and standardization and makes some decisions for you...
I think a better, more immediately understandable name for this concept would be command object, because it lets you pass around commands (or a list of commands) as objects.
That's the only thing you really need to know abut this pattern. The rest seems like boring implementation details that aren't that important, and that naturally follow from the primary definition above.
we need to step back and make a closer look at the DRY principle. As I mentioned earlier, it stands for "Don’t Repeat Yourself" and requires that any piece of domain knowledge has a single representation in your code base. The words domain knowledge are key here. DRY is not about duplicating code. It is specifically about duplicating domain knowledge
This is actually a good point – to have a single representation of specific piece of domain knowledge in the code.
DRY is not about duplicating code.