Rethinking Low-code
summary
Examines why current low-code/visual BPM platforms fail to deliver promised benefits: they produce XML/JSON blobs that defeat git diff, lack unit-test and static-analysis hooks, and rely on ad-hoc embedded JavaScript that leaks state, creating technical debt. Proposes concrete fixes: a small constrained application language, metaprogramming and code generation for forms, and a clear separation between system programming and application programming (while noting no complete alternative yet exists).
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:06Talk topic conflict
- 2:57What is low-code
- 8:38No version control testing
- 11:05Modularity architecture issues
- 13:15Staff qualifications
- 15:00Built-in low-code languages
- 19:47Marketing myths consequences
- 22:23Why low-code dead end
- 23:25Alternative low-code approach
- 25:54Role separation
- 33:28Q&A
related talks
39mWhy You Should Look Into Low Code
23mEmbracing low code as a hardcore developer
41mEnable Enterprise Citizen Development with Low Code No Code
29mLow-Code: It’s Also for Developers
07m"Learn how no-code/low-code can make you more productive."
57mThe Future: Low Code & Citizen Developer
28mLow Code Or No Code
31mHow We Write Better Software with Low-Code