As a system architect building interconnected tables, I want to prevent circular dependencies so that my data model remains stable, avoids infinite loops, and does not break reporting, syncing, or automation logic.
I think a lot of this would come down to the planning stages of an application if you are building a new one, mapping out the entity relationships and making sure the logic makes sense. Sometimes you have to take over applications that others built and don't have any control over how they designed it, in those cases try to understand the existing structure as much as you can, then plan out ways it can be optimized. Aim for a series of small wins that progressively enhance the application instead of one giant restructuring.
At a point refactoring and restructuring is the best way out of code but with low code we're limited considering factors like we don't have ownership of the base. Just like the way we rejoice and brag of achieving a lot in small time we also have the sad side of not having control of everything we build.
