In the State Changers meeting, a member presented some issues they were having with developing specific functions in a coding project. They shed light on the process they were following, such as decluttering loops with nested functions and creating stubs for fiscal years and issuance periods. A main issue was related to a large sub if statement being used in a consolidated debt schedule project. They had identified the problem but were looking for ways to solve it. Another issue involved dealing with a then-empty 'else' condition if they decoupled an update variable to another 'if' statement. While explaining the issue out loud, the member realized they were approaching it from the wrong angle and arrived at a potential solution. The group decided they could discuss the rest of the coding problems in the next meeting. The keywords "function," and "if statement" were mentioned. Keywords such as "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" did not feature in this meeting.
(Source: Office Hours 8/14/23 )
