Structured Programming, Object Oriented Design, Functional programming - all of these are the way code can be written.
WaterFall, Agile - is the process by which development can be done. Development is not the only thing when it comes to software development. Programming is one of the mandatory component of the process. The process can have design/testing/refactoring/maintenance.
And both of the above are complementary to each other (i.e. one can do structured programming and be modular and use some of the agile principles).
I don't know as to when it started (and I guess it should not matter). You might come up with your own style of process, which can work better in your own scenario.
EDIT: In summary, people started with structured programming, used it very well. It had its own limitations & things became object oriented. OO has its own limitations, as some gurus say and they see functional programming as the way to fix it.
It all depends on what suits your scenario & what serves you better. There is no silver bullet, as experts say.
发布评论
评论（2）
您可以在此处找到一种编程语言。 此着眼于范式
，这是发展时间表方法论：
you can find one here for programming languages. this one looks at paradigms
and here is a timeline of developement methodologies:
结构化编程、面向对象设计、函数式编程——所有这些都是编写代码的方式。
瀑布、敏捷——是可以完成开发的过程。 对于软件开发来说，开发并不是唯一的事情。 编程是该过程的强制性组成部分之一。 该过程可以有设计/测试/重构/维护。
以上两者是相辅相成的（即可以进行结构化编程、模块化并使用一些敏捷原则）。
我不知道它是什么时候开始的（我想这应该不重要）。
您可能会想出自己的流程风格，这在您自己的场景中可以更好地发挥作用。
编辑：总之，人们从结构化编程开始，并且使用得很好。 它有其自身的局限性和局限性。 事情变得面向对象。 正如一些专家所说，面向对象有其自身的局限性，他们将函数式编程视为解决它的方法。
这完全取决于什么适合您的场景和需求。 什么对你更有利。
正如专家所说，没有灵丹妙药。
Structured Programming, Object Oriented Design, Functional programming - all of these are the way code can be written.
WaterFall, Agile - is the process by which development can be done. Development is not the only thing when it comes to software development. Programming is one of the mandatory component of the process. The process can have design/testing/refactoring/maintenance.
And both of the above are complementary to each other (i.e. one can do structured programming and be modular and use some of the agile principles).
I don't know as to when it started (and I guess it should not matter).
You might come up with your own style of process, which can work better in your own scenario.
EDIT: In summary, people started with structured programming, used it very well. It had its own limitations & things became object oriented. OO has its own limitations, as some gurus say and they see functional programming as the way to fix it.
It all depends on what suits your scenario & what serves you better.
There is no silver bullet, as experts say.