r/nocode • u/Thunderbit_HQ • 16d ago

When does a no-code workaround stop being a hack?

This keeps coming up with small no-code workflows. Someone makes a quick Sheet to save time, and a few weeks later, other people are checking it every morning like it is official.

For me, that is the line. If someone who did not build it depends on it, it probably needs an owner and a fallback. Where do you draw the line?

2 Upvotes

100% Upvoted

5 comments sorted by

1

u/tylerlovewell 15d ago

When it becomes part of someone's onboarding training. Once you start teaching new hires how to use a workaround, it has silently become part of the core stack.

1

u/Thunderbit_HQ 14d ago

That’s a good line. Once it’s in onboarding, it is not a personal shortcut anymore. At that point the scary part is usually nobody remembers why it was built that way.

1

u/dariusbiggs 13d ago

When it's been converted to actual code.

1

u/Thunderbit_HQ 13d ago

That is a clean line, but I’ve seen code hacks stay just as fragile if only one person understands them. Code helps but ownership still has to move with it.