log 39: data

input

Part of the optimization process also includes refining what I already have. Previously, I had limited amounts of data that my app could query in order to grab the most optimal exercise. In order to make the exercise selection more accurate I needed to add more data. Things like, what equipment is required, priority, if it is time-based, and more. Adding these pieces of information allows me to query more specific results for the client. It will also save a lot more time in the process because I am able to add filters and filter the search parameters rather than the end result. I did get stuck, however, trying to categorize hundreds of exercises. It is rather tricky trying to pair different exercises with generic categories. But, I figure giving it a 70% match now to get me going is better than adding nothing. I can always revisit it if I think of a better way to organize data. The process has been extremely tedious so far because I have to import everything one by one. I did find a user API for Firestore and that has made it far easier. Make sure to always check if someone created a short cut! It can make tedious work less tedious, time and focus is precious!

Previous
Previous

log 40: development

Next
Next

log 38: speed