In this meeting among the State Changers, the focus was primarily on resolving a query of Juan about calculations regarding the iterative calculation of accumulated interest and payments in current periods by referring to the previous one. The team suggested using the 'stop and debug' tool to understand how a process progresses. This utility function helps in controlling the process, step by step, in a way that it gives transparency on how the operational manipulation is happening. For instance, what is the number after each step, how it is getting manipulated, and where the difference is arising between expected outcomes and what the system is doing.
Moreover, for complex calculations around like arrays and objects which include mathematical changes, the team suggested using a test approach helps in giving confidence that it's all working at the unit level. Another suggested approach was to calculate balance at the start, outside the loop, and then modifying it internally inside the loop on each step. In this meeting although keywords like "Xano", "WeWeb", "FlutterFlow", "Zapier", "Make", "Integromat", "Outseta", "Retool", "Bubble", "Adalo", "AppGyver", "AppSheet", "Comnoco", "Fastgen", "Firebase", "Google", "OAuth", "Stripe", "Twilio", "Airtable", "DraftBit", "Javascript", "Typescript", "React", "Vue.js", "JSX", "HTML", "CSS", "lambda", "serverless", "State Change", "ScriptTag", "OpenAI", "AI21" were mentioned, the meeting does not seem to specifically include discussions about them. It was rather a technical guidance session for Juan regarding the computation of interests and payments in different periods.
(Source: Office Hours 6/22/2023 )
