Oh I see. It's fine if you cannot reproduce the program from memory after copying it once, because that's not how software is written. The idea is to understand what the various statements are doing in the program - how to use loops, counters, variables, etc. and also howo to break a problem into little steps and procedures which you then turn into code. If I were you I would read a book or watch some videos about programming.
There are only a handful of basic concepts in programming: Variables, Functions or Procedures, Input & Output, Conditional branching, Looping and maybe a couple I'm forgetting. If you study what these are, what they are for and how they work, you will start to understand how to create your own program.
Hard to say without knowing more about the problem. I mean, what went wrong with the code you copied from the book. Could be a simple typo, and example code sometimes also has typos or is just wrong - surprisingly, authors sometimes confidently type in code exampoles without running them. Carefully comparing the code you entered with the code in the book might reveal the problem.
A friend of mine made up a rap song a long time ago about a superhero who got his powers from toxic waste. I remember one line, "His stupefying aroma, is like he's from Tacoma."
The excessive rain thing is actually bullshit. US cities that get far more rain include NYC, Chicago, Atlanta, New Orleans, Miami, Houston, and even relatively nearby Portland Or.
Totally depends on how long it takes to make and serve. If a place could somehow deliver beef Wellington to you in 2 minutes at a drive-thru window, I would call it fast food, but this would not redefine all beef Wellington as fast food. You're conflating "fast" and "junk".
Technically it only describes spherical bastards in a vacuum.