Sourcetree is still best by far for history browsing, and I’ll die on that hill.
For a while my network switches were pilfered from the tech recycle bin at work. And oh so many laptop power cables (the Surface ones) so now I have one at every seat in my house.
Not so much stolen, but I was… unofficially gifted…a high performance SSD that had been sitting unused at the office for a few years. No one claimed it so I was told to take it.
And then the usual stack of notebooks, reams of paper, pens, and pencils from the office supply.
My home first aid kit is pretty well stocked too, totally unrelated to the individually packaged piles of pills at work of course.
I think it’s more that you can play the game with low res textures while all the high red ones download.
That and I’m sure they order the download so level 1’s textures download first too so you’ll probably not end up reaching the areas being downloaded until they’re available.
Also why bother releasing a plain old APK when someone can use apkmirror to grab it manually. Though at least adding an APK is relatively easy.
And if you are releasing the app manually you need some handling for updates (or informing users to install an update on their own). At least in Google Play users tend to stay relatively up to date. Otherwise any time someone reaches out about an issue you’ll be more likely to find them on older versions, wasting a bit of your time.
Do similar things with a similar meaning, don’t just do what they do. They might like buying small gifts, but receiving small gifts might make them feel guilty.
“Sir or ma’am I assure you it’s safe to send me your banking information. It’s over Signal, so it’s secure. I promise no one can steal it because its encrypted. That’s why we’re not using emails, emails are not secure. We need this information immediately, do not delay.”
That’s what sold it for me.
I don’t mind if reddit wants to make some money on their API, but giving app developers barely a month to respond, having insanely high prices, throwing away the relationships they built with app devs, and not responding to community feedback around the issue at all was all too much.
Necessary evil more than anything, but it does at least allow the valet to double/triple park and get more parking in a smaller area (at the cost of longer retrieval times at the end of the night), so at least it helps make parking space denser.
But would this policy actually prevent that? A vandal in a community of 100 people would only be charged 1% of the repair fees (assuming they aren’t caught), seems like a meaningless disincentive for them.
And forcing community members to self-police or be charged fees is asking for trouble.
It’s also part of the reason why maintenance budgets exist. The condo board/government/etc should be responsible for factoring in the risk of vandalism repairs into their budget and spreading that cost over time. That’s why they exist.
At the end of the day it’s my dues/taxes that pay it either way, but I shouldn’t get stuck with a surprise assessment unless it’s a major unexpected repair.
Teaching them our sense for justice worries me. Either they understand we can police ourselves or they start holding us accountable for wrongdoings under their legal system with no warning, assuming we’ll understand.
While you’re getting started, put anything effemeral in Docker and keep anything meant to be persistent on the host directly.
Docker is great, but the number of times I’ve accidentally blown away data before I learned what I was doing… Just give it some practice before you put anything out there that you can’t remake quickly.
Same question, all modern browsers are reasonably secure for the average person’s security concerns (privacy on the other hand… Eek).
Don’t just summarize the content though, summarize the rationale or how things connect. I can read your diff myself to see what changed, I want to know the logical connections, the reason you did X and not Y, etc.
Or just say “stuff” and provide that context in the PR description separately, no need to overdo the commit log on a feature branch if you’re using squash merges from your PR.