GLMeece

Steps to Terminal Enlightenment on a Mac

Hopefully you'll Live Long and Prosper, so I don't mean terminal as in "you gonna die". This is a somewhat opinionated article on configuring a macOS machine with:

• iTerm2
• Z-shell
• Oh My ZSH! (mostly obsolete now)
• Powerlevel9k
• Nerd Fonts, which are Powerline-derived fonts, particularly my favorite - Hack Nerd

GLMeece

Unicode for Keyboard Symbols

• ⎋ (escape): U+238B
• ⇥ (tab): U+21E5
• ⇪ (caps lock): U+21EA
• ⇧ (shift): U+21E7
• ⌃ (control): U+2303
• ⌥ (option): U+2325
•  (Apple): U+F8FF (in some Apple-provided fonts only)
• ⌘ (command): U+2318

GLMeece

Copied from http://code.lancepollard.com/complete-list-of-html-meta-tags/

Basic HTML Meta Tags

<meta charset='UTF-8'>
<meta name='keywords' content='your, tags'>
<meta name='description' content='150 words'>
<meta name='subject' content='your website's subject'>
<meta name='copyright' content='company name'>

GLMeece

NANO on macOS and Windows

This should get you up and running with the installation and basic configuration of GNU Nano on both macOS and Windows. In the case of macOS, this will install a newer version of Nano that includes syntax highlighting.

macOS Installation

Homebrew

It is assumed you already have Homebrew installed. If not, then Verify or Install Apple's Command-line Tools and then proceed with the installation of Homebrew. 🍺

GLMeece

New macOS Machine Setup

This guide is based on my own experience, but also draws on other guides. It is primarily oriented towards those doing code-related stuff (e.g., I'm mostly an SDET, but is also applicable to those doing either Python or Web-based development).

A couple of other examples:

• Setting up my Dev Environment on a Mac.
• macOS Catalina: Setting up a Mac for Development

Most of the setup will use the terminal. For more details on how to setup an awesome terminal experience on the Mac, see my guide Steps to Terminal Enlightenment on a Mac (tweaking your terminal for fun and profit), which in fact includes some of these steps (you're welcome!).

GLMeece

Master List of Logical Fallacies

original article here

Fallacies are fake or deceptive arguments, "junk cognition," that is, arguments that seem irrefutable but prove nothing. Fallacies often seem superficially sound and they far too often retain immense persuasive power even after being clearly exposed as false. Like epidemics, fallacies sometimes "burn through" entire populations, often with the most tragic results, before their power is diminished or lost. Fallacies are not always deliberate, but a good scholar’s purpose is always to identify and unmask fallacies in arguments. Note that many of these definitions overlap, but the goal here is to identify contemporary and classic fallacies as they are used in today's discourse. Effort has been made to avoid mere word-games (e.g., "The Fallacist's Fallacy," or the famous "Crocodile's Paradox" of classic times), or the so-called "fallacies" of purely formal and symbolic, business and financia

GLMeece

If you have a company-managed OneDrive account like I do, you probably will never need or want to access a personal OneDrive account. It clutters up the Explorer menu and it's likely that you would prefer not to see it. Here's where I got the answer.

How to Stop Personal OneDrive from Being Pinned in Explorer

1. Open RegEdit (RegistryEditor): type regedit in the start menu and it should come up (select it)
2. Find the personal OneDrive here: hkey_current_user\software\microsoft\windows\currentversion\explorer\desktop\namespace
3. At the top, where it says Computer paste the following to the right of it (i.e., don't delete Computer):

GLMeece

Latency Comparison Numbers

Note: "Forked" from Latency Numbers Every Programmer Should Know

Event	Nanoseconds	Microseconds	Milliseconds	Comparison
L1 cache reference	0.5	-	-	-
Branch mispredict	5.0	-	-	-
L2 cache reference	7.0	-	-	14x L1 cache
Mutex lock/unlock	25.0	-	-	-

GLMeece

Sphinx Setup for autodoc

Sphinx is a documentation generator that is the de facto standard for Python projects. The official documentation can be a bit daunting as it includes so many options, it's hard to know where to start.

Note: This Gist was updated on 04/04/2019 to accomodate a newer version of Sphinx, as well as Python 3.7. YMMV!

This document is written with the following presuppositions:

• You want to leverage the DocStrings in your Python code.
• You'd rather write your DocStrings in Google-style instead of a more awkward reStructuredText format for calling documentation.

GLMeece

Rule - 0201 [W]: missing-doc-keyword: Missing documentation in '{{ name }}' keyword
Rule - 0202 [W]: missing-doc-test-case: Missing documentation in '{{ name }}' test case
Rule - 0203 [W]: missing-doc-suite: Missing documentation in suite
Rule - 0204 [W]: missing-doc-resource-file: Missing documentation in resource file
Rule - 0301 [W]: not-allowed-char-in-name: Not allowed character '{{ character }}' found in {{ block_name }} name
Rule - 0302 [W]: wrong-case-in-keyword-name: Keyword name '{{ keyword_name }}' does not follow case convention
Rule - 0303 [E]: keyword-name-is-reserved-word: '{{ keyword_name }}' is a reserved keyword{{ error_msg }}
Rule - 0305 [W]: underscore-in-keyword-name: Underscores in keyword name '{{ keyword_name }}' can be replaced with spaces
Rule - 0306 [W]: setting-name-not-in-title-case: Setting name '{{ setting_name }}' should use title or upper case
Rule - 0307 [W]: section-name-invalid: Section name should be in format '{{ section_title_case }}' or '{{ section_upper_case }}'