多模态大模型：技术原理与实战在LLM时代，对软件研发的更多思考———

本文链接：https://blog.csdn.net/universsky2015/article/details/140055708

Software 1.0 vs Software 2.0 软件 1.0 与软件 2.0

在这里插入图片描述

In software 1.0, the application’s logic is captured in the code written by a software developer. When data comes in, and the logic/code is applied, we get the desired outcome. In software 2.0, the application’s logic is captured by the machine learning model trained by a data scientist on top of real data. The word “training” is important — it means we use statistical methods (whether it is a neural network or linear regression) to which we feed data, and the statistical methods output a “model” which encapsulates the logic we desire. Basically, the statistical method is writing the code for us 😃 Oh, we used the word “statistics” a lot, but let’s just say that “statistics = machine learning” — we admit that machine learning has a nicer ring to it.
在软件 1.0 中，应用程序的逻辑是在软件开发人员编写的代码中捕获的。当数据输入并应用逻辑/代码时，我们就得到了期望的结果。在软件 2.0 中，应用程序的逻辑由数据科学家根据真实数据训练的机器学习模型捕获。 “训练”这个词很重要——它意味着我们使用统计方法（无论是神经网络还是线性回归）来输入数据，统计方法输出一个“模型”，它封装了我们想要的逻辑。基本上，统计方法正在为我们编写代码:)哦，我们经常使用“统计”这个词，但我们只能说“统计=机器学习”——我们承认机器学习有一个更好听的名字。

Of course, as time goes by, the underlying data or behaviour desired from a system may change; therefore, the logic of the model trained some time ago won’t reflect the current world and will deprecate. Similarly to software 1.0, where the software developers have to rewrite the code to fix the logic, in software 2.0, we have to retrain the model on the latest data, which will (hopefully) get the logic back on track.
当然，随着时间的推移，系统所需的底层数据或行为可能会发生变化；因此，前一段时间训练的模型的逻辑不会反映当前的世界，并且会被弃用。与软件 1.0 类似，软件开发人员必须重写代码来修复逻辑，在软件 2.0 中，我们必须根据最新数据重新训练模型，这将（希望）让逻辑回到正轨。

Looking at it this way, MLOps can be seen as DevOps for Software 2.0.
从这个角度来看，MLOps 可以被视为软件 2.0 的 DevOps。