From the monthly archives:

April 2008

As reported a few months ago, I wrote a series of articles for an anonymous Helium Marketplace publisher related to PC Optimization. Well, they bought one – an article written ‘on spec’ about the benefits of a paid-for registry optimizer. Since I had an inkling that the publisher is Uniblue software, I made sure to mention their product. I did not mention it in the article, but my choice for free registry optimizers is CCleaner. Aside from that omission, the article has valid information concerning features to look for in a registry cleaner. An excerpt follows. For a limited time, the article can be read in it’s entirety. Once Uniblue publishes it, it will be removed from Helium, since they bought exclusive rights to the content.


This content was removed per the purchase agreement.  The original article can be read here, with someone else’s byline.  They can do that because they purchased exclusive rights. –Jp

{ 0 comments }

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.

{ 0 comments }

My family and I recently took a break from Michigan’s cold and rainy early spring and vacationed in Arizona. We flew into Phoenix, rented a car, and set out for a number of destinations, all of which were great for R and R.

First we visited some good friends in Lake Havesu City. Matt and Tee showed us around Lake Havesu, and Matt particulary proved to be a fountainhead of knowledge about the town and it’s history. For example, Robert McCulloch of McCulloch Oil (think also, “Chainsaws”) basically founded the town, and he paid to move the London Bridge from London To Lake Havesu. Yes, the London Bridge. Matt and Tee were great hosts, and took us tooling around on the Colorado River and Lake Havesu in their boat. Most of us got our first glimps of California there.

After a few days we headed on down to Sierra Vista to visit my Dad and his two dogs, Bonnie and Lucky. We also met his friend (GF?) Marita. Sometimes we just lounged around and enjoyed the weather or swam in the pool, but we also went hiking in the neighboring mountains. Even though she is not a native to the territory, Marita proved to be delightfully knowledgable about the local flora, pointing out to us alligator cypress, manzanitas, prickly pear, and other species that grow there.

While we were staying with my Dad, we took a day trip to legendary Tombstone, where the gunfight at the OK Corral took place in 1881. The movies always portray the Earps and Doc Holliday as the good guys, standing up for law and order and trying to protect the town’s citizens from the outlaw gang known as the Cow-boys. The truth is, the Cow-boys (with the possible exception of Ike Clanton, an abrasive loud-mouth) were actually well liked by most of the towns’ people. They brought money into the town, whose principle business was saloon keeping, and they rarely carried out their lawbreaking in town.
On the other hand, the Earps were seen by many as opportunists, setting up gambling a establishment and using their connections with the law to play favorites. Nevertheless, the story is rich with drama, action, intrigue, and conflict that persists to this day. I was inspired to write an article, Surprising Facts About the Gunfight at the OK Corral. Check it out and let me know what you think.
Oh, and feel free to check out all the pix from the Arizona trip.

{ 0 comments }

April Foolin’

by joe on April 8, 2008

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...]

{ 1 comment }