Andrew McKnight armcknight

Run via:

irm "https://gist.githubusercontent.com/caccialdo/d26e89e9eb7b697811c4207e856d8d45/raw/win-iso-splitter.ps1" | iex

Notes from the Mystery Machine Bus

I've spent the past eight years (starting back in June 2004) writing elaborate rants about a bunch of vaguely related software engineering issues.

I was doing all that ranting because I've been genuinely perplexed by a set of "bizarre" world-views held dear by -- as far as I can tell -- about half of all programmers I encounter, whether online or in person.

Last week, after nearly a decade of hurling myself against this problem, I've finally figured it out. I know exactly what's been bothering me.

In today's essay I'm going to present you with a new conceptual framework for thinking about software engineering. This set of ideas I present will be completely obvious to you. You will probably slap yourself for not having thought of it yourself. Or you might slap the person next to you. In fact you probably have thought of it yourself, because it is so blindingly obvious.

Answer by Jim Dennis on Stack Overflow question http://stackoverflow.com/questions/1218390/what-is-your-most-productive-shortcut-with-vim/1220118#1220118

Your problem with Vim is that you don't grok vi.

You mention cutting with yy and complain that you almost never want to cut whole lines. In fact programmers, editing source code, very often want to work on whole lines, ranges of lines and blocks of code. However, yy is only one of many way to yank text into the anonymous copy buffer (or "register" as it's called in vi).

The "Zen" of vi is that you're speaking a language. The initial y is a verb. The statement yy is a simple statement which is, essentially, an abbreviation for 0 y$:

0 go to the beginning of this line. y yank from here (up to where?)

	// =============================================================================
	// XNU kperf/kpc demo
	// Available for 64-bit Intel/Apple Silicon, macOS/iOS, with root privileges
	//
	//
	// Demo 1 (profile a function in current thread):
	// 1. Open directory '/usr/share/kpep/', find your CPU PMC database.
	// M1 (Pro/Max/Ultra): /usr/share/kpep/a14.plist
	// M2 (Pro/Max): /usr/share/kpep/a15.plist
	// M3: /usr/share/kpep/as1.plist

	# A Best in Class Checklist
	A boiled down checklist adapted from this [post](https://www.swiftjectivec.com/a-best-in-class-app/), created by @jordanmorgan10.

	> To use this, create a Github Issue in your own repo, and simply copy and paste this text.

	## iOS Core Technology
	_Things any iOS app can benefit from_

	- [ ] iCloud Sync
	- [ ] Focus Filter Support

	// ninjaVanish hides from webdriver/headless browser detection
	//
	// Focused specifically on HeadlessChrome / Puppeteer.
	// When using Puppeteer this should be instrumented with the
	// `Page.evaluateOnNewDocument()` method which injects our code
	// after the document loads but before any scripts run
	//
	// Techniques leveraged are:
	// - Removes "Headless" from User-Agent
	// - Deletes `navigator.webdriver` to mimick standard navigator object properties

	#!/bin/bash
	#
	# Open the specified file on GitHub. It will use the master branch by default:
	#
	# repo -f app/controllers/application_controller.rb
	#
	# Specify a different branch:
	#
	# repo -b another-branch -f app/controllers/application_controller.rb

	i386 : iPhone Simulator
	x86_64 : iPhone Simulator
	arm64 : iPhone Simulator
	iPhone1,1 : iPhone
	iPhone1,2 : iPhone 3G
	iPhone2,1 : iPhone 3GS
	iPhone3,1 : iPhone 4
	iPhone3,2 : iPhone 4 GSM Rev A
	iPhone3,3 : iPhone 4 CDMA
	iPhone4,1 : iPhone 4S

	osascript -e 'tell application "iOS Simulator" to quit'
	osascript -e 'tell application "Simulator" to quit'
	xcrun simctl erase all