This is a semi-good LPT. You can save a lot of time and grievance by just not folding your clothes and throwing them into piles (inside boxes or drawers, preferably) by type (socks, underwear, shirts, etc). Bonus tip - if you have a spot where dirty clothes keep piling up (used to be bedroom for me), just put a laundry basket there (in the exact spot you discard your dirty clothes).
If you hate doing laundry, get a dryer and do this, it will make it so much easier. It becomes transport your basket from your aggregation area, dump it in the washer, throw in a random amount of whatever washing thing around, set an alarm on phone, throw it in the dryer, second alarm, take it to your usage pile(s). Turns laundry from tedious into barely a chore.
I recently upgraded to the new GE all in one washer dryer. Removes a massive step of having to move clothes between dryer and washer. Toss em in, and 2 hours later they’re done. Best part is they can be tossed in before bed and ready in the morning for work!
None of those specifically, but after you have a virtualization host your flock tends to grow pretty quickly. More that I’m hosting big multi-user things like nextcloud for a single user.
Imma be honest I pulled that estimate out of my ass lol, but I feel like it was pre-pandemic? which would put it at at least 4 years ago and so holy shit I’m gonna go cry in a corner because it’s been 4 years since the start of the pandemic
Isn’t this only the case in github? All my repos are based from master, and I would assume that’s because I init on the command line and push up to the remote?
GitLab also changed a few years back. We host our own, so got the update later than people using the service … it was a bit of an argument at first since everyone wanted to stick with the familiar, but laziness won out. Unfortunately, it’s not really justifiable to go back and change legacy projects, so now it’s inconsistent
If you don’t have any scripts that rely on branch name it should be pretty trivial actually. But I wouldn’t be shocked if you had a few dozen scripts that nobody has looked at in the last century lol
The question actually came up for a new tool to help automate dependency updates. Do we need to change the config to account for the inconsistency?
It turns out we don’t: it correctly uses the default branch, no matter what it’s called. However we had to consider the question. and investigate. It spent someone’s time
It works fine for small projects. I think that with more than 2-3 devs a PR based strategy works better for enforcing review and just makes life easier in general, since you end up with less stuff like force pushes to fix minor things like whitespace errors that break everyone’s local.
I don’t understand how anyone uses a paid API for a personal project. I looked hard into MS, Google and Amazon a few years ago for a project and couldn’t find anywhere where you could hard block services to never ever go above the free tier.
Considering that I’ll build a project and forget about it for years, putting in my credit card into a cloud service was a guaranteed gigantic bill sometime in the future when things went wrong. (Over your life, something is guaranteed to go wrong.)
Have you heard of virtual debit cards? You can’t charge what’s not there.
Also, at least AWS will in fact send you an email when you approach the end of free tour usage.
Having said all that, most devs can host the few hundred visits they might get over a month with a $200 home server and a free CloudFlare cache if they know what they’re doing.
All cloud providers will support budget notifications. That doesn’t do much good when you shoot past the budget in a short timespan. I set a Google cloud budget of $20/month and enabled a Tensorboard instance, which had no observable indication that it cost anything except the base cost of the VM, and got notified that I was $280 over budget the next day. Apparently there was an upfront $300/month/user fee for Tensorboard. (Several months later they changed the pricing model to $10 GiB/month with no user fee.)
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.