Naur经典论文重读：编程即理论构建
推荐指数 45.0 NO. 015 · 2026.05.10
发布2026/05/09Score68Comments13
为什么值得看
Peter Naur 1985年的经典论文《Programming as Theory Building》被重新推荐，核心论点是编程的本质是构建关于问题的理论而非仅写代码。对AI工程师有警示意义：LLM生成代码再快，若团队失去对问题域的深层理论理解，系统长期维护仍将崩塌。
媒体预览
编辑判断
这篇1985年的论文在LLM时代有了残酷的反讽意味。Naur当年批判的是"代码即文档"的幻觉——现在LLM让这种幻觉变本加厉：团队以为有了Copilot就拥有了知识，实际上只是加速了理论流失的速度。
真正该警惕的场景是：初创公司用AI快速堆出MVP，核心人员流失后，没人理解为什么某些边界条件要那样处理，系统变成不可触碰的黑箱。论文提出的"理论流失导致系统死亡"机制，正是当前AI辅助开发中被忽视的长期风险。
建议：用LLM写代码时，强制要求同步输出设计决策的"理论文档"——不是注释，而是关于问题域假设、约束权衡、反例场景的显性记录。
社区反馈
意见分歧 13 条评论
核心争论：LLM能否构建程序理论，还是仅生成无理解的代码？
The only reason I recommend this paper is because I encounter so many people that have a very myopic view of the software that they’re building. They are focused on individual features and how to quickly made them happen regardless of what happens to its cohesiveness. You start to talk about interfa
I wouldn't start to think of someone as a real developer unless they've at least designed & written something of at least 10K LOC or so of complexity from scratch a few times. At least, you're not going to be able to understand these lessons and characterizations of programming in the large unless y
I wrote a series of blog posts about this a few years ago: https://creating.software/essays/theory_of_a_program/, some of the few I ever actually finished, lol. Most of my posts have aged terribly in the age of AI (especially the ones I didn't finish...so long, extended disc