log 40: development

challenge

Rewriting my algorithm with my previous work as a template and my new skills as tools has been pretty difficult. While I have been able to get a lot of functions to work universally there is still a lot of things I have to learn. The most difficult part is knowing when and where data has been loaded. If the data hasn’t been loaded yet and I call for it, my app crashes. If the data has already been loaded and I load it again, I’m wasting time and space. If the data is in the process of being loaded and I call it, it crashes. I’m surprised I have to think about timing and load orders this much, but it does feel like I am making a good bit of progress. Previously, my “algorithm” only randomly picked exercises. What I am doing currently is adding more logic. What equipment does a person have, is it a core exercise, what training day is it on, and what is their workout split? So many questions and variables but this is the fun part. Using my brain and being able to apply new skills is extremely challenging, but exciting! This is the bread and butter of my app, so I better make sure it works well.

Previous
Previous

log 41: b-logs

Next
Next

log 39: data