收益率回测python代码_低代码收益或陷阱-CSDN博客

收益率回测python代码

Low-Code is promising to radically change the way organizations develop and manage their IT landscape. So far, there are many signs that this app development approach is delivering on this promise. Companies of all sizes are rapidly developing new applications and setting up their own Low-Code ‘Centers of Excellence’. The development platform market is projected to grow from USD 13.2 billion in 2020 to USD 45.5 billion by 2025 [1].

Low-Code有望从根本上改变组织开发和管理IT环境的方式。到目前为止，有许多迹象表明这种应用程序开发方法正在兑现这一承诺。各种规模的公司都在Swift开发新的应用程序，并建立自己的低代码“卓越中心”。开发平台市场预计将从2020年的132亿美元增长到2025年的455亿美元[1]。

While we’ve seen many organizations implement Low-Code successfully, we’ve also seen some organizations struggle. It is definitely possible to have your internal employees develop innovative applications in a matter of weeks and solve issues in a matter of hours. However, to realize this ambition, you must manage your delivery carefully. If you rush into it, the most communicated benefits of Low-Code platforms can quickly turn into the most common pitfalls. Here’s a few we would like to call out:

虽然我们看到许多组织成功地实施了低代码，但也看到一些组织在努力。绝对可以让您的内部员工在几周内开发出创新的应用程序，并在几小时内解决问题。但是，要实现这一雄心壮志，您必须仔细管理交货。如果您急于使用它，则低代码平台上传达最多的好处可能会Swift变成最常见的陷阱。以下是我们要介绍的一些内容：

即插即用 (Plug-and-play)

Sliders, data tables, tab containers; Low-Code platforms typically come with a library of UI components that are common in most well-known applications. It’s a matter of dragging and dropping them onto your What You See Is What You Get interface and your screen is ready.

滑块，数据表，标签容器；低代码平台通常带有大多数知名应用程序中常见的UI组件库。只需将它们拖放到“所见即所得”界面上，屏幕就可以准备就绪了。

The components are based on best practices and updated when new trends emerge. However, the combination or limitations of elements might not deliver the user experience that your users need in their context.

这些组件基于最佳实践，并在出现新趋势时进行更新。但是，元素的组合或局限性可能无法提供用户在其上下文中所需的用户体验。

As a concrete example, some platforms come with data tables that don’t allow in-line buttons. You are implicitly encouraged to present your Product Owner a table in which they have to select a row and subsequently scroll to the top to execute an action. In many cases, it’s possible to customize such an experience. In practice, it’s tempting to go for the plug-and-play option as ‘you don’t know what you don’t know’.

举一个具体的例子，某些平台附带不允许插入按钮的数据表。隐式地鼓励您为产品负责人提供一个表，在该表中他们必须选择一行，然后滚动到顶部以执行操作。在许多情况下，可以自定义这种体验。在实践中，很容易选择即插即用选项，因为“您不知道自己不知道的东西”。

轻松开发 (Easy development)

Low-Code is relatively easy. There’s no need to learn a new coding language, understand your IT infrastructure or even know what compilation means. This makes the approach very accessible to people without an IT background and no experience in developing software applications.

低代码相对容易。无需学习新的编码语言，了解您的IT基础架构，甚至不需要了解编译的含义。这使得没有IT背景且没有开发软件应用程序经验的人们都可以轻松地使用该方法。

Automatically and in the background, all your configurations are translated into an actual programming or query language and database tables are created for your data entities. Both in the cloud and on-premise, there is an infrastructure that runs your software.

在后台自动将所有配置转换为实际的编程或查询语言，并为数据实体创建数据库表。在云和本地中，都有运行您的软件的基础架构。

Without knowing how all the translations work, sub-optimal software code might be produced. This could lead to slow-performing queries, too many server calls, poorly structured database or even worse: the infamous spaghetti architecture.

在不知道所有翻译如何工作的情况下，可能会产生次优的软件代码。这可能导致查询速度慢，服务器调用过多，数据库结构不良甚至更糟：臭名昭著的意大利面条体系结构。

交货快 (Fast delivery)

An Agile way of working and Low-Code are a match made in heaven. The speed of developing and deploying Low-Code applications makes it much more feasible to act upon feedback and show results quickly.

敏捷的工作方式和低代码是天造地设的一对。开发和部署低代码应用程序的速度使根据反馈采取行动并Swift显示结果变得更加可行。

It’s also easy to develop from a user story perspective. Most Low-Code platforms provide a data — logic — interface setup out-of-the-box, which makes it ideal to build a full user story as a ‘chunk’ of front-end and back-end components. Developing your sprint backlog is a matter of building story after story.

从用户故事的角度来看，这也很容易开发。大多数低码平台都提供了开箱即用的数据-逻辑-接口设置，这使其非常适合将完整的用户故事构建为前端和后端组件的“块”。开发您的sprint待办事项是建立一个又一个故事的问题。

Functionally, this is great. Technically, it has some risks. Only focusing on the delivery of user stories might result in an inconsistent or non-existent foundation layer. Working on the data, logic and interface layers at the same time from a solely functional perspective could lead you to choices that jeopardize the stability, maintainability and reusability of these layers.

从功能上来说，这很棒。从技术上讲，它存在一些风险。仅关注用户故事的传递可能会导致基础层不一致或不存在。从单一功能的角度同时处理数据，逻辑和接口层，可能会导致您选择危及这些层的稳定性，可维护性和可重用性的选择。

The expectation of fast delivery poses a second risk: no priority on testing. A slick demo of a Low-Code platform will always show you how quickly you can build functionality. It will rarely show you how to incorporate component testing, regression testing or load testing. While Low-Code does reduce the need for some tests due to its built-in quality checks, a complete lack of testing is not advised.

期望快速交付会带来第二个风险：测试不被优先考虑。低代码平台的精巧演示将始终向您显示构建功能的速度。它很少会告诉您如何合并组件测试，回归测试或负载测试。尽管Low-Code通过其内置的质量检查确实减少了某些测试的需求，但建议不要完全缺乏测试。

With the greatest benefits of Low-Code — its reuse of best practice components, its ease and its speed — some risks come along. When not appropriately applied, the approach could lead to poor user experience, low-quality products or below-par performance.

低码最大的好处是-最佳实践组件的重用，易用性和速度-随之而来的是一些风险。如果使用不当，该方法可能会导致用户体验差，产品质量低下或性能低于标准。

But, no need to be afraid! This article is not meant to scare you; it just needs to be emphasized that Low-Code has to be done right to give you its promised results. For each of the risks stated above, technical and non-technical mechanisms can be implemented to reduce or even omit the risk.

但是，不必害怕！本文并非要吓you您；只是需要强调的是，必须正确执行低代码，才能为您提供承诺的结果。对于上述每种风险，可以实施技术和非技术机制以降低或什至忽略风险。

As an example, we have written several blog posts about how we execute our ‘Discover’ phase in projects [2, 3, 4, 5]. In this phase, we use extended Design Sprints to design the user experience before we use library components. This leads to a technology-agnostic design of the solution. To mitigate the other risks, we have carefully defined our ‘Develop’ phase. In this phase, we initiate the development with a development plan and a technical foundation plan. Our future articles will dive into these topics and describe how they help us to seize the great benefits of Low-Code.

例如，我们写了几篇博客文章，介绍如何在项目[2、3、4、5]中执行“发现”阶段。在此阶段，在使用库组件之前，我们将使用扩展的Design Sprint来设计用户体验。这导致该解决方案的技术不可知的设计。为了减轻其他风险，我们精心定义了“开发”阶段。在此阶段，我们通过开发计划和技术基础计划来启动开发。我们未来的文章将深入探讨这些主题，并描述它们如何帮助我们抓住低码的巨大好处。

This article is part of a larger series. To get an update when new articles are published, be sure to follow the Quatronic Medium publication or our LinkedIn.

本文是更大系列文章的一部分。 要在发布新文章时获得更新，请确保遵循Quatronic Medium出版物或我们的LinkedIn 。