"Every time a server crashes, an angel gets his wings!" Yeah, sure. Watch who you say that around. I'm still learning how to walk again.
With your script all written and your database in place, you're probably chomping to see it all work. But the most important thing to remember with CGI scripts is to make sure they're stable. Always have a trusty engineer take a look at your scripts to make sure they don't do anything stupid. If the engineers claim not to have time to look things over, say something like, "I'd hate to crash the site with a script that erases the hard drive." They'll be doing the hustle in no time.
Once you get the go-ahead, put 'em up and push 'em live. If you want to
see everything all in one place, take a look at the finished code (cut and paste at will).
So there you have it: Your very own, living, breathing CGI script. As you can see, most of CGI is just standard Perl, with a few changes here and there to give it that bonus CGI flavor you have to pay so much extra for at Starbucks.
So with the power of CGI firmly in your paw, what're you going to do with it? Well, that's up to you. The mighty CGI knowledge has been known to drive some mad. I know many scripters, who having learned the art, decided to head into the thickest forests they could find to build shanties and bombs. Knowing how to script CGI is the easy part of the equation. The toughest part is figuring out how to use your power to do something worthy, while maintaining your sanity and the sanity of the sysadmins who oversee the machines that run your scripts.
So with that, I'll leave you to it. Go conquer the world with coolness - and don't forget to send me the proceeds in the form of a check or money order.
