Files
logseq/pages/@Low-Code Is Often High-Code, So We Must Design Low-Code Platforms to Enable Proper Software Engineering.md
2025-06-05 22:07:12 +02:00

21 lines
2.2 KiB
Markdown

date:: 2021
publisher:: Springer International Publishing
place:: Cham
isbn:: 978-3-030-89158-9 978-3-030-89159-6
title:: @Low-Code Is Often High-Code, So We Must Design Low-Code Platforms to Enable Proper Software Engineering
book-title:: "Leveraging Applications of Formal Methods, Verification and Validation"
pages:: 202-212
volume:: 13036
item-type:: [[bookSection]]
access-date:: 2023-05-17T09:46:34Z
original-title:: "Low-Code Is Often High-Code, So We Must Design Low-Code Platforms to Enable Proper Software Engineering"
language:: en
url:: https://link.springer.com/10.1007/978-3-030-89159-6_14
authors:: [[Timothy C. Lethbridge]]
library-catalog:: DOI.org (Crossref)
links:: [Local library](zotero://select/library/items/8LBEA26Y), [Web library](https://www.zotero.org/users/1039502/items/8LBEA26Y)
- [[Abstract]]
- The concept of low-code (and no-code) platforms has been around for decades, even before the term was used. The idea is that applications on these platforms can be built by people with less technical expertise than a professional programmer, yet can leverage powerful technology such as, for example, for databases, financial analysis, web development and machine learning. However, in practice, software written on such platforms often accumulates large volumes of complex code, which can be worse to maintain than in traditional languages because the low-code platforms tend not to properly support good engineering practices such as version control, separation of concerns, automated testing and literate programming. In this paper we discuss experiences with several low-code platforms and provide suggestions for directions forward towards an era where the benefits of low-code can be obtained without accumulation of technical debt. Our recommendations focus on ensuring low-code platforms enable scaling, understandability, documentability, testability, vendor-independence, and the overall user experience for developers those end-users who do some development.
- [[Attachments]]
- [Lethbridge - 2021 - Low-Code Is Often High-Code, So We Must Design Low.pdf](zotero://select/library/items/96MP3IME) {{zotero-imported-file 96MP3IME, "Lethbridge - 2021 - Low-Code Is Often High-Code, So We Must Design Low.pdf"}}