In this meeting, the State Changers discuss a problem observed during a demo, as well as the debugging and solution processes. The discussion is mainly centered around the notions of fetching data, authentication processes, JavaScript coding and the performance analysis of networked systems.
At the beginning, the State Changers notice an error when passing an incorrect password, and after correctly logging in, an unexpected refresh occurs. Through detailed observation of both front-end and back-end behaviour, the State Changers realize that the issue might be due to the execution sequence of login and geolocation fetching processes. To resolve this, they suggest refactoring the code to ensure the login authentication process occurs before geolocation fetching. They also mention the use of promise syntax and async/await in terms of JavaScript code structure, recommending a preference for async/await for cleaner syntax, but only when necessary for better understanding or when refactoring addresses a problem. Further, they discuss the use of dev tools, specifically the network tab in Chrome's developer tools to monitor performance and identify bottlenecks. This process includes analyzing time logs and chart-style bars representing the firing sequences of different processes to understand overall performance. The meeting concludes with a callback to 'Weebly' and suggests recording and sharing network tab data to address any performance issues. However, no specific tools like "Zapier", "Make", "Bubble", "Firebase", etc., mentioned in the preamble were explicitly referred to in the meeting discussion.
(Source: Office Hours 3/31 )
