I read that recently as well, it is a great read. I can relate to a lot of the things. While it is meant as a humor piece, there is some solid advice in there.

I didn’t exactly have it in mind when I wrote my comment, but maybe subconsciously 😅

Caveman no understand

It is amazing how many cavemen didn’t understand the sarcasm of my comment, and in their rage had to downvote it to hell. 😂

This always happens to me when I’ve written some genius code. Takes so long to review it, because my caveman colleagues don’t understand it.

I’ve played around 90 hours of the game. I’ve done all the big quest lines except for the companion ones. I will stop playing it for now. Maybe, some time in the future if more content is added I will play it again. I might do the pirate quest one more time to see the opposite outcome. But content wise this is more or less it. If I hadn’t repeated some of the quests I would have spent much less time to complete all the above.

I didn’t want to grind out multiple NG+ to get a better suit. Not worth it at this point.

Wonder how long it will take for them to become available in Azure DevOps Pipelines 🤔

A lot of this info has been restricted in newer versions of Android, so you can only get this info if you have root access.

That sucks. I was considering one of their devices instead of a Google Pixel, mainly due to the form factor. I guess not anymore.

It is a bit of wishful thinking, but could be cool if they had an AndroidX package with some kind of global caching system. Problem is though, how do you make a caching mechanism that can fit all use cases.

LRU cache seems like a good choice for caching images. Then set a max size and/or age of items in the cache and evict as necessary. This is the defacto caching mechanism in Apps.