Friday 7th August, 2015
Week 342 - Interesting links
This section of the manual and its associated Hackpad wiki looks as if it contains a wealth of useful material about user interface design, much of which is probably relevant to our work on Smart Answers. — JM
I found David McKee’s write-up of a spreadsheet conference (!) really interesting:
The conference reminded me particularly of one simple fact about spreadsheets that often gets ignored: Spreadsheets are code
On a related note, this paper suggests that if you track the copying & pasting of formulae in a spreadsheet and then propogate edits to any of the copies to all the other copies, you can introduce better abstraction into a spreadsheet without complicating the user experience. — JM
Apparently fast, non-volatile memory is likely to be available in the not too distant future. This article talks about what implications that might have on how we design software applications. — JM
git worktree command looks interesting. In our work with Smart Answers, I’ve occassionally found myself creating a second working copy of the repository in order to run some tests while continuing to work in the original copy. It sounds like the
git worktree command would simplify this process slightly. — CR
This looks kinda interesting, from the folks at Delicious.
From the FAQ:
The Dmail chrome extension encrypts your message locally on your computer. The encrypted body of the message is sent to Dmail’s servers, while the decryption key and a link are sent to the intended recipients through Gmail. Neither Dmail nor Gmail gets both the encrypted message and the decryption key, so only the sender and intended recipients can read the message legibly.
The Delicious blog post explains that the product was born out of their “own personal experience sending and trying to protect sensitive information via email”. I think it’s great when things are born out of frustration/necessity and am interested in seeing whether this takes off.
I can imagine this coming in handy if you’re trying to find a slightly quieter time to visit a popular attraction.
The blog post suggests that the data comes from people that have activated Location History on their mobile device. While the data is being used here to provide a useful service, I can also imagine certain groups being interested in using the data to spot suspicious patterns of activity in non-touristy places. — CR