log 3: minimizing maximization
min-maxing
Moving from the planning phase to the action phase is incredibly difficult and somewhat mentally taxing. I imagined it would be much easier, especially while following a detailed plan of attack. Being in the process of learning while developing has set me back multiple times. Earlier in the week, I was finally able to figure out how to extract my values from the Cloud Firestore Database that I created, which was a huge win. Shifting from being totally blind working with a new database to seeing how the pieces of the puzzle slowly start fitting together is very rewarding. Although I am finally able to extract pieces of data from my database, there is the problem of optimization. I’m not entirely sure of how to optimize the data or even my app so that the querying doesn’t take forever. Optimization in Cloud Firestore requires the placement of data in collections and documents while also figuring out where to repeat the data for easier querying. While it is definitely a later problem, it’s still something to think about now so that the running of my app is faster. And this is my problem. I get so stuck on trying to make it perfect and maximize my time so that I don’t have to worry about it later, when in reality, I have to focus on getting the barebones of my app done. Even if the progress is little, it still leads to the final product. Here is what I have worked on in the past few days.
As I mentioned previously, after a frustrating bit of coding and testing I was finally able to figure out how to extract specific values from the collection/document system in Cloud Firestore. This is probably the definition of “a small win” because it really is a tiny win. However, it is a big stepping stone to automating the reading process. Being able to have values displayed without other random values interjected into the value allows me to display the data on the screen directly, or use it in finding other information. My next step in the database reading is to automate the collection path because, at this moment, I have to type in the document path manually.
Aside from working on my app and other miscellaneous company work, I have been studying for the CSCS (Certified Strength and Conditioning Specialist). Although I could definitely pass the CPT exam blindfolded, the CSCS has far more useful and detailed information. Studying for the CSCS and reading through the textbook has reinforced so many concepts about training that I had already learned. It is also the first textbook that I have dedicated time to read end to end, sorry college. This week I read about the 7 steps to efficient program design which has previously sparked my inspiration for building anything. While the actual steps are irrelevant in this case, I was reminded that there is always a structure and there is always a plan, so follow it. When you’re stuck, go back to the plan. When you’re not stuck, make sure it’s part of the plan. Following the plan is probably going to yield the best and most reliable results regardless of how much you work during the week. That being said, I hope I’m able to follow my plan and put some sizable work into learning or developing this coming week.
