I have two voices in my head when it comes to new tech. One is the wide-eyed optimist who wants to try every tool and click every AI button. The other wants to delete every app on my phone, move to a cabin in the woods, and write by candlelight. There's no doubt AI is exciting.
I have two voices in my head when it comes to new tech. One is the wide-eyed optimist who wants to try every tool and click every AI button. The other wants to delete every app on my phone, move to a cabin in the woods, and write by candlelight. There's no doubt AI is exciting.
In context
- Topic: Low-Code y No-Code — Plataformas de bajo código, su gobierno y su deuda técnica.
- Source: Zapier Blog
- Published: 08/10/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
Everything that gets automated stops being visible. That is the benefit and also the risk: the work does itself until the day it stops doing itself, and by then the person who understood the manual process has left the company.
My criterion for what to automate is simple: high volume, stable rules and bounded consequences when it goes wrong. When any of the three is missing, automation costs more than it saves and gets dismantled within eight months.
What usually goes wrong
Where it usually goes wrong is permissions. To make the flow work, an account with broad access gets created because that is the quick path, and that account stays there forever with no owner and no review. It is the most common back door I find when auditing an automated operation.
What to watch
- Cost per run at real volume, which on these platforms scales fast and surprises people.
- How the flow reports failure, and to whom: without that, the error gets discovered by the customer.
- How many flows already exist and who maintains them, which is where the invisible debt shows up.
How I read this entry
If this were adopted in an organisation, I would ask from day one for a simple register: which flows exist, who built them, which systems they touch, and who to call when they fail. It costs an afternoon to set up and avoids the scenario where nobody knows what broke.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Comments
No comments yet. Yours can be the first.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
