ELLIOTTCABLE

HI! I've got some feedback I'd like to provide, but you guys don't seem to have a Twitter account that I can find.

First, your website:

Add a link to your Twitter account.
If you don't have a Twitter account, get a Twitter account. :P

Onwards to the meat; your app:

When entering ‘typewriter mode’ with a document already open, the visible position in the document won't immediately follow your cursor; this starts working after you start typing. It's possible to get your editing cursor (confusingly) stuck at the bottom of the document, invisible, while your viewpoint is locked to the top of the document.
The ‘width’ settings for Fullscreen should refer to the same width regardless of the size of the screen. They should be defined in columns-of-characters (or approximations thereof), instead of in the screen-size. (The [accepted practice][1], backed by the science of how humans read text, is around ~2.5 alphabets-per-line, or ~65 of the lowercase letter ‘m’.) I suggest, perhaps, 45em, 65em, a

Development log (slash wiki)

I want to be able to write the kind of raw-thought, chronological, Markdown entries that I already do, and have them be public and logged. Basically, tumblogging/microblogging for projects instead of people.

Git backed
- Each change is a commit
- No commit messages or any of that crap. Simple as possible.
- Can be configured to commit to a branch of an existing repository (think ditz or GitHub Pages)

Cascading responsibility

At the moment, more than one Exec can be responsible for a given Thing. This is bad:

Responsibility represents the ability to sequentially read from a data-structure without interruption, or modify a data-structure without interrupting somebody else's sequential-read.
Given-responsibility thus represents blessing another modifier (or reader) by saying “their process is a sub-step in my own process,” or, effectively, “I expect them to modify the thing I've said not to modify.”
Currently, however, this doesn't protect at all against you, and your subjects, from interleaving in unintended ways: just because you want to give a step exclusive permission to complete without giving up your ability to exclude other processes permission, doesn't mean you want that sub

Reservations (or not)

May 5, 2015

Should reservations be ‘visible’ libside? (i.e. first-class, and differentiable from holding the unspecific Execution; or should they be simply an invisible property of Executions)
So, I'm back to thinking there's no need for reservations, and I can just do everything with ownership. But I'm running into some issues:

Reservations (or not)

Should reservations be ‘visible’ libside? (i.e. first-class, and differentiable from holding the unspecific Execution; or should they be simply an invisible property of Executions)
So, I'm back to thinking there's no need for reservations, and I can just do everything with ownership. But I'm running into some issues:
- There would have to be some sort of semantic handling of syntactic indirection (ew); because foo[] [bar[] [baz]] and such would need to work … that is, foo having ownership of

I need to network with more women developers and makers in Chicago.

Hit me up with the most talented you know!

Met so far:

@melissapierce, who runs @CWDEVs, a Chicago dev-meetup for technical women

	#!/usr/bin/env sh

	netrc="${NETRC:-$HOME/.netrc}"
	subdomain="${HARVEST_SUBDOMAIN:-elliottcable}"

	if [ -f "$netrc" ] && [ ! -d "$netrc" ]; then

	fraction="$(
	curl -s --netrc-file "$netrc" \
	-H 'Content-Type: application/json' -H 'Accept: application/json' \

	Non-Linear Paws
	===============

	In the original Paws design, control-flow was basically a library function. You'd call into
	routines that would provide control-flw primitives. I want to try a Paws that makes control-flow
	explicit within your code; that makes it a first-class citizen.

	I'm concerned on what this does for code-coherence and programmer intuition; I'm not sure complex
	control-flow graphs encoded directly are going to result in comprehendable code. >,>

	fastboot oem unlock
	tar -xzvf nakasi-jdq39-factory-*.tgz
	cd nakasi-jdq39-factory-*
	./flash-all.sh

	fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img

	adb sideload cm-10.1.3-grouper.zip
	adb sideload gapps-jb-20130812-signed.zip

	set -g set-remain-on-exit on

	new-window -n '2961' 'bfgminer -c 3255.bfgminer.conf'
	new-window -n '3255' 'bfgminer -c 3255.bfgminer.conf'