This is a cycle that repeats every 10-12 years imo.
And then, after 2 or 3 years, the hype is gone, because it turns out that
a) Complexity can be hidden and displaced but not eliminated
b) Vendor Lock-In issues
c) Interoperability issues with existing tools, platforms and systems (ever tried to version-control a nolo-code project?)
and last but certainly not least
d) As projects get bigger and requirements pile up, at some point there is a requirement not satisfied by the platform; then the dance to somehow interface it with "some code" starts, then the next requirement comes along, and the next, and at some point somehow aska the question "Wouldn't it be simpler to rewrite this in XYZ" and at that point the cycle usually ends.
That doesn't mean that these things do not add value. The hype is usually gone after each cycle, but useful things that help a lot of people making things they would't have otherwise made remain.
Comments
This is a cycle that repeats every 10-12 years imo.
And then, after 2 or 3 years, the hype is gone, because it turns out that
a) Complexity can be hidden and displaced but not eliminated
b) Vendor Lock-In issues
c) Interoperability issues with existing tools, platforms and systems (ever tried to version-control a nolo-code project?)
and last but certainly not least
d) As projects get bigger and requirements pile up, at some point there is a requirement not satisfied by the platform; then the dance to somehow interface it with "some code" starts, then the next requirement comes along, and the next, and at some point somehow aska the question "Wouldn't it be simpler to rewrite this in XYZ" and at that point the cycle usually ends.
That doesn't mean that these things do not add value. The hype is usually gone after each cycle, but useful things that help a lot of people making things they would't have otherwise made remain.
But it doesn't replace coding.