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 — a rhyme with later unsanctioned AI workflows.
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–2025
Low-code will replace eng
Drag-and-drop apps for the enterprise backlog. Useful for internal tools; fantasy as a full replacement for engineering — a pitch later absorbed by AI demos.
Practice · 2021–now
AI pair programming
Autocomplete that understands the file — now table stakes. Generation outran review capacity; ownership is the bottleneck.
Framework · 2023–now
LLM app frameworks
LangChain-class glue gave way to vendor SDKs and thin wrappers. The durable pieces are 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.
Practice · 2024–now
Vibe coding
Accept AI output on feel, skip the diff, hope tests exist. Fast demos; CVEs and nobody owns the middleware.
$ Ship-to-prod without reading the diff became a flex until incidents revealed nobody knew which prompt wrote the auth middleware. Review debt arrived in one weekend demo.
Practice · 2023–now
Shadow AI / paste-into-ChatGPT
Prod data into consumer chat because the approved tool is slow. GDPR with better autocomplete.
$ Employees routed tickets, logs, and customer PII through consumer chat before InfoSec finished procurement. Compliance scramble followed the demos.