Publications

I’ve been a contributor on Associated Content, now Yahoo!’s Contributor Network (since the site was purchased by them), for several years now.  For the last few years I was a “Featured Contributor” in their Technology category, so focused most of my writing on meeting their requirements.

Featured Tutorial
The good news is that for a few weeks now, an article I wrote well over a year ago on using the Pigeon IM client to manage all your messaging connections has been Yahoo’s “Featured Tech Tutorial.”  The up-tick in views (which translates into more money) was significant and appreciated.

Changes to the Featured Contributor Program

Recently, Yahoo! announced that they were dis-continuing their previous Featured Contributor program and implementing a new one.  We were all invited to apply for one or more FC designations, based on category.  Naturally, having nearly 25 years experience in computers, programming, and consumer electronics, I thought I had a pretty good chance of getting re-accepted in the Technology category.  Only one problem.  The old program had a production quota – I was supposed to contribute 3 articles per month for their standard pay for FC articles ($10 each) plus one more article in the Tech category.  With a “day job” keeping me busy 50-80 hours a week, plus the responsibilities of raising a family and working on our farm, I frequently didn’t complete all 4.  The new program has a much more relaxed quota however – only 1 article every 3 months is required.  I could have made that even at the busiest of times.

Unfortunately, my past record of not completing all assignments on time garnered me a rejection this time around.  Go figure.  Guess I’ll concentrate more on my presence at Suite 101.

I don’t plan on jumping away from the Y!CN altogether.  There’s something to be said for having articles on a Yahoo! owned site.  But I’ve noticed that some of my content on other sites is gaining momentum.  For example, TrueKnowledge.com’s Facts About Wyatt Earp has a link to my article  Surprising Facts about the Gunfight at the OK Corral published on Socyberty.com (a Triond site).  This has led to a nice increase in page views there.  If I continue to flush out content on these other platforms and not focus so much on Yahoo!, I should have a nice, diverse base of residual-earning content.

I previously reported that I had become a contributing writer on Suite 101. For my first article, I decided to summarize some of the Best Free Encryption options available for computer users.  I covered the pros and cons of Encrypting File System (EFS), TrueCrypt, and GnuPG.  Here’s the quick rundown:

• EFS: OK for Windows users who aren’t using a home / basic edition of Windows.  Can’t encrypt on removable devices.
• TrueCrypt: Good for encrypting not only sections of the hard drive (or entire partitions), but also removable media like thumb drives, CDs, etc.  Encrypted emails possible, but not ideal.
• GnuPG: Best for end-to-end encryption of data at rest and in transit (via email or IM).  Most complex to set up, but messages can only be decrypted and read by the intended recipient.

For download links and full details, please check out the entire article.

During our trip to Arizona this past spring (see pictures), the visit to Tombstone inspired in me a renewed interest in the famous Gunfight at the OK Corral and the surrounding events. After some research, I wrote a quick little article entitled Surprising Facts about the Gunfight at the OK Corral. I wasn’t quite satisfied with that one however, so I sat down and wrote a more extensive article called Behind the OK Corral – the Legend and the Legacy, which goes into more depth and discusses the prevailing attitudes and histories of the combatants. It also covers some of the alternate interpretations of history as maintained by the surviving members of the Clanton family. Give it a read and let me know what you think.

Several months ago I wrote an article for a Helium Marketplace publisher.  My submission was not selected, but I find that it is one of my more popular articles on Helium (definitely in the top 3), so I thought I’d share it here.  Please read How to find out what’s running on your PC (and why this is important).  Let me know how you like it.

Imagine planting a pine tree, a small seedling, using a spade shovel. Not too difficult, right? Now imagine doing that 1000 times. Repeat every spring for 14 years. That’s exactly what Bob Zirnhelt did on 11 acres where he and his wife live in Davison, Michigan.

Beginning in 1991, Bob began buying young trees from the Genesee County Conservation District. Every spring he would buy 1000 seedlings and plant them around his home. “It’s one of the best ways to enhance the beauty and improve the value of your home,” he says. Bob is a code enforcer for the city of Burton, and knows a thing or two about home values.

Read Full “Zirnhelt’s Trail” Story on NewsFlavor.

I recently started writing articles for a publisher who puts out several newspapers local to our surrounding communities. The Davison Messenger, The Tri-County News, The Burton Banner, etc. Some of them were existing publications which he purchased, some are new startups. All are collectively published under the name of his company, ‘Flint Area Media’ (FAM).
Production problems and slow sales have caused some delays in getting the papers out regularly, but I have hopes that these glitches are temporary. The organization is currently moving into a newer, larger building, and I take that as a good sign.

Of course, I expect to be paid for the articles I write, but I’m also doing it for the excitement of seeing my byline in print. Plus, although FAM eventually expects to make all their articles and stories available on-line, they are not ready yet for that. In the mean-time, Mike (the publisher) has given me permission to post them on the 3 sites I write for (Associated Content, Helium, and Triond). I’ll place links in future postings.

A while back I wrote a story entitled ‘The Great Rodeo Trainers’, which was sold to a Helium Marketplace publisher with exclusive (I thought) rights. Now I see the story has reappeared on Helium’s website, so I’m thinking it was only sold with first publication rights rather than exclusive. I could never find it on-line, so I’m glad it’s back on Helium because it’s one of my favorite stories. Read The Great Rodeo Trainers and let me know what you think.

This article was originally published by Triond on their web site ComputerSight. I thought it was time to reprint it here, so it appears below in its entirety.

---

Configuration Management (‘CM’ hereafter) means a lot of different things to different people. Weighty tomes have been written describing the goals, policies, procedures, benefits, pitfalls, and a variety of definitions of CM. One recent CM plan I worked on is a 20-something page document attempting to detail this information and how it relates to the client’s projects.Most of the information available can be boiled down into 4 key concepts, or what can be called the 4 cornerstones of great CM. These concepts represent ideals. The challenge is in the implementation, so that the policies, procedures, and utilities developed support these ideals, or at least the intent behind them.

1. Version Control : Everything is maintained in a Version Control tool like Serena’s. Some agreed set of items (Configuration Items, or CI’s for short) stored within the tool represent baselines. In other words, they are the set of revisions currently in production. They are not necessarily the most recent revisions.Builds intended for deployment to any post-development environment (QA, Test, Prod, whatever) are always pulled from Version Control, and never copied directly from a development environment.
2. Separation of Duties and Least Privilege : Actually, these are two principles lumped together because Least Privilege is not possible without Separation of Duties, and Separation of Duties is pointless without Least Privilege. The former simply means that no single person has independent responsibility over more than one area of a system.For example, developers change code, perform unit test, etc., but do not deploy or promote such code to any non-development environment. CM people promote code, but do not develop applications, nor do they approve code changes made by developers (although they may participate in code reviews).
   DBAs have database privileges, but don’t develop application code nor act as system admins. And so on. The Least Privilege principle simply states that no person or running process has more access or system privilege than they need to perform their normal duties or functions at any point in time.Access or privilege for either people or processes can temporarily be increased during the performance of some activity as necessary, then immediately restricted again. Policies implementing these controls make allowances in both these principles for emergency situations.
3. Auditing : CM personnel periodically conduct audits of applications, systems, and procedures. Any updated application software or configurable item should be traceable to an approved change request, as well as through the entire set of existing quality control, tech review, and change control procedures.This includes not only application executables but database configurations as well. All items are compared with their baseline counterparts in the Version Control repository (ie; the revisions marked as ‘Production’). Discrepancies are reported as non-compliance issues and investigated, and will generally lead to procedural changes designed to eliminate future non-compliance.
4. Automate, Automate, Automate : This one is an over-riding theme for how we accomplish all this with limited resources. Checking items out of and into Version Control should be quick and painless, and integrated into development IDEs (Interactive Development Environments) if possible. Code promotions are scripted. Database changes are scripted. Auditing utilities are scripted.These scripts themselves are subject to review and kept in version control. Tying it all together gives us reliable, secure systems built with verifiable, repeatable and efficient processes.

Someone posted a challenge to the writers on Associated Content to come up with humor articles to be posted on the April 1st, April Fool’s Day. Being somewhat of a fool myself, I accepted the challenge, along with a dozen or so of my fellow AC writers. The results are compiled in a Squidoo lens – I’ve included the link below. My entry is printed here for your convenience. If you like it, consider voting for it on Squidoo by following the link.

---

Foolin’ With Your Kids
Not only is it our “birth”-right to play jokes on our children, it is also our sacred duty, and one that my wife and I take very seriously. After all, how else will they learn patience? How will they learn humility? How will they learn to fool and embarrass our grandchildren when the time comes?
Embarrassment
There are numerous ways to embarrass your kids. Some kids are embarrassed by the mere presence of their parents when they’re hanging out with their friends. This should be exploited whenever possible. Accentuate whatever traits you possess that your kids find embarrassing. If possible, combine these traits for maximum impact. For example, if your singing embarrasses them and they can’t stand old country music, pull up to the school to pick them up with your windows open, belting out “Lovesick Blues” at the top of your lungs. Volunteer to chaperon the high school dance, and show up wearing the same pastel-colored velvetine tuxedo you wore to your 1979 prom. While there, offer to teach your daughter, her date, and all her friends how to do the “Electric Slide.”
Embarrassing your teenage kids is almost too easy, and can be done pretty much anywhere at any time. Whip out the baby pix showing your son in the buff. Say things like “Aw, my little man is growing up. Looks like he’s finally gotten over the ‘girls have cooties’ phase.” These are especially good when your son is spending time with a new girlfriend.
Tall Tales
Getting your kids to fall for some things is a little more challenging. When my son Stan, who’s now 13, was about 5 years old, he was asking me about the various knobs and buttons on the dash of my car. I went through the radio, windshield washers, fog lights, etc. Then, adopting the soberest countenance I could muster, I pointed to the emergency flashers. “You should never, ever, push this button.”
“Why not?” he gravely asked.
“That is the ejector seat.”
“What’s a ‘jector seat?”
So I explained what an ejector seat was, and how after it was introduced to the public in the James Bond movies, people started asking for them in their own cars. Responding to this demand, the car manufacturers began making them options that anyone could get when they bought a new car.
He was nervous, but fascinated. “So what would happen if I pushed the button?”
“A secret panel in the roof would open up, and a super powerful spring would shoot you right out. The car would keep going, so you’d land in the road and probably get run over by that truck behind us.”
“Wow. Does Katie know about this?” he asked. Katie is his older sister, and I wasn’t sure whether he was worried that she might push the button on him, or excited about the possibility of pushing the button on her.
About a year later, I was again driving with my son in the car, and I had forgotten all about the ejector seat conversation. Not him! We needed milk, so I stopped at the corner store. I told him I would be right out, and to keep the doors locked and not let anyone in the car. He says, “Don’t worry, Dad! If anyone tries to get in, I’ll just slide over into your seat and push the ejector seat button! Boy, won’t they be surprised!”
“Um… yes. But keep the doors locked just in case.”
A few months later we were once again in the car together, and I needed to use the rear defroster. I accidentally hit the emergency flashers button first. They flashed a couple of times before I turned them off and turned on the defroster. My son jerked is head to look at me, eyes wide as tea saucers. I knew what he was thinking. I said, “Boy, it’s a good thing that ejector seat has a 5 second timer! I remembered to shut it off before it flashed 5 times, thank God. You were almost a goner!”
“Da-ad! Why did you do that? You almost splatted me on the road!”
“Sorry pal, I just hit the wrong button. It won’t happen again.”
My wife said that some day when he becomes the laughing stock of his driver’s education class, he’s going to come home and kick my butt. Maybe so, but I won’t be alone. Not long after this last exchange he was basically tattling to his Grandma about me almost splatting him on the road. We had to surreptitiously explain what was going on. Now she’s completely in on it with us. My daughter on the other hand tried to tell him that we were all making it up. When she wouldn’t sit in the passenger seat so he could “prove” that we weren’t (mainly because she couldn’t be bothered to move), he became more convinced than ever that she was lying to him. [click to continue...]

Some time back I wrote an article about Charity Music, a great non-profit organization that provides musical instruments (and sometimes instruction) to students, soldiers, and senior citizens who desire to play but can’t afford to buy or rent them. The article was originally published on Associated Content, but as reported at the time, I planned to also post it on Helium. The great thing about the article appearing on Helium is the fact that I could donate all advertising revenue (my share at least) to the charity itself! So if you missed the article the first time around, read all about Charity Music on Helium, and remember – just by reading it you’ll be helping out a fantastic cause.

Pub Crawl!

I thought this would be a good opportunity to let you know about a recent development at Charity Music. They are organizing what they hope will be the biggest Pub Crawl in history, and they hope to get listed in the Guinness World Book of Records in the process. The goal is to have up to 100 clubs and bars from every state participating. If you own a bar and would like to get in on this, it might be a good way to get some great publicity, and in any case you would be helping out the cause. More information is available at the Pub Crawl Registration site.

A Helium Marketplace publisher recently asked for an article entitled ‘Quick Tips for Inner Peace’, with a 700 word maximum. I condense religion, psychology, and meditation and attempt to answer the call. Let me know how you think I did.

---

Inner peace is a state of mind in which one is free from conflict in mind and spirit. This is not to say that there is no conflict in one’s life, simply that there is harmony between one’s mental, emotional, and spiritual aspects. Without such harmony, the flow of creativity slows or stops, physical and emotional ailments do not heal as quickly and may worsen, and progress toward ones goals in life is impeded. To remove these blockages one must restore harmony and return to a state of inner peace. Understanding is the first key to unlocking the door.

Let Go of the Past
Often attaining inner peace is not so much acquiring something as it is letting things go. The past is immutable, so holding on to regrets is counter-productive. Understand that mistakes are part of our humanity, and that sometimes it is the lessons learned the hard way that enable us to mature and progress. Realizing that just as much of our wisdom comes from error as from trial, one begins to accept that our mistakes play an indispensable role in our development.

Guilt is a large source of internal conflict, and must be expunged. The quickest way to reduce guilt is to apologize to those whom you’ve wronged. It is not essential that they actually forgive you, but it is essential that your apology is sincere. You have to actually mean it when you express your remorse. In this way, guilt fades to regret, which can then be dealt with accordingly. Examine the bad decisions and lapses in judgment, figure out where you went wrong and how you could have handled the situations differently, then move on.

Read the Rest of the Article >>

The Field Car was a beater. It was a 1971 Maverick, which I bought in 1980 while in college. It wasn’t really a beater then, but it didn’t take me long to turn it into one. With dedication and determination, any car can be turned into a beater in a matter of months.

The transformation on the Maverick began when my room mate Tim came home with me for the weekend, and I had to repair the fences around the horse pasture. My parents left for the day, and we didn’t want to carry fence wire, tools, and extra posts around a 200 acre pasture, so we put it all in my car and headed out. All was well for the most part, until we got bored and decided to see how well the Maverick would take the hills. The educational opportunities in this type of exercise cannot be overstated. Not only did we get most of the fences fixed that weekend, but we learned how to replace shock absorbers, too! We could have learned to do some body and paint work as well, but we decided that the little scratches and dings just added character to the car. Tim dubbed it the “Field Car,” a name that has stuck with the Maverick ever since.

Beatership wasn’t bestowed upon the Field Car all at once. Sometimes days or even weeks would go by without it acquiring a single new distinguishing feature. Then just when it seemed like progress had stalled, an opportunity for further customization would present itself, although I seldom recognized it as such until after the fact. The distinctive markings on the roof of the car for example came about when Tim and I were on our way to meet some friends and didn’t want to wait for a train. When we saw the lights start flashing at a crossing up ahead, we were sure we could safely beat the on-coming train. Indeed, we beat the train with a hundred yards to spare. It was the descending barrier that proved to be the real challenge. We actually did beat it… mostly.

Read the Rest of the Story >>>

I first wrote this article as a submission to Helium’s Marketplace. It was not chosen, so my loss is your gain, as I’m posting it here in it’s entirety. Note that I received no compensation for this article, but since I was hoping WinRAR would choose to publish it, I can’t say it is completely unbiased. That being said, every point in the article is absolutely true, and the benchmarks referenced are available for anyone to view.

*** Original Article Below ***

Two of the most popular file compression programs on the market today are WinZIP and WinRAR. The question that inevitably arises is, which is a better buy? The answer can be found by comparing the performance, price, and features of each.

Compression – the whole purpose behind using compression software is to shrink the size of files for more efficient storage and faster transmission over a network. Thus, how well a utility compresses files should be of primary concern to those needing to choose one. Many independent sites on the Internet consistently show that WinRAR compresses files more than WinZIP. There are a few exceptions with specific file types, particularly those that are already compressed in their native format, like mp3 files. These do not compress very much in any case by either WinRAR or WinZIP. WinRAR comes out the clear winner among most other, highly compressible file types, and the aggregate or overall measures generally show WinRAR on top. Supporting data can be found on wikipedia (Comparison_of_file_archivers), techarp.com (Compression Comparison Guide Rev. 2.0), and maximumcompression.com. [click to continue...]

As a Configuration Manager, I’m always looking for ways to improve the automation of the builds and deployments of my company’s applications. We use scripts to compile the apps, replace certain token strings with environment-specific values, and copy the new executable code out to the production servers. Ideally, we should not have to use seperate scripts when deploying to different run-time environments (development, integration test, production, etc.). We want instead to pass the target environment into these scripts, and use logic to determine environment-specific values. So I set out to create a Lookup Table to set the values according to the target environment.

I wanted to keep it simple so maintenance would be easy. I wanted it to run in a basic command shell (I use ‘bash’, but most other shells would work as well). UNIX and linux utilities like ‘sed’ and ‘awk,’ and xml parsers would have done the job, but they added complexity so I stayed away from them (although I do use ‘grep’). The listing below is a simplified version of what I came up with. It takes one parameter representing the target environment, and sets 3 variables: the target server, the target database, and a process user ID. It then prints the new values to the screen for verification (an optional step). The script we actually use at work also sets target directories, service names, and website urls, but this is enough to give you the idea:

Listing 1

#!/bin/bash

# Sets environment variables based on lookup string

# Environments: DEV = Development, QA = Quality Assurance,

# UAT = User Acceptance Test, PROD = Production

ENVIRONMENT=$1

# Set server addresses, database names, and user IDs.

line=`grep ^$ENVIRONMENT <<EOF

Env Server Database User ID

— ———————— ——— ———-

DEV dev.myapp.mybusiness.com myappdev devappuser

QA qa.myapp.mybusiness.com myappqa qaappuser

UAT uat.myapp.mybusiness.com myappuat uatappuser

PROD prod.myapp.mybusiness.com myappprod prodappuser

EOF`

set — $line

export AppServer=$2

export DataBase=$3

export UserID=$4

#

# Show environment settings:

echo “AppServer = $AppServer”

echo “DataBase = $DataBase”

echo “UserID = $UserID”

Sample run:

$ ./Lookup.sh DEV

AppServer = dev.myapp.mybusiness.com

DataBase = myappdev

UserID = devappuser

$

Using the Technique

Knowing how this script works is not essential to using the technique, as long as you realize that you can expand it by adding more values to the ends of the input lines, and creating enough values with the ‘export’ statements to accomodate the new values.

>>Read explanation and rest of article >>