in 1997, Professor Brian Harvey of UC Berkeley published a three-volume set of books that approached teaching computer science via the #Logo #programming language.
That three-volume set is out of print and costs almost a hundred bucks if you can find a paperback copy.
Professor Harvey, however, has supplied copies of all three volumes on his website for personal use, which has been lovingly archived by the Internet Archive.
Volume 1 starts here: https://web.archive.org/web/20130707051345/http://www.cs.berkeley.edu/~bh/v1-toc2.html
(the original site is still online and available at https://people.eecs.berkeley.edu/~bh/v1-toc2.html if you prefer)
re: why logo? (long, quote)
@djsundog Hmm. I wonder if anyone has a Logo interpreter for the Lego RCX?
No. I will not get my Legos out of storage. I will not. I will not. (Where would I put them?)
why logo? (long, quote)
@djsundog Seymour Papert &c's long paper Mindstorms was where icve most recently got some good Logo shilling. he compares to basic. it was a fun read for me. Bret Victor seems to be hosting a download,
http://worrydream.com/refs/Papert%20-%20Mindstorms%201st%20ed.pdf
one of the things that really clicks about Logo to me is that the turtle is an embodied agent. other whole environment starts with a xreal" thing on the screen & to program is to consider yourself from the things perspective & to engage & act upon the world about the turtle-self. trying to think of machines & programs as embodied agents, as actors, is a huge leap over how imperative language leaves us thinking foremost about algorithms & number crunching, abstract forms of computing. the real meat of computing happens on a higher plane & getting the operator in touch with, thinking on a much more material plane of different agents, & what options they have, & how they can interact... that's the real, that's material, that's what systems should strive to surface.
why logo? (long, quote)
from the preface: