kamen

Some laptops now have physical privacy shutters for that - and for those that don’t, you can get one that you can stick on top.

Saving a picture and posting it somewhere.

I see people making screenshots of their whole phone’s screen and posting them just to show a picture. In reality, maybe 90% of the time, if you see a picture on the screen of your phone, you can save that picture, with no pointless information around it, no black bars and so on. Even if that’s not possible, Android for example has been doing something from the recent apps screen that lets you extract a picture from an app’s screen - and that’s arguably even easier than doing a screenshot.

Electricity police, this fella right here…

Sketchy indeed. I’ve seen this as well, and the redeeming thing about it is that you’re locked out after 3 unsuccessful login attempts - so no matter how easy bruteforcing would be, there’s a safety catch dealing with it.

That Canadian tech guy. The channel has some good content, but that whole drama with the ex-employees, even without knowing the whole story, stinks of a toxic workplace, and I don’t want to support that. Plenty of other good tech-related content that I still follow - Level One Techs, Gamers Nexus, Hardware Canucks, Hardware Unboxed, JayzTwoCents.

Fro Knows Photo - used to have some good content years ago when I watched it, but started becoming more and more annoying, with clickbait thumbnails on almost every video.

SMoD - a good source for getting to know new/unknown bands in the doom/stoner/sludge metal realms, but unsubbed after the scandal.

Besides the water cooling that’s already mentioned, those could be used for example for routing an internal device out and into the I/O of the motherboard. An example would be some fan/RGB controllers that are meant to be somewhere inside the case, but are terminated with a standard USB A plug (and very few motherboards have that as an internal connector). Another example is a mini display that you could put inside the case that would need to interface with the GPU (so you’d need to route a DP or HDMI cable out of the case and into the back of the GPU).

“Catching mice is a stupid question.”

Also be mindful that a lot of online reviews might be sponsored, thus biased. I personally do look for reviews (ideally at least 2-3 different ones), but also for opinions of users on forums and other social media.

It’d be interesting to see that answered scientifically.

This must be a “hold my beer” kind of joke and someone wanting to see how far they can take it.

Weren’t you getting runtime errors for the function not being found?

Yes, and there’s that small thing that’s done in a slightly different manner that you can’t change through settings and it messes with your muscle memory.

Same.

No, we must rewrite it in this fancy new framework that came out last week.

(/s if not obvious)

I have the equivalent of RAID 5 too, but mind the usual “RAID is not a backup” - if you deliberately delete something (or something goes wrong with an app managing your media), hardware redundancy won’t save you in any way; it only helps if the data is intact and you want to remedy a hardware failure.

I only back up my music collection because I put extra effort into organising and tagging everything, plus some of it is rips of CDs not available anywhere. As for movies and TV shows, I only back up configurations and catalogues of the relevant apps, the contents themselves are 1) too big to be feasible to back up and 2) 99% of the time available to re-download.

I hope this is real; and if it is, I hope there are more teachers like this.

Imagine playing a shooter over a network using this protocol.

My take is use a GUI for anything read-only/nondestructive (i.e. anything that won’t modify your local or remote state). It’s nice for example to compare the state of two branches.

For anything that does changes make sure you know what’s happening under the hood, otherwise you might shoot yourself in the foot. It’s convenient for example to do a commit and push in one go, but then you lose the ability to edit any changes (you’re forced to either do another commit, or change your local commit and force push).

In VSCode you can go to the Output pane and switch to Git - there you’ll see everything that gets done through Git’s CLI for whatever you do through the GUI (although it can be a bit noisy); same goes other GUI utils.

One key thing that can help you wrap your head around rebasing is that branches get switched while you’re doing it; so, say you’re on branch feature and do git rebase master, for any merge conflict, whatever’s marked “current” will be on master and what’s “incoming” is from feature.

There’s also git rerere that should in theory remember a resolution you do between two branches and reuse it every time after the first; I’ve rarely used it in practice; it would happen for long lived branches that don’t get merged.