Today I learned
- I’m trying to cram too many things into a single function.
- The downfall here is that I want to name things that are easy to remember, and have functions that are only differ in by a line or two so that makes things…fuzzy
- Also, who cares? Are you gonna see my dirty code? NOPE!!! So I’mma make 2 different model methods so that I can call them based on an enum state.
- Clean it up later! Make the dumb thing work!
- Timer objects will run until you call .invalidate() on them. This causes problems if you invoke a timer more than once without stoping it (or realizing that you created 2 timer objects). I will make the timer fire more than once a second.
- I think I’ve just about finished part of my MVP on this silly app. I have one major feature I want to build. Most of the logic is already there, since I’ve been using a modified VM architecture. My logic is all chilling in one ViewModel object with my preferences all wrapped in ‘@AppStorage’ properties.
I know it’s been (literally) 2 months since I last posted a TIL. Life gets in the way! My schedule is still flexible, and I have to be that way too. Thanks for reading!