Code Execution Quotes

I'm OK with procedural code, and the web is a top-down type of problem. It makes sense to me that you have HTML, you spit out a bunch of HTML, then you call a function to do something and then call another function.

The good news about computers is that they do what you tell them to do. The bad news is that they do what you tell them to do.

It seemed really amazing that you could write a few lines of code and have it learn to do interesting things.

I'd make people say 'use Fork;' if I thought I could get away with it.

The computer would do anything you programmed it to do.

Any good software engineer will tell you that a compiler and an interpreter are interchangeable.

The bare bones tools for a cyber-attack are to identify a vulnerability in the system you want to gain access to or you want to subvert or you want to deny, destroy, or degrade, and then to exploit it, which means to send codes, deliver code to that system somehow and get that code to that vulnerability, to that crack in their wall, jam it in there, and then have it execute.

I suppose you could switch grammars once you've seen 'use strict subs'.

It used to be the program's purpose to instruct our computers; it became the computer's purpose to execute our programs.