Hey @petter got your book, and thought very useful - particularly for removing a lot of the opaqueness on how Bubble works! Many thanks for all the work you put into getting this together!
Have a question related to reusables and parameters (which wouldn’t have been around when you wrote the book). If you have a moment, I’d be interested in your view on it…
When I have a value that is required by a number of reusables (e.g. the answer to the question ‘Is this user a member?’) I pass the resulting value as a parameter to the reusables (often initially saving the starting value in an invisible group). Then, if there are reusables inside those reusables they also take that parameter value and pass it down, etc.
My assumption is that this is more effective than getting each reusable to go direct to Bubble and ask the question again - e.g. that it’s better to get the answer once, and distribute it. However, at the same time I know that Bubble caches queries, and that it wont ask the same query twice… and as such, perhaps sharing it as parameters is slower than just getting each reusable to ask the query again, as and when they need it? Passing parameter values makes debugging much easier - since if the rules to answer the question changes, it can just be changed in one place - but if passing parameters comes with a performance penalty then the gain from simplicity may not be worth it…