你不需要人工智能来生成代码
3 分•作者: Lozybug•大约 1 个月前
各位，我要说一句“异端”的观点。那就是：你不需要人工智能来生成代码，而且你不应该使用人工智能来生成代码。
相反，我认为人工智能应该被用来梳理用户需求，然后人工智能可以用来生成一个规范，从中可以确定性地映射代码来生成最终的程序。我们在 20 世纪 80 年代就已经以一种简化的形式在做这件事了。
如果你认为这对于“氛围编码”（vibe coding）和“代理工程”（agentic engineering）来说是一个相关的替代方案，请告诉我。我可以向你展示这一切是如何运作的，以及为什么它在 2026 年及以后至关重要。
是的，我确实有这么老了，但我对软件工程的基本原理有着深刻的见解。我感觉自己像是一个失落文明的幸存者，这个文明已经被冲刷殆尽，被人遗忘。我的方法将形式化方法和人工智能结合起来，这在过去是无法实现的。但是……现在我们有了计算能力和真正的人工智能，而不仅仅是“智能知识库系统”（IKBS），我们可以专注于生成规范，而不是代码。一个能够贯穿整个软件开发生命周期（SDLC）的规范。这有点像其他工程领域都有图纸、规范和电路图等。
祝好，
Loz
查看原文
Hi Guys, I'm going to make a heretical statement. It's this: you don't need AI to generate code and you shouldn't use AI to generate code.Instead I believe AI should be used to elicit the user requirements and the AI can then be used to generate a specification from which code can be mapped to produce code deterministically. We were doing this in a simplified form in the 1980s. If you think this is relevant as an alternative to vibe coding and agentic engineering. Let me know I can show you how all of this works and why it is important in 2026 and beyond. Yes, I am actually that old, but I have a view on the fundamental basics of software engineering. I feel like a survivor of a lost civilisation that has been washed away and forgotten. My approach brings together formal methods and AI in a way that was impossible back in the day. But... now that we have the compute and proper AI, not just IKBS, we can focus on generating a specification and not the code. A specification that can persist across the entire SDLC. All a bit like all the other branches of engineering that have drawings, specifications and circuit diagrams and things. Cheers me dears, Loz