From page 4: "Like a diary from the forgotten past, computer code is embedded with
stories of a program’s making, its purpose, its assumptions, and more"
I think that this is a very good point, especially in today's age of all of these large software companies constantly testing new software. I always see countless articles that go in-depth on easter eggs and clues that are in the beta code that is released for testing.
From page 12 "...PRINT does not literally “print” anything
in the way the word normally is used to indicate reproduction by marking
a medium, as with paper and ink—instead, it displays. To send output to a
printer, PRINT must be followed by # and the appropriate device number,
then a comma, and then the argument that is to be printed."
I had no idea that was how printing to an actual printer worked. I never really thought of it, actually. I always just clicked "print" and then paper came out with my document on it. Tying in with Design 2, I can't imagine what the code looks like for all of the complicated settings and such.
Also, I've realized that when I first started to learn how to code, I always thought of the "print" function as "oh, instead of printing to paper, it prints to the screen." I've now realized that it is, in fact, the other way around. I wonder what paradigms will switch over the next few generations.
From page 4: "Like a diary from the forgotten past, computer code is embedded with stories of a program’s making, its purpose, its assumptions, and more"
I think that this is a very good point, especially in today's age of all of these large software companies constantly testing new software. I always see countless articles that go in-depth on easter eggs and clues that are in the beta code that is released for testing.
From page 12 "...PRINT does not literally “print” anything in the way the word normally is used to indicate reproduction by marking a medium, as with paper and ink—instead, it displays. To send output to a printer, PRINT must be followed by # and the appropriate device number, then a comma, and then the argument that is to be printed."
I had no idea that was how printing to an actual printer worked. I never really thought of it, actually. I always just clicked "print" and then paper came out with my document on it. Tying in with Design 2, I can't imagine what the code looks like for all of the complicated settings and such.
Also, I've realized that when I first started to learn how to code, I always thought of the "print" function as "oh, instead of printing to paper, it prints to the screen." I've now realized that it is, in fact, the other way around. I wonder what paradigms will switch over the next few generations.