- Template::Test — Verify that the logic in my templates (which I strive to keep simple) is working.
- Devel::Cover — Produces HTML output that can provide incentive to write more tests. The HTML output gives “red-light, green-light” visualization for what is happening with tests. If I incorporate this with the testing infrastructure that I’m putting together, other people (i.e. my boss) should be able to see my progress over time as far as writing test cases that cover the functionality we have.
- Class::DBI::DataMigration — Dan Friedman’s effort to distill his experience on multiple migration projects to something that is easy to set up and use. Since I’ve been doing a lot of this by hand up till now, this tool will come in handy.
- DBD::Mock — I learned how useful this tool could be yesterday for testing the sort of functionality you want to use in cases of, say, database failure. Since the site doesn’t degrade very will in case of a failure, I should be able to use this tool to come up with and test solutions.
- SQL::Translator — Translating between Database’s different dialects. And it also gives you nice tables of the schema.
Did I ever tell you that I love Free Software? I do. I love the fact that, in a meeting today about spam and the prevention of it, there was talk of appliances. The NT admins pointed out that these appliances use the same software we are using, but just put it inside a locked box and give you an Web-based interface. But, since the software is freely available, we already use it. And we’ve already adapted it to our needs in ways that the appliance couldn’t be used. But, that’s just part of the story. Did I ever tell you that I love Emacs? I do. I love the way I can run the same operating enviornment on Windows, Linux, or Mac OS. I love the way I can adapt Emacs to my every need. For example, at work I have to sort through mail and look for spam or phrases within spam that can be blocked. I wrote up a nifty bit of ELisp so that whenever I hit a spam, it grabs the most easily blockable parts (URLs, email addresses) and helps me find other pieces. It has made my job that much easier. And, since Emacs is free software, it has grown and evolved with the input and contributions of all its users. Emacs is about 20 years old, but it is one of the most powerful enviornments that you can use for day-to-day computing. I use it to read email, edit code, take notes, prepare documentation … I’m using it right now to type this entry. Better, with Emacs and Free Software in general, if I run into a problem with the software I can fix it. Sure, I’ll send email to the author, but sometimes he’s busy. I can fix it. That’s what I’ve done with the RSS reader in Emacs. I’ve run into problems with the XML parsing code with RSS, but I was able to fix it. And, get this, since Emacs is free software, I was able to contribute my code back, safe in the knowledge that other’s wouldn’t have the same problem. But it’s not just Emacs. Its a whole slew of software. I use Mail::Audit::List for sorting my mailing lists into separate folders. Today, I found a bug in it, fixed it, and submitted the patch. This power, the ability to fix your own problems, or, lacking the skill to fix them, appeal to the community of fellow user for a fix, is awesome. Proprietary software doesn’t give you that power. At the most, you can appeal to your fellow users for a work-around. Rarely will you find a fix. You’re gonna have to wait for the vendor to come out with a band-aid. And then, there is a chance that they won’t understand the problem (and so won’t give a complete fix) or they’ll fail to fix the problem at all. Does Free Software have its problems? Sure. But you can fix them.
After reading enough of Paul Graham (thanks David!), I want to try some server-side web-programming in Lisp. I found Common Lisp Hypermedia Server, so I imagine I’ll check it out sooner or later. But, heck, I’m already doing the modern Lisp — XSLT!
Dave talks about the Python and leads into programming using an outliner. This is very interesting to me. I love Perl (the un-Python) and it is interesting that he talks about the advantages of programming using an outliner because this is what led me to contribute the outline-mode enhancements to emacs‘ cperl-mode.el.
Emacs is actually a pretty nifty folding editor. Here is how to use it to edit Perl code in this fashion.
Cool! Everybody’s favorite search engine, Google, is sponsoring a programming contest.
I hate sleep — it means that work takes up more of my life than I want it to. Sleep is good for my kids (so I get a few hours to myself), but, overall, I hate it.
I perused the archives for the blogger list today and came up with the specs for a couple more calls so I’ll be able to make it possible for you to go through posted messages on your blog with emacs and edit them.
Then I had a great idea for integrating htmlize.el in the blogger buffer so that you can add faces and whatever to your messages to make them pretty and stuff.
Hey, with Emacs21, you could drag-n-drop pictures into your emacs buffer and have them automatically posted to your site. Coolness!
That’s the real trouble with Emacs — too many navel-gazing programmers intent on programming. Not enough navel-gazing programmers intent on blogging.
“Never do anything twice” That should be the mantra of all system administrators. Whatever you do, automate it. If it is installing a piece of software or the steps that you have to go through to add a user, automate it. On Unix, various tools exist to help. When it comes to managing the configuration of multiple machines, CFengine stands out. Its meta-language allows you to actions to take on various classes of machines. You can create classes (e.g. web-servers) and have packages installed on those machines and various configuration tweaks made. It really saves time because it helps you document all that you’ve done to set up a package or service. For compiling software and installing binaries, there are different methods available depending on your operating system. Solaris has a package system, but it installs software in funny places (usually something like
/opt/packagename) and there is no obvious, easy way to make your own packages. RedHat Linux uses RPMs which at least learned the fallacy of putting every package in its own special hierarchy, but they didn’t make producing RPMs very easy. They use some sort of meta scripting language that is yet another thing to learn. At least the packaging system is free, though. The various free BSDs (FreeBSD, NetBSD, and OpenBSD) have what they call a ports system. This is based on Makefile, so you don’t have to learn anything if you already know about Makefiles, but it can be difficult to get everything right. For example, after you’ve gotten the whole thing to compile and install correctly, you may have to go through a few iterations of the install to produce a binary package so that you can ensure that you have all the files included and all the extra steps taken care of. The best system I’ve seen yet is Debian’s. They use Makefiles plus some scripts to simplify things. The scripts can take care of 90% of the work in most cases, and in those few that they don’t, they greatly simplify things. When it comes to installation, they have fakeroot which ensures that they’ve captured all the files that are installed. Another good thing about Debian is their Apt protocol. Apt will take a debian package, grab all dependencies from the Internet (optionally compiling them) and install everything. It can be done totally non-interactively — a huge benefit. The driving force behind good system administration, as with good programming, is laziness. As the SysAdmin, you have great power available to you to automate a lot of what you do. Use it.