Jeff Vannest's Weblog

May 18, 2005

Where Does Quality Come From? (The Stunning Conclusion Continued)

Over the past couple of weeks, I have been building a case for the source of quality. The first in this series stated, "I am the only standard of quality." I later qualified that the individual (any individual, not just me), is the source of quality, and that the world is broken down into things (subjects) and ideals (archetypes). In the second part of this conclusion, I will explain my own thoughts on how individuals use things and ideals to define, experience, and scale...

Read entire article >>

Posted by Jeff Vannest at 02:37 PM | Comments (0) | TrackBack (0)

May 15, 2005

Where Does Quality Come From? (The Stunning Conclusion)

I finished last week's article with these words, "Having fully shown that I am the only standard of quality, read next week's stunning conclusion." With words such as those, I'm certain you expect me to start this article with some kind of recantation. You're wrong. I still maintain that I am the only standard of quality, but not in the way you might think because I also maintain that you are the only standard of quality. I will explain. First, let me rewind for around 2,400 years. Plato's...

Read entire article >>

Posted by Jeff Vannest at 12:15 AM | Comments (0) | TrackBack (0)

May 12, 2005

Where Does Quality Come From? (A Preposterous Introduction)

So, I was writing this software design specification today and thinking to myself, "This is a *really* great design." I got all goose-fleshy, patted myself on the back, and thought of all the ways that my document showed quality. It...uh... It has…uh… I had to face the truth: I don't know why I think this document is any good, I just do. Where does quality come from? If I add chocolate chips to cookie batter, it makes for better cookies. Maybe quality is an ingredient, something added...

Read entire article >>

Posted by Jeff Vannest at 08:38 PM | Comments (0) | TrackBack (0)

April 29, 2005

How to Care for Your New LIMS Consultant

Well, you've really gone and done it now, haven't you? You just had to have a new LIMS consultant. If you are a veteran of the LIMS consultant-owning scene, you surely can recall the excitement and enthusiasm you felt when you brought that first one into your office or quality unit. If this is your very first LIMS consultant, there may be just a bit of, "What have I done?" anxiety about this major moment in the life of your organization. Well, you should be just a bit anxious! Caring for a LIMS...

Read entire article >>

Posted by Jeff Vannest at 07:31 PM | Comments (0) | TrackBack (0)

April 25, 2005

Tools and Methodology

I had an interesting discussion with John about tools and methodology. The discussion centered on the question, "Does the methodology choose the tool, or can a tool choose the methodology?" I had never seriously considered this question, but my gut reaction was that tools - software or hardware - should have some bearing on methodology. I will take this time to consider the question more thoroughly. First, let me clarify the terms: By "methodology", I mean the philosophy by which a person or...

Read entire article >>

Posted by Jeff Vannest at 08:44 PM | Comments (0) | TrackBack (0)

April 08, 2005

Validating Email

In the past several years the email client has become central to the user desktop, and for good reason. My email program (Outlook) contains more than just electronic correspondence; it has contact information for co-workers and customers, work and project calendars, personal reminders, and lots of other mumbo-jumbo I usually can't recall without some kind of help (like my mom's birthday). However, while LIMS users clamber to receive system notifications and electronic records through email,...

Read entire article >>

Posted by Jeff Vannest at 10:35 AM | Comments (0) | TrackBack (0)

April 01, 2005

Identifying files by Digital Signature

In the past, I've looked at how digital signatures can be used to identify textual and binary files. Today I'd like to explore the specifics of how a company can use digital signatures to organize and identify files. A file's digital signature, which is sometimes called a checksum, is actually a cryptographic hash function. To break it down, a hash function (or simply "hash") is a computer subprogram that converts a large amount of input into a smaller output, and the steps used to...

Read entire article >>

Posted by Jeff Vannest at 09:36 AM | Comments (0) | TrackBack (0)

March 25, 2005

Failure, Failure, Burning Bright

Every successful consultant has to sit and wonder when that great, next failure will occur. You know the one where you tell a customer you can do this one thing only to find you can't deliver because the technology isn't ready, resources didn't pan out, or the vision was too grand to fit into the timeline or budget. See, great consultants are like Rock Stars; they get paid handsomely to put themselves out for everyone to see, then bear the brunt of the ridicule when they trip on the stairs and...

Read entire article >>

Posted by Jeff Vannest at 03:41 AM | Comments (0) | TrackBack (0)

March 18, 2005

Identifying Custom Code - Binary

Last week I presented a scenario wherein the correct version of custom code for a CFR Part 11 LIMS system had been lost, which presented the opportunity to review several methods of re-identifying custom code that was textual (meaning human readable). Let's now look for a way to reliably identify binary code in that same scenario. Binaries files are not meant for the eyes of mere mortals. This is advantageous from a system perspective because computer programs can use characters and symbols to...

Read entire article >>

Posted by Jeff Vannest at 09:05 PM | Comments (0) | TrackBack (0)

March 15, 2005

Identifying Custom Code - Textual

Eventually in the lifecycle of every project someone will look at a piece of custom software and think to themselves, "Is this the right version, or did I put the new version on my other computer?" While it seems silly for a company that likely spent thousands of dollars on analyzing, developing and validating that particular piece of software, this still happens in even with the best companies. Let's look at some ways a company can re-identify a piece of custom code that is textual...

Read entire article >>

Posted by Jeff Vannest at 06:30 PM | Comments (0) | TrackBack (0)