Clear history to save space
$ cd myrepo
$ rm -rf .git

This has been bugging me about my Samsung monitor. Thankfully I found the answer HERE. Basically, go to your monitor’s Settings. Try Setup and make sure it is set to PC mode rather than AV mode (for TV)

To sort a row of columns:
Define the following formula on a blank row:
=transpose(sort(transpose(C3:H4)))
Then just copy the sorted row and copy...special..values only
Delete all but the copied row

To sort column of addresses that contain street numbers [1]:
Create a blank column next to the address column. Select a blank cell adjacent to the address list, and type this formula =MID(A1,FIND(” “,A1)+1,255) (A1 is the cell of your address list), and press Enter button, then drag the fill handle to fill the range you want. After that, you can see all addresses are extracted to the help column except the street numbers.

The following will create a new file with lines removed containing given pattern:

cat file.txt | grep -v "pattern" >filtered.txt

Match two words:
grep -E -i -w 'word1|word2' sourcefile.txt
grep -rl "string" /path // -r recurse, -l output filenames only

Test your speed here.

Netflix recommends a minimum of three megabits per second for standard-definition video quality, five Mbps for HD, and 25 Mbps for Ultra HD content.

So when streaming video best to connect to the faster 5G band.  The 2.4 band is about 1/2 the speed.  If many devices are using the same band it could slow things down.

Update May 9, 2020: Another good article about passwords: Why jK8v!ge4D isn’t a good password

You can find plenty of arguments to counter the points made in the article linked below, but I happen to agree with many of the points made.
I password is useless if you can’t remember it and these days, we all have tons we have to remember.

At work I had to write a password validator to use in a mobile app’s enrollment screen.  I chose to only allow the special characters found on a standard keyboard. No extended ascii characters allowed.   Limiting support calls was my main motivation.

Myth #2. Dj#wP3M$c is a Great Password

A common myth is that totally random passwords spit out by password generators are the best passwords. This is not true. While they may in fact be strong passwords, they are usually difficult to remember, slow to type, and sometimes vulnerable to attacks against the password generating algorithm. It is easy to create passwords that are just as strong but much easier to remember by using a few simple techniques. For example, consider the password “Makeit20@password.com”. This password utilizes upper and lower-case letters, two numbers, and two symbols. The password is 20 characters long and can be memorized with very little effort; perhaps even by the time you finish this article. Moreover, this password can be typed very fast. The portion “Makeit20” alternates between left and right-handed keys on the keyboard, improving speed, decreasing typos, and decreasing the chances of someone being able to discover your password by watching you (for a list of nearly eight thousand English words that alternate between left and right-handed keys, see http://www.xato.net/downloads/lrwords.txt.)

The best technique for creating complex passwords that are easier to remember is to use data structures that we are accustomed to remembering. Such structures also make it easy to include punctuation characters in the password, as in the e-mail address example used above. Other data structures that are easy to remember are phone numbers, addresses, names, file paths, etc. Consider also that certain elements make things more memorable for us. For example, patterns, repetition, rhymes, humor, and even offensive words all make passwords that we will never forget.

Click here for full article

When creating a Facebook post, if you include a url to a website, Facebook will preview the website in your post.  Facebook looks in a cached version of the home page so if it has changed since Facebook cached it, it may not preview correctly.  To force Facebook to fetch a fresh version, go here: https://developers.facebook.com/tools/debug/

Great analysis of the differences between Google Maps and Apple Maps

Here is there summary:

We looked at 54 pairs of maps across three cities (New York, San Francisco, and London) and found several significant differences:

• Apple Maps, on average, labels more citiesthan Google at every zoom.
• Google Maps, on average, labels more roadsthan Apple on nearly every zoom.
• For two-thirds of zooms, both maps generallyshow the same number of roads. For the remaining third, Apple almost always shows more roads.
• Both maps, on average, label a similar number of POIs—but have only 15% of their POIs in common on an average zoom.
• Both maps also prioritize different kinds of POIs: Google Maps heavily prioritizes transit, while Apple prioritizes landmarks. Apple also generally shows a greater number of POI categories on a given zoom—and shows twice as many restaurants and shops as Google.