1. Temporarily enclose your ~/.zshrc file with benchmark instructions:

zmodload zsh/zprof
...
zprof

Most pager applications, including more, less, ov, and eless, corrupt hard tabs to spaces. Consequently, they may break common copy & paste workflows for Go, make, and other indentation sensitive languages.

Some alternatives exist.

Configure an environment variable PAGER=<command> with the desired pager command. Many applications, such as git, invoke pagers this way.

When registering URI handlers, Brave's configuration system often corrupts. Various hyperlinks may misbehave.

To fix this horrid computer state, pop open the hood and ensure that the pipes are fully connected to the right parts:

1. Navigate to brave://settings/handlers.
2. Set the desired platforms as the default handlers, such as Proton Mail for email mailto URI's.

Command + Shift + P, Chat: Hide AI Features, Return

Control + Shift + P, Chat: Hide AI Features, Enter

Navigate to Settings -> Accessibility -> Touch and set Reachability to off. Now your iPhone will stop randomly yanking the entire screen halfway down the device when using various gestures in the vicinity of the bottom of the screen.

1. Write an ffmpeg input configuration file list.txt of the form:

file '<input-1>'
file '<input-2>'
file '<input-3>'
...

Apple does not make it easy to very rapidly toggle between the two F1 - F12 vs. Brightness - Volume Up keyboard modes.

Fortunately, this can be automated via the Shortcuts scripting system.

Run Shell Script

defaults write -g com.apple.keyboard.fnState -int $(( ! "$(defaults read -g com.apple.keyboard.fnState -int)" ))

macOS' SMB implementation is buggy, corrupting images when viewed with Preview.app.

As a workaround, select a different protocol, such as NFS.

The gold standard of software testing is formal verification, a mathematical proof that a body of code cannot fail with unspecified behavior. However, in practice formal verification proceeds at a slower pace than many teams prefer to operate. Fortunately, we have a productive compromise: Fuzzing.

Fuzzing significantly raises the quality bar of software components, closing subtle testing gaps that other approaches neglect to address. For example, validation, a handful of manual tests, and code coverage will still leave latent bugs in very many codebases. This is because the input/state space is many orders of magnitude larger than the number of lines of code, and scale exponentially with the bit width and number of variables.

Fuzzing is able to identify these kinds of bugs, by generating random test cases to more comprehensively evaluate the input and/or state space. Code coverage won't tell you when you have a division by zero bug, or a nil pointer bug, or an empty array