Insurance / logistics enterprise (pattern case) · 2021 · cost index 3/5
Low-code to replace engineering — then hire engineers
Seven-figure platform licenses; shadow IT integration debt
What happened
Leadership bought a low-code platform to "10× citizen developers" and shrink engineering headcount. Ops built brittle workflows. Integrations hit API limits. Governance panicked. Two years later the company hired senior engineers to untangle the graph citizen devs had painted over legacy APIs.
Failure mode
Vendor fantasy that drag-and-drop replaces distributed systems thinking. Edge cases, PII, idempotency, and version control do not fit in citizen-dev training decks. The org got faster demos and slower production change.
Lesson
Low-code wins internal tools with clear owners. It fails as a strategy to delete engineering because the business runs on exceptions — and exceptions are code whether you admit it or not.
Sources
- Forrester — citizen development limits
- Gartner — low-code technical debt surveys
- Enterprise shadow IT remediation patterns
Related tech
Practice · 2018–now
Low-code will replace eng
Drag-and-drop apps for the enterprise backlog. Useful for internal tools; fantasy as a full replacement for engineering.
Practice · 2021–now
AI pair programming
Autocomplete that actually understands the file. Changing how code is written faster than how it's reviewed.
Framework · 2023–now
LLM app frameworks
Chains, agents, and prompt wrappers shipping weekly. The durable pieces will be boring: evals, retrieval, and product UX.
Language · 1995–now
Java
Write once, run everywhere — then enterprise forever. Still the backbone of serious backend estates.
Platform · 1974–now
SQL / Relational
Declarative data that outlived every ORM fashion cycle. Postgres and friends keep winning by being boring.
Framework · 1999–now
J2EE / EE frameworks
EJB-heavy stacks taught a generation that XML config was architecture. Spring and lighter runtimes absorbed the survivors.