Chill Coding Weekend 😎
Already with the shift in development focus to the next section of the MOOVPAD Web App, I've come across more ways to optimise the code for MOOV data. So I thought I'd share this with you guys so you can see the reasoning behind it as well as the overall status of the code progress. Hope you enjoy this latest awesome release from Blume while I catch us up 🙂
Data Handling
The captures showing the code here were included to show how I'm structuring the coding and markup sections. In recent posts, I've been focused on the MOOV results section. This involved two 'parts': the user completing a new MOOV, and then the comparison with benchmark MOOVs that needed to be loaded. Now when I was working on just that section, it made sense to load all the benchmark data in one method/function.
However for other sections like the user's logged in homepage, some of this data will be needed, but not all of it. So I've broken up the one big method into smaller ones. This does two things. First, it means that the user's login process is quicker as less data needs to be loaded. Second, since some of the data will already be loaded at this initial stage, the loading of benchmark data later during a MOOV session will be quicker too. Both of these processes are therefore improved.
Also, the design of the homepage has changed to shift the Stats section to the larger panel on the left, for better focus on this data and to hold more of it.
See? Me learnings some some 🙂
Stay awesome,
EMH
