One of the things that's beneficial with writing code (as opposed to using something like Retool, as awesome as it is) is that it's easier to get a bird's eye view of what's going on/how everything relates, and searching through code to find those relations is not only fast but pretty intuitive, at least for someone who's used to doing it. Even better is having some sort of UML diagram-thing that dynamically maps the architecture in a flow-chart-like way, but I don't do this myself unless it's something simple I whip up Whimsical.
However with Retool, I find myself constantly flipping between my many queries, components, and their respective event handlers, trying to assemble in my mind how they're chained together. I sometimes make quick flow charts to make sure that I'm not duplicating any queries that are already being triggered by another's onSuccess handler (or via the normal query event handlers), but it feels like walking around a cave with a candle, since I have to visit queries one by one, check components one by one, to figure out how certain actions are chained. Of course, designing things consistently and predictably from the ground up on my end makes introducing bugs less likely and this process less arduous, but things don't always go as planned, and changing how queries/events fire each other can become hairy business if I have to re-design certain action flows.
What I'd like to see (this is admittedly a big ask) is for Retool to provide a dynamic flowchart for how all my queries, their corresponding event handlers, and my components' event handlers (and perhaps even hard-coded triggers() inside JS queries) all relate to each other. That way it's easier to avoid duplicating certain logic/certain guards for specific actions firing, as well as knowing where the right place in the chain to insert a new event handler is.
Event handlers can't be chained in Retool (always run in parallel, unless I guess writing a script), which would solve some of the problem, but the real pain point is that even when I design the flow such that I'm using the right string of query event handlers/component event handlers to execute a full chain of actions, if any of that needs to be changed down the line, I have to methodically examine each query, component, and their event handlers to understand once again how everything is chained before making a change.
I realize you have to do something similar with code, but combing through code is much easier to solve the same problem then having to inspect every suspect component/query in a GUI. A flowchart would function as a map so I knew where exactly to dive in.
Please let me know if this makes sense or if I'm approaching the whole problem in a poor way!