I was working on a proposal for a talk like “User Experience of Command Line Tools” for O'Reilly’s design conference, but missed the deadline. :(
I’d also like to see more studies of real-world codebases, and the tradeoffs made (stuff like Michael Abrash’s writing, as in http://blogs.valvesoftware.com/abrash/latency-the-sine-qua-non-of-ar-and-vr/). Annotated codebases that I’ve seen are a start, though they’re often not more than just comments on a line-by-line basis, whereas I’m more interested in why it was done that way and what else was tried/discarded.
I haven’t written it up yet (I’ve been mainly in “gathering” mode and wrote just enough for an abstract), wasn’t sure if anyone was interested, but using you as a proxy :), I’ll probably start putting something together. I’ll post it here once I’ve gotten it started.
You should check out the Architecture of Open Source Applications series. There’s a lot of great stuff in there, but I particularly liked the chapter on Warp from volume 3.
Many of these are implementation-specific, which is usually not what Computer Science is about. The first one is okay, but I experienced most of that under a different name (which I now forget, but it was the course that used Scheme or Lisp for its projects).
I was working on a proposal for a talk like “User Experience of Command Line Tools” for O'Reilly’s design conference, but missed the deadline. :(
I’d also like to see more studies of real-world codebases, and the tradeoffs made (stuff like Michael Abrash’s writing, as in http://blogs.valvesoftware.com/abrash/latency-the-sine-qua-non-of-ar-and-vr/). Annotated codebases that I’ve seen are a start, though they’re often not more than just comments on a line-by-line basis, whereas I’m more interested in why it was done that way and what else was tried/discarded.
Have you written about CLI UX anywhere? I would like to subscribe to your newsletter, as this is something I’ve been thinking a lot about lately.
I haven’t written it up yet (I’ve been mainly in “gathering” mode and wrote just enough for an abstract), wasn’t sure if anyone was interested, but using you as a proxy :), I’ll probably start putting something together. I’ll post it here once I’ve gotten it started.
Would love software archaeology courses.
You should check out the Architecture of Open Source Applications series. There’s a lot of great stuff in there, but I particularly liked the chapter on Warp from volume 3.
Many of these are implementation-specific, which is usually not what Computer Science is about. The first one is okay, but I experienced most of that under a different name (which I now forget, but it was the course that used Scheme or Lisp for its projects).
I am 100% going to propose the first (Unlearning OOP) and last (Programmer Obsessions). Not with those names, of course, but the same idea.