This meeting among the State Changers focused on how to optimize data handling processes, particularly considering user activities by creating a user-friendly table structure. One participant queried if having work-in-progress tables would bring about better performance when cataloging user activity, envisaging it to provide faster and specific data that can be pushed to a front end.
The general consensus was that during the early stages of a product's lifecycle, optimization for performance need not be a priority. This is because, with expected limited user numbers, any impact on database performance would be negligible. Instead, the focus should be on the ease of data management and understanding for the developer, recommending simplified tables for dealing with small user bases.
Further, the discussion segued to the participant's efforts on WeWeb where they have a master form consisting of multiple microforms. The intent is to capture user input and process it upon form submission in a way that a variable (essentially an object) is gradually extended.
A demonstration was conducted on how to achieve this: after altering a variable's value, say, 'start time', developers can add it to the object. This is done by using the 'Partial Update' action, enabling the developer to update just one aspect, like the start time. It was highlighted that maintaining multiple simple functions could be more convenient than one complex function.
(Source: Office Hours 1/27 )