Updated Part G with rest of manuscript

005/codex-005.tex

@@ -255,6 +255,8 @@ The problem was that the magazine employed a faulty polling technique, and so di
 At the height of the Great Depression, most people couldn't afford a magazine subscription, much less an automobile or a telephone, and these people tended to vote for Democratic candidates. The inaccuracy of the poll ruined the magazine's reputation, and it ceased publication two years later. (In point of fact, they not only failed to find a random sample, they relied solely on people who responded to their poll, and such people responded because they were vehemently opposed to Roosevelt. This is an example of ``non-response bias'' or ``participation bias'' but the point is the still the same—they failed to select a random group of people to poll.)
 \kdive{-1}
 
+Part G
+
 I have previously mentioned the educational-industrial complex and its very aggressive embrace of what was then called ``Web 2.0'' and how just devolved into little more than social media. 
 
 Because I wanted to be seen as someone who could ride this wave into the future, I decided to embrace it wholeheartedly. I decided to get a website first, so I looked around, found a webhost (who was also a domain registrar—convenient), plunked down \$30, and I was in business.
@@ -263,9 +265,35 @@ This was my first real experience with a server and FTP. I had made websites bef
 
 I had to learn FTP, which meant that I needed an FTP \textit{client}. I had no idea what a client was, so I had to learn some new vocabularly. It was like being in elementary schools again, where new words were printed in boldface and then defined in the margin. But I eventually figured out (through learning JavaScript) the difference between client-side (your computer) and server-side (their computer).
 
-Part G
+With an FTP client in hand, I could now upload files to my web site far faster than i could via a web based file upload, perhaps because FTP clients don't need to wait for ads to load. I had no idea how to properly view these files locally before I uploaded them to the web, so the only way I could check that everything was correct was to upload them and then refresh my web browser.
 
+FTP gave me a lot will have control over a website that I had never had before but if i've learned anything think from reading comic books it's that great power comes with great responsibility. Sure you can do more things now and rely less on your hosts for certain things (and learning neat .htaccess tricks is but the first of these) but that means that you must assume more responsibility for things. If you screw up a config file it's entirely possible that your web host has a backup copy somewhere and you can file a support ticket and they will eventually get around to replacing it. Even better is when you screw up a config file but you have a backup version of it and can just FTP it to your site. The ideal situation would be to understand that config file well enough that you never make a mistake with it but that's not going to happen we're all human we all make mistakes. To err is human, to have an uncorrupted back up is divine.
 
+But yeah let's talk about backups. If you're going to have a website than you need to seriously consider handling backups on your own. Sure, your web host might make weekly backups, but that is to cover their ass not yours. Their backups are there to cover their fuck ups not yours. The only way to recover from your own fuck ups is to manage your backups.
+
+That's not always a simple thing. Because Web 2.0 included blogs I decided to start a blog where i could use my newly minted English degree to talk about books. My web hosts at the time had a one-click install  for WordPress which was then considered to be a blogging platform and little else, so I clicked once and the Big Bad Book Blog was born.
+
+Until then i had been fairly comfortable with everyday run of the mill HTML and CSS files. But nothing is perfect right out of the box and iIfound that my newly formed book bblog was less than satisfying to me. Changes were obviously needed.
+
+The challenge/problem for me is that WordPress is a web application that uses PHP, CSS, and Javascript. I could handle CSS, but I needed to figure out PHP and Javascript.
+
+So yep, Ihad to learn PHP at least in a rudimentary way, and I had to learn some Javascript in an even more rudimentary way.
+
+These were not impossible tasks.
+
+The problem for me was that while CSS and Javascript are client-side technologies, PHP is a server-side technology.
+
+Let's back up a bit but to understand how this works. It's actually pretty complicated but I'm going to present a greatly simplified version of this.
+
+When you visit a website, there are two computers involved (mainly)—yours and one that is actually hosting all the files that make up that website.
+
+Your computer is called the client computer. When you view a website on your computer you are looking at it in a web browser which is a client-side technology. That is, it exists on your computer. If you don't like the web client you have now you can install a different one.
+
+On the other hand all those files that your client is downloading and presenting to you as a web page must exist somewhere. And they do—on a server somewhere. When you sign up for a website what you are doing is agreeing to pay money for some space on a computer that has been can configured to serve those files to whomever asked for them. In other words, it is a server.
+
+Like i said you can use an FTP client to move files over to your server but if you must make a mistake in one of those files and don't catch it before you upload it then it's there for all the world to see. Even worse you can upload a file with serious errors in it that causes your entire website to not be available. Uh-oh. that's not good.
+
+The obvious solution is to do all your practice runs in a localhost environment.
 
 Part H
 
@@ -297,15 +325,10 @@ It was fun but it was also frustrating to have to start over so i did what i sho
 
 I found a highly adaptable theme that i really loved (Graphene) and became an expert in it and started helping out in its support forums. The theme's developer appreciated my efforts and made me a moderator in those forums and also gave me free access to the mobile-friendly version of the theme. It was a great time and I was learning a lot.
 
-
 This was back when mobile was just becoming a thing and a lot of websittes had two versions of their site—a desktop version first and a mobile version second but at some point people began accessing websites more on their mobile devices than on a desktop so that process is now reversed—we develop first for mobile and then usually later for desktop, sometimes poorly. If you've ever been to a website that looked fine on your phone but looked like an utter shit show on your computer this is why.
 
 I was not, however, getting a teaching job. I was getting lots of opportunities as a substitute teacher but that was because I could follow a lesson plan, I could manage a class room and keep kids in line, and I would actually teach and then wander around the classroom and make sure kids were learning.
 
-Part H
-
-
-
 \section{Today}
 
 I am in a very different place now than I ever thought I would be. I'm not on Plan A or Plan B. In fact, I've pretty much run out of alphabet to describe exactly where I am now.