cdzombak

# Sample Bear-Things Template
* item a
notes for item A
* item b
* item c
notes for item C
; comments/empty lines begin with `;`
a second line of notes for C

---

cdzombak

#!/usr/bin/env bash
set -u

WHITE='\033[0;37m'
RED='\033[0;31m'
YELLOW='\033[0;33m'
GREEN='\033[0;32m'
NC='\033[0m'

if [ -e "/Volumes/Chris Dzombak's iPhone 11 co.brushedtype.doppler-ios" ] ; then

cdzombak

#!/usr/bin/env bash
set -e

urlencode() {
    # from https://gist.github.com/cdown/1163649
    # urlencode <string>

    old_lc_collate=$LC_COLLATE
    LC_COLLATE=C

cdzombak

#import <Foundation/Foundation.h>

@interface CDZTableViewSplitDelegate : NSObject <UIScrollViewDelegate, UITableViewDelegate>

@property (nonatomic, weak) id<UITableViewDelegate> tvDelegate;
@property (nonatomic, weak) id<UIScrollViewDelegate> svDelegate;

- (id)initWithScrollViewDelegate:(id<UIScrollViewDelegate>)scrollViewDelegate tableViewDelegate:(id<UITableViewDelegate>)tableViewDelegate;

@end

cdzombak

javascript:!function(){var%20e=window.getSelection().toString(),t=document.title.replace(%22%20-%20Jira%22,%22%22),n=e%3Fe:t,o=%22[%22+n+%22](%22+location.href+%22)%22;(function(e){var%20t=document.createElement(%22textarea%22),n=document.getSelection();t.textContent=e,document.body.appendChild(t),n.removeAllRanges(),t.select(),document.execCommand(%22copy%22),n.removeAllRanges(),document.body.removeChild(t)})(o)}();

cdzombak

#!/bin/sh

figlet -f big "$(hostname --fqdn)" | grep -v "^ *$"

cdzombak

collected links on rewriting software (or not)

• Rewrite Code From Scratch has good discussion of reasons to rewrite and reasons not to
• Things You Should Never Do, Part I is the commonly-cited argument from Joel On Software
• Re (tilly) 1: (OT) Rewriting, from scratch, a huge code base has discussion on when rewriting may be a good idea. It seems like there's more conversation in this thread, which I haven't read.
• code quality - When is a BIG Rewrite the answer? - Software Engineering Stack Exchange is a good answer, specifically calling out that the challenges are sometimes organizational rather than technical
• [Repeat yourself, do more than one thing, and... — programming is terrible](https://programmingisterrible.com/post/176

cdzombak

#!/usr/bin/env bash

set -u

NOW=$(date +"%F %T %Z")
OK=
if curl -s https://a2mi.social/api/v1/streaming/health | grep -c OK > /dev/null ; then
	OK="1"
else
	OK="0"

cdzombak

property droppedContext : "Dropped"

tell application "OmniFocus"
	tell front document
		try
			set theDroppedContextID to id of item 1 of (complete droppedContext as context)
			set theDroppedContext to first flattened context whose id is theDroppedContextID
		on error
			display alert "No context found whose name contains “" & droppedContext & "”"
			return

cdzombak

it makes sense, and I suspect you’d see something similar on any device with a worn battery (edited)

basically everything battery powered changes clock speeds based on battery voltage level and whether you’re plugged in (_edit:_ also based on workload, so you’re not running at full speed and burning battery power when you’re not doing anything) (edited)

you can’t run a CPU at full speed when the battery voltage is low (edited)

so it follows that when the battery is worn out (and its top voltage is presumably lower), performance is consistently lower

the phone knows about battery age/wear, and takes that into account for the user-facing battery percentage meter