The meeting was attended by State Changers, and they discussed a coding and machine learning dilemma related to variables posting information to an endpoint with DialogFlow, a natural language understanding platform. The main challenge brought forth was the placement and behavior of variables in if statements. One participant was attempting to ensure that multiple variables are present and saved using certain conditional statements and considered employing complex if statements, dealing with an imposter syndrome along the process.
The State Changers advised that the problem might be related to the location or extraction of data and one could take either a "data interrogation" approach or a "caching" approach. The attendees were advised to look at the data to solve the issue before considering cache options like storing information in a database and retrieving it when necessary. The conversation also touched on performance concerns, with the State Changers emphasizing the importance of focusing on functionality and correctness over computational efficiency. The State Changers suggested that issues related to computational complexity ("Big O notation") could arise from nested "for" loops, not from nested "if" statements. There were no references to "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". The meeting would be helpful for those interested in the intricacies of code development, variable placement and tracking, machine learning application, and dealing with data extraction challenges. It also touched upon the challenges of imposter syndrome and the independent debugging. Structuring logic and identifying complexities in the code were significant themes of discussion.
(Source: Office Hours 7/18 )
