And so he said, "I need to make fun of him. I need to put in a comment system." And so, his friend when he saw the comment was like, "What the fuck? this subroutine and you put XoYo, X1Y1, but when you call this other subroutine , it's XoX1, YoY1, you get that right, and that's your job."
But if you've never, ever done any coding before, that is so much more fun and easy than install Visual Studio, and then figure out what subroutines you need to include, and, like, what libraries you need, and then compile, and then how do you-- what you need to do. And then it also shows you, this is the JavaScript for the code that you made.
over and over again. So they started building a library of tapes, and then they could bring and put those tapes together when they were working on another problem. They didn't call it subroutines at the time but in effect it became the basis for some of Hoppers work later on. They developed a concept of flow-charting, to chart out the problem they were working on, and to allow people who were working on the problem to know what the person had done before them. So you start seeing the rudimentary operational system behind programming also
And register 14 was the return address. So to return from a subroutine , you just put register 14 back into 15. And that returned. The last one is a conditional return from function call all in one hit.
So he's basically saying that his leg did not feel like his own. if you're setting your body on subroutines like that?
and father genomes, if you will. And a program is really a tree of subroutine calls all the way down to simple operations like additions, multiplications, and ands, and ors.
that she would call the Compiler. The compiler would allow the computer to start helping the programmer program itself. She tells the world about the compiler in a very funny titled paper 'The Education of a Computer' and in that paper she maps out how a Compiler can pull from a library of subroutines , um, take care of many of the administration functions of the programmer and create automatically, machine code. She, 6 months later, produces
directly got cyclones right. We kind of had a, if you like, a cyclone subroutine . But now the basic physics of these models spontaneously generates cyclones in an amazingly accurate way.
So he's basically saying that his leg did not feel like his own. But at some point, I realized that it seems that often you set part of your body off on a subroutine .
And then it also shows you, this is the JavaScript for the code that you made. This, as many of you may know, is based on the open source Blockly subroutines that-- the Blockly source code that Google has helped us with. One thing that was also really exciting when we launched this tutorial was being able to say that we were using intellectual property
So he's basically saying that his leg did not feel like his own. So it's not quite as simple as saying, I told my I guess, we're in a software company because we were talking about subroutines .
in a long tunnel with only the problems to solve ahead of her. Her and Richard Block were constantly searching for ways to increase the speed of the coding process and their solutions evolved out of the expediency rather than intellectual curiosity." So what did they create during those war years? Well they came up with the concept of subroutines . They would use a tape to program the machine, to code the machine. And what they realized was that once they had a piece of tape that was cleared of errors, why not use that tape