3 ms·
Low code allows "less" sunken cost when the inevitable misalignment of requirements happen. It's same reason why design starts on napkins, then wireframes, and
by pxue 4y ago
Low code allows "less" sunken cost when the inevitable misalignment of requirements happen.
It's same reason why design starts on napkins, then wireframes, and then low def, high def and eventually a fully interactive prototype.
In software we dive into code way to eagerly and way too early in the product process.
Equating no/low code tools to full on dev is impossible. Just as you wouldn't/shouldn't equate a design prototype to napkin scribbles.
- ElectricalUnion 4y ago> In software we dive into code way to eagerly and way too early in the product process. Low code doesn't help at all? It's still code. > Low code allows "less" sunken cost when the inevitable misalignment of requirements happen. Sunken cost is about investment already incurred that can't be recovered. It's very likely that low code increases software sunk cost problems. If you use low code as a prototype thing to throw away, that's almost a complete waste of investment. Wrong low code often is much harder to programmatically test for correctness and debug, so you often need a larger investment to fix it.