A Little Background I’m usually a stickler for best practices, but automated testing is something that has eluded me in my professional career for a long time. I typically work on legacy, line of business applications. So automated testing was never a priority. I’ve tried and failed to introduce various development teams to automated testing. Legacy applications are inherently difficult to test. Most everything I’ve read about automated testing points to trivial examples of testing and something like add (1, 2) and making sure the output was 3.
As developers, we sometimes tend to want to throw our latest, new-found tech toy at every problem. After recently converting this blog from a WordPress site to a static HTML site using Hugo, of course I’ve decided to try this elsewhere. Here’s what I learned. Benefits of Static There are a lot of examples (1, 2, 3) showing the difference between Static Site Generators (SSG) and a CMS like WordPress.
As you can see from the last post, this blog hasn’t been updated in a while. For all intents and purposes, it’s a static site. So why not take this opportunity to test out static site generators? For this, I’m using Hugo. There’s been a lot of stuff going around with these, but I haven’t had a chance to test them out. A dead blog is a perfect place for this.
In The Series Part 1 Part 2 Part 3 Part 4 Define The Problem In the past, I’ve done some freelance Web Development and Web Design for different clients. One question I’ve always had to ask myself is: How will the user be updating this website? That question is usually preempted by a question to the client: Do you have any HTML experience? I can count (on one hand) the number of times that I’ve heard a yes to this question.
Now, it’s no secret that I can be a moron sometimes, but I’d like to put it on record that it was all me and not WordPress 2.7 that had the issue. So I’m sitting here last night minding my own business and Chris Coyier sends out a tweet talking about how it took him 10 minutes to upgrade. So I figure, why not? I already had the WordPress Automatic Upgrade plugin ready to go, so I figured it would be a breeze.
So it’s been about a weeks since it was out, so I figure, why not? After all I have the WordPress Automatic Upgrade plugin, so this should be a breeze. Now this plugin makes upgrading WordPress ridiculously simple. It handles file backups, database backups, deactivating and reactivating all plugins, etc. So I go through the process and I’m not totally disappointed. There were the normal problems we have with all upgrades and some new ones:
New Domain I has finally occurred to me that I should have gotten my own domain name a long time ago. Really, I don’t know what I was waiting for, but it was about time. Since my focus is Web 2.0, WebDevelopment2.com was an obvious choice. I’ve already written about moving wordpress to a different domain, so moving to this domain was walk in the park. I loaded up PhpMyAdmin and exported my database.
Here’s a quick tip for today: Interlink Your Posts: aLinks Plugin
After reading this post, I have come to the conclusion that Web Developers can learn a lot from this. I cannot over stress the importance of number seven (7) and eight (8): Everyone suggests researching webhosting companies, but for your first year, just use a web host that can get the job done. I use Dreamhost, and its fine except for the 20,000+ visit days … If youre serious about your site, get your own domain name that somewhat relates to your topic (obviously cleverdude.
Now, I’m going to be deliberately vague because I don’t to give this blogger any traffic. This is what happened. I developed a new a interest lately. As a result, I was looking for a blog that I could use as a reference. All my searches returned this one blog. The name of the blog was specific to the actual topic. I went on the blog and to my dismay, I saw post after post which looked like emails from a mailing list.