Hey everyone,
So today, I was actually stuck on a problem for a long time. I’ve tried so many solutions that didn’t really help out. It was from looking at my own code where I wasn’t able to see anything wrong with it, towards listening to a task, down to rebuilding my view model again and disposing my listeners, down towards recreating my activity.
The last two options work pretty much the same way, with the exception of recreating all of your views and adapters (if any) which can be a much more expensive operation if you had to deal with many objects, versus dealing with maybe 4 or 5 items. Unless it’s better to do a recreation of an activity without worrying too much just as a page refresh, and if it takes at most 3 seconds to load the page, then that’s worth the change.
Anyhow, this post was more about being stuck on a problem. It turns out that the problem was laying under the shared code, and it was a boolean that was missing there that just didn’t provide the results for me on time!
Wow, now that’s not so easy to find. I had a second pair of eyes to take a look as well. And yes, although he had told me what I should try, I have already done most everything and it’s better just to say so. Therefore, it’s always better to know what you have done and then explain it as simplified as possible.
So that’s where the problem lies. Okay, I’m probably not too much of a genius, but I do know what I’ve tried. I also don’t want code that seems too complicated, or even spaghetti, otherwise it just seems like too much time and even trying to find out what each segment does.
However, that’s most of what our code looks like. But since I’ve learned to always try and simplify the code, it’s serving me quite well.
Therefore, remember that quality of work is always important. Otherwise, watch out and don’t let bad code pile up to a mess.
That’s all I have for thoughts, and until next time!
Brian.