With the greatest intentions and exuberance we build the coolest solutions that make our stakeholders and clients smile. And then the other shoe drops - maintenance dependencies - where all profit and productivity escapes the cabin like a bird strike with complete decompression. We struggle to maintain control as the clear blue sky viewed from the cockpit begins to fade to a deep shade of dirt.
Happy hump day y’all!
More seriously, this is the realm and reality of no-code/low-code. You must budget for change because the risk envelope of impact from dependencies are vast and roughly 20 times greater than if you build them yourself for sustainability.
I have a client in the UK who paid me exactly once for a complex integration process. It has fired about 6 million times in two years without additional cost or subscription fees; not a single code-related error or deprecation issue has emerged while many parts of the system have changed around it. It is designed to self-heal in the event of a data mishap, or an API outage. This same client has more than 200 Zaps running and they are forever chasing issues with a team of two people who put out fires daily. They had difficulty breathing when their systems started failing a few days ago presumably because of this new version.
I’ve written about the risks of using these glu-factories; deprecation is just one of many.