Well-Used Simple Tools
Monday November 17, 2014
A short talk for Design Thinking DC.
I work with data, and the tools that are unique to what I do may or may not be interesting to you. So I'm going to start with four tools that are useful for everyone.
Tool number one is a keyboard. You use a keyboard a lot, and you should probably use it more.
Steve Yegge has a 2008 blog post about programmers who can't touch type. You wouldn't think such people existed. But just this year, in 2014, I met such a person.
A keyboard is probably the tool you use more than any other. Improve your typing. Then, use keyboard shortcuts so that more things become typing.
Tool number two is a browser. I usually use Chrome. I want to use Firefox more, but the keyboard bindings are broken for switching tabs when you have a YouTube video up.
Often, you don't have to reach for the mouse to use your browser. I'll call out key combinations that work on my Mac; on other systems they're often similar.
tab switches applications.
l gives us the address bar. I'll type in my blog's domain,
f finds in page. I want the post on
esc to leave the search.
return to follow the link.
space to page down a little.
Let's do it again, another way.
t for a new tab. We want to search for
return to search.
tab to start exploring links.
down to get the result we want.
return to follow the link.
left to change tabs.
w to close the tab.
l to get the address bar.
a to go to the beginning of the line.
k to kill the line.
y to yank it back.
f to move forward,
b to move back.
These commands are stock - I'm not using any special accessibility tools. They work not just in the browser but across many different settings. Learn them once, and you can speed up many common operations.
Tool number three is email. Gmail has been getting progressively worse, but it's still the best option. You can turn off some of the bad features, and turn on keyboard shortcuts.
A pass through email should not take a long time. It should be distinct from work, but will integrate with task management.
Move through emails with
k, open an email with
r to reply, and do it immediately if it's a brief request.
[ to archive an email and move to the next one. Some emails don't require a response.
Sometimes an email represents a task, but you can't work on it until some point in the future. This is where task management is useful. I can forward (
f) to a future date like
firstname.lastname@example.org and the task will be tracked in the system, so I won't see it until Thursday.
Tasks that will take longer than two minutes get moved to task management, even if they're for today.
After a pass through email, the inbox should be empty.
Tool number four is Good Todo, which is a calendared to-do list app that integrates with email. It supplements my memory by keeping track of when I need to do things, and lets me focus on just the tasks that I'll be able to accomplish in a given day. It is way better than any other to-do application I've ever seen.
I include brief tasks that just need to be remembered and crossed off, as well as more substantial tasks. By looking at the list for the day I can decide what to work on first and what to reschedule or reconsider.
The Unix philosophy describes a way of building an effective system of tools. To paraphrase Doug McIlroy:
- Use tools that do one thing well.
- Use tools that work together.
- Use tools that work with text, because text is universal.
I think my four simple tools follow this fairly well, but they aren't ideal examples. I'll use a simple task to demonstrate further. 
 For more on this family of tools, see Data Science at the Command Line by Jeroen Janssens.
Right now, I'll work on this "Friday sales report" task. I'll download the Excel file. Then I'll go to the command line.
Step one is getting the data out of Excel format and into text. Luckily there's a package called csvkit, which includes
in2csv, which will make short work of this simple file.
in2csv sales.xlsx > sales.csv
Now that we have text, a whole world of tools are available. I'll take off the header row with
sort the rows, reduce to the unique terms and count occurrences with
uniq, then do another sort to see things in a nice order.
tail +2 sales.csv | sort | uniq -c | sort -rn
Notice the input and output are both text. I could work with this text further.
R to make a quick bar graph.
cat sales.csv | Rio -ge "g+geom_bar(aes(item))" > plot.png
In three lines, I've done fairly much, and I've done it repeatably.
I'm using my command line from inside Emacs, which is a text editor.  I'll take my three lines and make them a script. Now I can repeat what I've done whenever there's new data.
 For more about Emacs, see my Emacs and Python talk.
what are good tools?
Good tools have low or negative cognitive load. They are simple in what they do, and how they do it. They avoid hidden state.
Good tools are pure, in that they are distinct from what they operate on. They don't lock you into a closed format. They are tools, not kits.
Good tools are textual, programmable, repeatable, inspectable, automatable: anything you do once can be examined and repeated later non-interactively.
These are some of my thoughts on tooling, and I'd invite you to consider them. You could also read some of the books that have influenced me.
My thoughts on email and to-do management come directly from Bit Literacy, which you can get for free at bitliteracy.com.
My thoughts on text and separation of concerns, among other things, were certainly influenced by The Pragmatic Programmer.
ReWork, which is largely the same as the freely available Getting Real, has a lot of good ideas for working effectively. "Do everything you can to remove layers of abstraction" is one quote I like.
This is an image from the drafting process for this talk. I've been strongly influenced by the Bard Institute for Writing and Thinking, and paper is my favorite invention. I mention this to emphasize that while I've shown certain kinds of tools, thinking in many different ways is important to everyone and multiple types of process can be useful in supporting various stages of work.
use version control!
The major tool I've omitted is version control. Use git.
And don't use SAS.
Thank you very much!