What do you think?
Rate this book
10 PRINT CHR$(205.5+RND(1)); : GOTO 10
A single line of code offers a way to understand the cultural context of computing.
This book takes a single line of code—the extremely concise BASIC program for the Commodore 64 inscribed in the title—and uses it as a lens through which to consider the phenomenon of creative computing and the way computer programs exist in culture. The authors of this collaboratively written book treat code not as merely functional but as a text—in the case of 10 PRINT, a text that appeared in many different printed sources—that yields a story about its making, its purpose, its assumptions, and more. They consider randomness and regularity in computing and art, the maze in culture, the popular BASIC programming language, and the highly influential Commodore 64 computer.
This book takes a single line of code—the extremely concise BASIC program for the Commodore 64 inscribed in the title—and uses it as a lens through which to consider the phenomenon of creative computing and the way computer programs exist in culture. The authors of this collaboratively written book treat code not as merely functional but as a text—in the case of 10 PRINT, a text that appeared in many different printed sources—that yields a story about its making, its purpose, its assumptions, and more. They consider randomness and regularity in computing and art, the maze in culture, the popular BASIC programming language, and the highly influential Commodore 64 computer.
309 pages, Hardcover
First published November 2, 2012
40 people are currently reading
496 people want to read
About the author
Nick Montfort
15 books38 followersNick Montfort is Professor of Digital Media at MIT. He is the author of Twisty Little Passages: An Approach to Interactive Fiction and Exploratory Programming for the Arts and Humanities; the coauthor of Racing the Beam: The Atari Video Computer System and 10 PRINT CHR$(205.5+RND(1)); : GOTO 10; and the coeditor of The New Media Reader (all published by the MIT Press).
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 30 of 35 reviews
April 4, 2013
Although team-writing an entire book about a BASIC one-liner is a clever conceit, the results I found to be highly patchy. There was some interesting history of the C64 and of BASIC, and some amusing bits of 30-year-old assembly code, but there was also way too much pointless riffing and capital-t Theory about What It All Means. Mildly recommended to those of us of a certain age who grew up programming on the first generation of home computers.
October 27, 2022
This is an entire book about one line of code! It is a famous line of code, but that's still crazy. Too much of a woman to understand the really technical stuff but I did admittedly find it interesting. One of the more accessibly written books I've read in this vms vein of like, cultural software. Chapter about the religious and cultural history of mazes was the best part. Also enjoyed all the pictures of Atari VCS ports.
“As with a rosary and the Stations of the Cross, the Christian labyrinth is unicursal. None included dead ends or choice points until the fifteenth century, when multicursal aberrations appeared, as Helmut Birkhan explains, as a “symptom of the secularization of the labyrinth idea” (quoted in Kern 2000, 146). With this secular turn, the maze becomes a space of leisure as well as ritual, and is lined with hedges, marked by rocks, and surrounded by grooves.”
“Because BASIC was a hit at a unique time in the history of computing—when microcomputers were becoming mainstream but before executable software distribution became widespread—there may never be another language quite like it.”
“The pattern therefore consists of multiple, intertwined unicursal mazes; once embarked on a particular path from edge to edge, there are no choices to make. A 10 PRINT maze might be considered multicursal if there is a choice of where to enter the maze from one of the outside “openings,” but once such a choice is made, the path will lead irrevocably to its paired entrance or exit.”
“Behind the ordinary features of a program—a call to produce random numbers, a printing mechanism, a repeating loop—lie ghostly associations with distant and forgotten forms of cultural activity and production whose voices echo from somewhere inside the labyrinth of material history accumulated in a particular technology.”
“In the case of 10 PRINT, the program’s mazelike output is not a neutral pattern, but one wrapped up in numerous contradictory Western ideas about the notion of a maze.”
“As with a rosary and the Stations of the Cross, the Christian labyrinth is unicursal. None included dead ends or choice points until the fifteenth century, when multicursal aberrations appeared, as Helmut Birkhan explains, as a “symptom of the secularization of the labyrinth idea” (quoted in Kern 2000, 146). With this secular turn, the maze becomes a space of leisure as well as ritual, and is lined with hedges, marked by rocks, and surrounded by grooves.”
“Because BASIC was a hit at a unique time in the history of computing—when microcomputers were becoming mainstream but before executable software distribution became widespread—there may never be another language quite like it.”
“The pattern therefore consists of multiple, intertwined unicursal mazes; once embarked on a particular path from edge to edge, there are no choices to make. A 10 PRINT maze might be considered multicursal if there is a choice of where to enter the maze from one of the outside “openings,” but once such a choice is made, the path will lead irrevocably to its paired entrance or exit.”
“Behind the ordinary features of a program—a call to produce random numbers, a printing mechanism, a repeating loop—lie ghostly associations with distant and forgotten forms of cultural activity and production whose voices echo from somewhere inside the labyrinth of material history accumulated in a particular technology.”
“In the case of 10 PRINT, the program’s mazelike output is not a neutral pattern, but one wrapped up in numerous contradictory Western ideas about the notion of a maze.”
December 29, 2012
I've been reading a lot of Nick Montfort and Ian Bogost books recently, since no one can so unapologetically justify 8-bit geek nostalgia like academia can. :-) And as a grown man who has a nearly unhealthy love for all things Commodore 64, I had to pick up this book. It's a 300 page exercise in deconstruction, focusing on a single line of C64 BASIC code (the very title of the book) that prints a random maze. In these details "lie ghostly associations with distant and forgotten forms of cultural activity and production whose voices echo from somewhere inside the labyrinth of material history accumulated in a particular technology." The book ties the elements of the deconstruction back to well-trodden anecdotes and back stories (often better covered in other books).
A Commodore 64 was very different than an Apple ][ or an Atari 800. Interacting with a computer back in the 80s meant knowing how to exploit many platform specific details. Given these machine specifics, a given programmatic approach would usually go with the grain of one system, but against the grain of another. I did enjoy seeing the difficulty of porting the one line BASIC program to the Atari 2600, which by the end, provided a "more revealing comparison that does simply lining up the technical specs of the two systems for side-by-side comparison". Another reader has shown how bloated the Java equivalent of the program could become: http://preview.tinyurl.com/cz3n54s
A Commodore 64 was very different than an Apple ][ or an Atari 800. Interacting with a computer back in the 80s meant knowing how to exploit many platform specific details. Given these machine specifics, a given programmatic approach would usually go with the grain of one system, but against the grain of another. I did enjoy seeing the difficulty of porting the one line BASIC program to the Atari 2600, which by the end, provided a "more revealing comparison that does simply lining up the technical specs of the two systems for side-by-side comparison". Another reader has shown how bloated the Java equivalent of the program could become: http://preview.tinyurl.com/cz3n54s
April 5, 2015
Deconstruction of a single line maze generation program in Commodore 64 Basic. A ten author collaboration that is mostly interesting. The discussions of what makes a maze and diversions into textiles were not terribly interesting; the deconstruction of an assembly version of the same code was fascinating. Comprehensive list of sources, plenty of relevant illustrations. Would mostly be a good book to base an intro to programming course on.
January 8, 2014
The first 50% or so of this book is super-pretentious, annoying artsy yammering. The second half is a wonderful little technical romp, especially if you have some experience programming asm. Definitely worth speeding through the smelly half to dive into the fun.
May 31, 2017
Another one of the geekiest books I've ever read.
You'd never believe a loosely organized set of essays inspired by a one-line BASIC program for the Commodore 64 computer in the early 80s would work as a book, but it kind of does.
Lots of good little tidbits about the history of programming, the Commodore 64 architecture itself, BASIC programming, the golden age of the personal computer, and even the mathematical topology and semiotic significance of mazes. No one topic goes on for too long, and then it's off to the next one.
The whole thing brought back lots of great nostalgic memories of typing in cryptic BASIC programs from computer magazines and seeing what happened. Everyone back in the day knew that the weird short cryptic programs, like "10 PRINT CHR$(205.5+RND(1)); GOTO 10", were always the most rewarding ones.
You'd never believe a loosely organized set of essays inspired by a one-line BASIC program for the Commodore 64 computer in the early 80s would work as a book, but it kind of does.
Lots of good little tidbits about the history of programming, the Commodore 64 architecture itself, BASIC programming, the golden age of the personal computer, and even the mathematical topology and semiotic significance of mazes. No one topic goes on for too long, and then it's off to the next one.
The whole thing brought back lots of great nostalgic memories of typing in cryptic BASIC programs from computer magazines and seeing what happened. Everyone back in the day knew that the weird short cryptic programs, like "10 PRINT CHR$(205.5+RND(1)); GOTO 10", were always the most rewarding ones.
April 11, 2020
I really wanted to like this book. I'm a child of the Commodore era, and first learned to program on a Pet, followed by a Vic-20, and then a Commodore 64.
I found it largely a work of tedious navel gazing and mental masturbation. A mish-mash of ideas with no coherent overarching structure or narrative. There are a lot of asides on computer and programming history, and while I generally enjoying reading that sort of thing, somehow they manage to leach some of the pleasure of out of those anecdotes too.
Maybe some of this is the result of 10 authors without a strong editor, or maybe this is the book they all wanted to produce. A much more enjoyable, and shorter, book could have been produced from this material, but in this form I would discourage any of my friends from reading this, and that's really why I'm writing this review: life it too short.
I found it largely a work of tedious navel gazing and mental masturbation. A mish-mash of ideas with no coherent overarching structure or narrative. There are a lot of asides on computer and programming history, and while I generally enjoying reading that sort of thing, somehow they manage to leach some of the pleasure of out of those anecdotes too.
Maybe some of this is the result of 10 authors without a strong editor, or maybe this is the book they all wanted to produce. A much more enjoyable, and shorter, book could have been produced from this material, but in this form I would discourage any of my friends from reading this, and that's really why I'm writing this review: life it too short.
May 17, 2023
While I can certainly understand some reviewers saying this book can be a bit of a navel-gazing exercise, it sure can be relaxing to do so from time to time, and even informative, especially if one is indulging in the warm glow of nostalgia, and reflecting on what in reality actually was a simpler time: home computers of this era, their interfaces, and what they could do, were in fact much simpler, but this very simplicity encouraged a mindset of experimentation of learning that isn't present in computers of today. Just wistfully remembering the past is not really the goal of the book however, and I did find it interesting to use a simple maze-generator program as a gateway to discussions about randomness and art in addition to programming. Not really recommended unless you subscribe to a bunch of retrocomputing YouTube channels like I do, but enjoyable nonetheless.
March 13, 2018
A great overview of the way computers intersect with art, with play, with creativity, with research, and lots of other angles on it; a good example of the amount there is to look at about any subject when placing it in its context, demonstrated by picking an extremely small computer program as this stone soup's jumping off point. Occasionally a little dry in places, but full of so many interesting interconnections with the wider world, you'll probably find yourself with plenty of open tabs to follow further along on some of the threads it uncovers.
December 18, 2017
In case you ever wondered, this book demonstrates that a single line BASIC program for a Commodore 64 can provoke an entire book about computers, culture, and context.
Ten academics review a single line of code and take it on tangents about programming, art, culture, history, psychology, math, design, and more. Reading this book took me on a delightful walk down memory lane that has provoked further reading.
Ten academics review a single line of code and take it on tangents about programming, art, culture, history, psychology, math, design, and more. Reading this book took me on a delightful walk down memory lane that has provoked further reading.
August 14, 2021
Too stupid to understand parts but overall very cool
October 17, 2021
I understood some of this but only because I asked my dad like 500 questions
June 11, 2024
Wow!
I did not expect this level of detail in the analysis of a simple one liner of code.
Read hours 8.86
I did not expect this level of detail in the analysis of a simple one liner of code.
Read hours 8.86
June 1, 2025
The hermeneutics and semiotics of a single line of code. For someone who grew up working on the hex editor on the C64 then getting and undergrad philosophy degree, this book is just awesome!
May 18, 2013
10 Print reads very much like an academic tome. The book opens, "Computer programs process and display critical data, facilitate communication, monitor and report on sensor networks, and shoot down incoming missiles." Outside of academia it's pretty hard to find someone using "facilitates" out in the wild. I should know, I'm pretty sure I have an academic paper out there with one of two "facilitates". Many of the words, phrases and descriptions were boilerplate academia. To me they created a complex layer of nostalgia. First, I was reminded of my experiences in grad school. Second, I recalled my adventures exploring and manipulating my own early BASIC programs. Third, and finally, I remember the joy of playing games on the early Commodore 64 computer.
10 Print takes a single line of code and explores computing and art, the concept of mazes in culture, the impact of the BASIC programming language, and the legacy of the influential Commodore 64 computer. To a large extent it succeeds. When entered into the command line of a Commodore 64, the title of this book generates a complex maze-like image until the program is cancelled by the user. Each chapter looks at a specific aspect associated with this program. For example, there is a chapter devoted to mazes, one to regularity, another to randomness, one specifically to BASIC, one to ports, etc. While it is obvious each of the authors contributed to individual chapters, the editors did a good job of tying the project together into a cohesive work.
I would recommend this book to anyone who grew up in the Commodore 64 era and shares a passion for computing. It will certainly make you appreciate the quick one-liners you whip up to help facilitate any complex computer task.
10 Print takes a single line of code and explores computing and art, the concept of mazes in culture, the impact of the BASIC programming language, and the legacy of the influential Commodore 64 computer. To a large extent it succeeds. When entered into the command line of a Commodore 64, the title of this book generates a complex maze-like image until the program is cancelled by the user. Each chapter looks at a specific aspect associated with this program. For example, there is a chapter devoted to mazes, one to regularity, another to randomness, one specifically to BASIC, one to ports, etc. While it is obvious each of the authors contributed to individual chapters, the editors did a good job of tying the project together into a cohesive work.
I would recommend this book to anyone who grew up in the Commodore 64 era and shares a passion for computing. It will certainly make you appreciate the quick one-liners you whip up to help facilitate any complex computer task.
April 25, 2013
As a kid in elementary school, I learned to program in BASIC. I never became an advanced programmer, but BASIC helped me grasp the fundamentals and logic of making a computer actually do something that you want it to do. The subject of this book is a one-line BASIC program that was written for the Commodore 64 and popularized in "type it yourself" instructions in manuals and magazine features. The program draws a never-ending, pseudo-random maze on the screen. That's all it does.
The authors use the program as a text, upon which they perform critical analysis. They intend this analysis to be a model for how other computer code can be analyzed in the future. As a model analysis, they go in all sorts of directions, from a look at mazes and their cultural significance, to what this particular code says about the hardware it was written for, the computing culture it came from, and the nature and history of randomness in computing.
If your eyes are glazing over, this book is not for you. If you are a programmer who likes delving into the academic side of things, or someone who remembers fondly the days of tooling around with BASIC programs on any platform, then you'll probably enjoy this book.
I found some sections more interesting than others, and the book as a whole does suffer from its purpose as an example of code analysis. As a whole, it doesn't feel particularly cohesive, since as I said, the analysis goes off in many different directions, some of which feel a little "so what"-ish.
I'm glad I read this. Maybe you will be, too. You know who you are!
The authors use the program as a text, upon which they perform critical analysis. They intend this analysis to be a model for how other computer code can be analyzed in the future. As a model analysis, they go in all sorts of directions, from a look at mazes and their cultural significance, to what this particular code says about the hardware it was written for, the computing culture it came from, and the nature and history of randomness in computing.
If your eyes are glazing over, this book is not for you. If you are a programmer who likes delving into the academic side of things, or someone who remembers fondly the days of tooling around with BASIC programs on any platform, then you'll probably enjoy this book.
I found some sections more interesting than others, and the book as a whole does suffer from its purpose as an example of code analysis. As a whole, it doesn't feel particularly cohesive, since as I said, the analysis goes off in many different directions, some of which feel a little "so what"-ish.
I'm glad I read this. Maybe you will be, too. You know who you are!
November 16, 2022
10 PRINT -kirjan nimi on kokonainen tietokoneohjelma. Kun sen suorittaa Commodore 64 -tietokoneella, tuloksena on ikuisesti näytöllä vierivä sokkelomainen kuvio. Tästä yhden rivin tietokoneohjelmasta on saatu aikaiseksi kokonainen kirja: hieno suoritus.
Toki kirjassa on muutakin. Kirja käsittelee sokkeloita, säännönmukaisuutta, sattumanvaraisuutta, BASIC-ohjelmointikielen historiaa ja Commodore 64 -tietokonetta. Itse ohjelmasta esitellään erilaisia muunnelmia, jatkoksia ja portataan se eli muunnetaan toimivaksi Atari 2600 -pelikonsolilla. Aivan erilailla toimiva laite tuo mielenkiintoisia haasteita.
Itse Commodore 64:n BASICilla ohjelmointiuraa aloitelleena 10 PRINT kolahtaa monin paikoin vahvasti, mutta luulen, että vielä enemmän kirjasta saa irti sellainen, joka ei aihetta juuri tunne. Asioita käsitellään sen verran rautalangasta vääntäen, että aikaisempaa ymmärrystä ei tarvita.
Miinuspuolelle kirjattakoon akateemisen kirjan vähän väkinäinenkin taipumus vetää kaikesta suuria teorioita. Minun makuuni kirja olisi saanut liikkua hieman enemmän konkreettisemmalla tasolla. Historiaa olisin lukenut enemmänkin, taiteen teoriaa taas vähemmän.
Esimerkki 10 PRINT -ohjelman suorituksesta löytyy Youtubesta. Itse kirjan voi paitsi ostaa kaupasta, myös ladata kirjan nettisivuilta ilmaiseksi. (14.3.2013)
Toki kirjassa on muutakin. Kirja käsittelee sokkeloita, säännönmukaisuutta, sattumanvaraisuutta, BASIC-ohjelmointikielen historiaa ja Commodore 64 -tietokonetta. Itse ohjelmasta esitellään erilaisia muunnelmia, jatkoksia ja portataan se eli muunnetaan toimivaksi Atari 2600 -pelikonsolilla. Aivan erilailla toimiva laite tuo mielenkiintoisia haasteita.
Itse Commodore 64:n BASICilla ohjelmointiuraa aloitelleena 10 PRINT kolahtaa monin paikoin vahvasti, mutta luulen, että vielä enemmän kirjasta saa irti sellainen, joka ei aihetta juuri tunne. Asioita käsitellään sen verran rautalangasta vääntäen, että aikaisempaa ymmärrystä ei tarvita.
Miinuspuolelle kirjattakoon akateemisen kirjan vähän väkinäinenkin taipumus vetää kaikesta suuria teorioita. Minun makuuni kirja olisi saanut liikkua hieman enemmän konkreettisemmalla tasolla. Historiaa olisin lukenut enemmänkin, taiteen teoriaa taas vähemmän.
Esimerkki 10 PRINT -ohjelman suorituksesta löytyy Youtubesta. Itse kirjan voi paitsi ostaa kaupasta, myös ladata kirjan nettisivuilta ilmaiseksi. (14.3.2013)
December 4, 2013
A wide-ranging rumination on the history of art, culture, and personal computing, using a one-line BASIC program as a hub from which many spokes of inquiry extend. It's nearly exhaustive, yet energizing.
I have two quibbles:
Some of the links from the BASIC program to a related topic of discussion seem a bit too tenuous, and some of the discussion feels a bit too descriptive or catalogical without having a clear point to make. I suppose you could say this is a metaphor for the output of the program (or vice versa).
The pretense is of 10 writers collaboratively writing and revising a single cohesive text, but sometimes it doesn't quite cohere: sometimes the same point seems to be made in multiple chapters in slightly different ways, and some passages don't quite fit the flow of the surrounding text but seem to have been kind of shoehorned in for lack of a better place to put them.
The quibbles are both pretty minor, though, and subjective. They don't detract from the value of this book a persuasive argument for taking a critical approach to computer programs as texts and cultural artifacts, even at the microscopic level of a single line of code.
I have two quibbles:
Some of the links from the BASIC program to a related topic of discussion seem a bit too tenuous, and some of the discussion feels a bit too descriptive or catalogical without having a clear point to make. I suppose you could say this is a metaphor for the output of the program (or vice versa).
The pretense is of 10 writers collaboratively writing and revising a single cohesive text, but sometimes it doesn't quite cohere: sometimes the same point seems to be made in multiple chapters in slightly different ways, and some passages don't quite fit the flow of the surrounding text but seem to have been kind of shoehorned in for lack of a better place to put them.
The quibbles are both pretty minor, though, and subjective. They don't detract from the value of this book a persuasive argument for taking a critical approach to computer programs as texts and cultural artifacts, even at the microscopic level of a single line of code.
September 16, 2015
Ah, uh, it took me 19 months to finish this book. But it's really good! It's a 300-ish page book about a one-line program, and it covers it from all kinds of angles. There are chapters that dive into the cultural history and significance of the labyrinth, then some that move on to early efforts with randomness/computation in art, the significance of the grid in modern art and its relation to textiles and computing, all kinds of stuff. There's some scary-looking assembly bits toward the end, but even the code that gets used for discussion is broken down very concisely.
For me this primarily was about computing in the early '80s when the Commodore 64 (the computer of primary interest in this book for a variety of reasons) was popular. It kind of touched on the cultural context that existed at the time, and the kind of computing goals that BASIC embodied that I think in many ways are echoed today in movements to make creative computing tools more accessible (e.g., Twine).
The book is available for free in PDF form on 10print.org, but the hardcover from MIT Press is also suuuuper beautiful if you're a person who finds books beautiful.
For me this primarily was about computing in the early '80s when the Commodore 64 (the computer of primary interest in this book for a variety of reasons) was popular. It kind of touched on the cultural context that existed at the time, and the kind of computing goals that BASIC embodied that I think in many ways are echoed today in movements to make creative computing tools more accessible (e.g., Twine).
The book is available for free in PDF form on 10print.org, but the hardcover from MIT Press is also suuuuper beautiful if you're a person who finds books beautiful.
November 16, 2015
10PRINT is a different kind of computer science noel, it manages to fill its length by dissecting the single line of code that makes up its title. Tickled by the novelty of this approach, I decided to read it.
It covers a very eclectic range of interpretations of the title, opening with a straightforward description of the program's output and its literal interpretations. It moves on to higher computer science aspects such as pedagogy and porting. Outside of computer science, it touches on its artistic meaning and the social aspect of learning.
At times it goes too far in its comparisons and correlations (as all works do), which makes for a pretty boring or incredulous read, but overall is an interesting read, with many valid takes on a very simple statement. You need not be a programming whiz to read this book, just a fledgling interest in the subject - maybe it'll open up a new interpretation of the field for you.
It covers a very eclectic range of interpretations of the title, opening with a straightforward description of the program's output and its literal interpretations. It moves on to higher computer science aspects such as pedagogy and porting. Outside of computer science, it touches on its artistic meaning and the social aspect of learning.
At times it goes too far in its comparisons and correlations (as all works do), which makes for a pretty boring or incredulous read, but overall is an interesting read, with many valid takes on a very simple statement. You need not be a programming whiz to read this book, just a fledgling interest in the subject - maybe it'll open up a new interpretation of the field for you.
February 9, 2013
Amazing in-depth look at a single line of code within its historical, cultural, and technical context. The book touches on the history of the C64 and the surrounding era of home computing, the aesthetics of emergent patterns and randomness, and the details of the C64 that made the program possible. The book managed to hit my love of generative art, my weak spot for cultural analysis of technical topics, and nostalgia for computing in my childhood. The only part of the book that felt clumsy was the chapter on the cultural significance of the maze, which was relevant but felt like it was stretching a bit too far sometimes (even for a book this unusual).
Overall, out of five I give this an Awesome.
Overall, out of five I give this an Awesome.
June 18, 2017
A meditation on a famous code one-liner in the programming language BASIC. The book demonstrates the elegance of the simple line of code producing a fascinating output. It reflects on the one-liners programming language (Basic), visual output (maze), required functions (randomness), required hardware (Commodore 64), re-interpretations (in processing) and playful extensions (complimentary maze walker). There is no need to give every chapter the same amount of attention. But when you end the book, you are left with a high respect for the thoroughness and meticulousness with which the book's 10 (!) authors executed their mission.
September 20, 2018
Anyone who has an interest in computer code, be it programmers, media theorists or otherwise, would have fun reading this. There are parts where the authors delve too deep into the code for a layman such as myself to keep track, but it was not too bothersome. I simply glossed over those areas and could use the general gist of it to understand the implications they would discuss afterwards. Definitely an addition to anyone interested in software studies.
December 2, 2012
A "world in a grain of sand" enterprise, it succeeds better at the task than I expected. (The sections on modern art are very strained, however. I would've preferred some mathematical analysis of the mazes generated and their properties to that whole section.)
March 8, 2016
The premise of this book is pretty fascinating AND I like mazes AND think C64 stuff is neat but no, no I don't think I can bring myself to finish this one cover to cover.
Drawing a cool maze shaped set of lines in the proverbial sand and calling this stalled-out.
Drawing a cool maze shaped set of lines in the proverbial sand and calling this stalled-out.
January 11, 2016
My 5 star rating is in spite of the book's sometimes pedantic nature. I enjoyed the incredible detail that went into analyzing one simple line of code. I was particularly impressed with the creative digressions that never strayed far from the treatise's heart and soul.
March 14, 2013
Geekiest book ever... blog post forthcoming.
June 23, 2014
I enjoyed it. An interesting read for computer geeks, particularly those of us who grew up in the 1980s and used a C64 or programmed in BASIC.
January 10, 2014
A nice trip into recursion, but I got a little bit annoyed after a while.
Displaying 1 - 30 of 35 reviews