Influenza A (H1N1) is like Computer Virus

This analogy will most likely make sense only for computer geeks. The post is excellent read and make sure you read the comments, too.

For those not familiar with molecular biology, DNA is information-equivalent to RNA on a 1 to 1 mapping; DNA is like a program stored on disk, and RNA is like a program loaded into RAM. Upon loading DNA, a transcription occurs where “T” bases are replaced with “U” bases. Remember, each base pair specifies one of four possible symbols (A [T/U] G C), so a single base pair corresponds to 2 bits of information.

Proteins are the output of running an RNA program. Proteins are synthesized according to the instructions in RNA on a 3 to 1 mapping. You can think of proteins a bit like pixels in a frame buffer. A complete protein is like an image on the screen; each amino acid on a protein is like a pixel; each pixel has a depth of 6 bits (3 to 1 mapping of a medium that stores 2 bits per base pair); and each pixel has to go through a color palette (the codon translation table) to transform the raw data into a final rendered color. Unlike a computer frame buffer, different biological proteins vary in amino acid count (pixel count).

To ground this in a specific example, six bits stored as “ATG” on your hard drive (DNA) is loaded into RAM (RNA) as “AUG” (remember the T->U transcription). When the RNA program in RAM is executed, “AUG” is translated to a pixel (amino acid) of color “M”, or methionine (which is incidentally the biological “start” codon, the first instruction in every valid RNA program). As a short-hand, since DNA and RNA are 1:1 equivalent, bioinformaticists represent gene sequences in DNA format, even if the biological mechanism is in RNA format (as is the case for Influenza–more on the significance of that later!).

OK, back to the main point of this post. The particular RNA subroutine mentioned above codes for the HA gene which produces the Hemagglutinin protein: in particular, an H1 variety. This is the “H1″ in the H1N1 designation.

If you thought of organisms as computers with IP addresses, each functional group of cells in the organism would be listening to the environment through its own active port. So, as port 25 maps specifically to SMTP services on a computer, port H1 maps specifically to the windpipe region on a human. Interestingly, the same port H1 maps to the intestinal tract on a bird. Thus, the same H1N1 virus will attack the respiratory system of a human, and the gut of a bird. In contrast, H5 — the variety found in H5N1, or the deadly “avian flu” — specifies the port for your inner lungs. As a result, H5N1 is much more deadly because it attacks your inner lung tissue, causing severe pneumonia. H1N1 is not as deadly because it is attacking a much more benign port that just causes you to blow your nose a lot and cough up loogies, instead of ceasing to breathe.

Researchers are still discovering more about the H5 port; the Nature article indicates that perhaps certain human mutants have lungs that do not listen on the H5 port. So, those of us with the mutation that causes lungs to ignore the H5 port would have a better chance of surviving an Avian flu infection, whereas as those of us that open port H5 on the lungs have no chance to survive make your time / all your base pairs are belong to H5N1.

So how many bits are in this instance of H1N1? The raw number of bits, by my count, is 26,022; the actual number of coding bits approximately 25,054 — I say approximately because the virus does the equivalent of self-modifying code to create two proteins out of a single gene in some places (pretty interesting stuff actually), so it’s hard to say what counts as code and what counts as incidental non-executing NOP sleds that are required for self-modifying code.

So it takes about 25 kilobits — 3.2 kbytes — of data to code for a virus that has a non-trivial chance of killing a human. This is more efficient than a computer virus, such as MyDoom, which rings in at around 22 kbytes

Immune System is like Spam Detector

From this post about diabetes. Read the whole thing, it is worth it:

The immune system is my body’s spam detector.

Basically, the immune system is a biological classification system. In the simplest terms, its job is to label entities found in the body as “pathogen” or “safe”– much like your email system labels email as “spam” or “eh, let it through.” The trick is, as with any good classification system, the world is not black and white to my immune system; every decision is a question of weights and probabilities, of likelihoods and comparisons. Is entity X a pathogen? Well, this molecular compound indicates maybe, but only if it co-occurs with another particular molecule that I don’t see here; let it by for now.

As with a spam detector, certain rules are innate, built in to my immune system. Any email with no subject and only a link is spam, no matter how many times I tell my spam detector it’s not. Likewise, certain bacterial mechanisms and molecular structures are known at birth by my immune system to be unwanted, and it doesn’t have to develop immunity over time.

Other rules, though, are learned; spammers are smart, and they keep changing to try to trick spam detectors. When all emails with “Viagra” and a link were marked as spam, spammers started sending “V1agra” and paragraphs of Old English text. Enough of those emails get labeled as “spam” by their recipients, and the spam detectors learn– both “Viagra” and “V1agra” are bad, and so is random text from old books. Similarly, my immune system might let certain pathogens through the first time around, but, seeing the ill-effects on other parts of the body, and seeing that the pathogen causes bad reactions, will train T-cells to look out for that particular pathogen, and to lie in wait if it ever comes back.

The problem is that sometimes classification systems get a bit overzealous and learn rules they shouldn’t. In spam detection, this means all my boss’s emails keep getting caught in the spam filter, and I miss important pieces of information. In immunology, this means I have an autoimmune disease, and my immune system keeps labeling my precious beta cells for destruction.

Why does this happen? Somewhere during training, the classification system learns rules that it applies to each new scenario, and it layers these rules to come up with a likelihood that the entity at hand is either good or bad. Is the email short? Does it have links? Is it addressed by name? Is the recipient in the to-line or BCCed? No single feature here gives a certain positive, but merely adds a weighting to the likelihood overall that the email is spam.

Similarly, in the immune system, maybe at some point I got a virus that had a certain peptide– GAD, let’s say, for the sake of example– and my body learned to look for GAD, and to assign protein sequences that had the peptide GAD with a certain weighting towards “pathogen.” Well, it just so happens that beta cells also have that peptide sequence. And it also just so happens that perhaps genetically, perhaps by the luck of the draw, perhaps by the individual variation that is possible in any biological system, I have too few NKT cells in my immune system. Or too weak regulatory T-cells. Or some minor imbalance of another kind. And the weighting against that one peptide doesn’t get out-weighed by some other factor of my beta cells. And my immune system labels my beta cells as pathogens.

And the rest is history. Once the beta cells are initially labeled, the attack begins. To complicate matters, over time my immune system, out of balance and unaware that it’s doing damage to its own body, begins to think it’s doing the right thing by killing beta cells. And so it starts to train itself based on other features of the beta cells. Then it’s not just the initial peptide that indicates pathogenicity, but others associated with beta cells and insulin generation likewise get weighted as likely indicators of an unwanted entity. And pretty soon every beta cell in my body has been tossed into the spam folder, and my body is incapable of producing the insulin it needs to regulate blood sugar, and I am a Type 1 diabetic.

Cloud Computing is like IKEA

There are plenty of analogies to cloud computing, such as utility, money, airline or office rental business.
Here is another one:
One of the most interesting and relatively nascent markets to emerge from the rise of cloud infrastructure is PaaS. While Infrastructure-as-a-Service forces a developer to set up, configure, deploy and manage an application from scratch, a PaaS hides all of this complexity, often allowing a software developer to simply upload application code to run. The platform handles all the gritty details that system administrators usually handle and lets the developer focus on the software. In the non-technical world you could compare this to buying a piece of furniture at IKEA, lugging it home and then figuring out how to put it together, vs. buying it online and having it delivered and set up in your living room.
 

Public Key Encryption is like Chocolate-In-A-Box

There is a great site from New Zealand called Computer Science Unplugged that is focused on teaching kids all about IT in an entertaining way. But it is a great resource for adults as well so if you always wanted to know what binary numbers are or how does compression work, check it out. 
Here is an explanation how does public key encryption work:

 

Microprocessor is like City

lntel has recently introduced Xeon 5600 microprocessor and here is (not very successful) attempt of their marketing department to use city analogy explaining the main features. Why I don't think it is good? Well, they use a lot of IT lingo (VMM, SSL transactions, cores, etc.) and if I am not familiar with it, then the analogy is not going to make me smarter. If I understand the IT language, then I don't need an analogy to get explanation of the main benefits of the processor. Anyway, still a worthy try. 

 

Cloud Computing is like Office Rental Business

 
 If you feel like using a new analogy for cloud computing, because utility, money or airline are not what you're looking for, here is an alternative:

Today’s cloud computing is very much like the office rental business long time ago. At that time, the office rental business got started and offered an option to these companies who had to build their own office buildings. Some people, especially the investors, might have asked, “Will all the companies rent offices rather than building their own in the future?” This is a very similar question as we ask, “Will all the companies rent data centers rather than building their own in the future?”

Let’s look at the “future” of the office rental. As we can find today, most SMB businesses rent office instead of building their own; most big companies own their offices. In fact, it’s mixed for big companies. They own some of the office buildings, and rent the rest. The criteria to build or rent is not capital investment, but how long it needs the space. The longer it needs it, the more likely it builds or buys its own.

So we can predict the future of cloud computing very much the same as today of office rental. Most SMB will use cloud service providers. Most big companies will continue to build and own their datacenters and infrastructure, but will leverage the cloud services on some short term projects.

Cloud Computing is like Airline

If you are tired of using the same analogy for cloud computing, such as this one or electricity, here is another one:
 
Consider that every nation has its own airline, even if it runs at a loss. It’s simply one of the trappings of nationhood. Airlines are part of the national infrastructure. In bigger countries–particularly free-market ones–a few competing airlines can survive. The U.S. has several competing brands, for example. They’re heavily regulated, but they compete.
In every country, there are other airline business models. Take Netjets, a timeshare approach to air travel. Or Air Ambulance services to transport patients on critical journeys. Or regional airlines that feed a larger national carrier. Or the military.
Like clouds, airlines need to interoperate, to ensure that luggage and passengers get where they’re going. Competitors will honor one anothers’ tickets to help out in cases of interruptions, and a set of agreed-upon routing codes and baggage tags make interoperability possible. Regulatory bodies fine airlines for violating service level agreements. Indeed, airports are simply the peering points of airlines, with frequent travellers having the equivalent of private peering.
The model works at the consulting and professional services level, too. We have self-service travel, but we also have travel agents, stitching together trips across multiple carriers and adding related services.
I like this analogy because clouds, like airlines, tend towards consolidation. There are economies of scale to be had, and both are essential to national security. While each airline must work with those of other countries–indeed, there are loose marketing alliances between airlines–every airline has an allegiance to its home country.

Cloud Computing is like Money

The most common analogy for cloud computing is that it is like utility, although I would argue that cloud computing is the analogy in itself already...
 
Here is a new one, and quite good in fact:
Take the monetary system. In his address to the annual RSA Conference on computer security held in San Francisco on March 2nd, Art Coviello, president of EMC’s security division, noted how civilisation started with barter, then invented coins to make money more portable—even though people still had to carry their wealth around with them physically. The first step in the virtualisation of wealth came with the introduction of paper money. These promissory notes, with no intrinsic value, forced people to deal with the concept of attestation—certifying that something is genuine. And with that, the advent of financial instruments such as stocks, bonds and mutual funds created ways of sharing wealth—so that when one person wasn’t using it, another could. Today, virtual money dominates the money supply. In much the same way, virtual processing will one day dominate the computing supply.

Relationship is like Operating System

Media_httpk9zwfileswo_zfngf
For geeks who understand computers better than life, this explanation of relationship in IT terms can come handy.
 
Here is an excerpt:
My partner and I see our relationship as running on an operating system.
 
When all is running smoothly, we barely notice it. It efficiently handles resource allocation and quietly runs applications (dance lessons, friendship development, work life). It operates as an operating system does on a computer. Without the operating system, the relationship has nothing on which to run.
 
How to Install a Relationship OS This will vary from couple to couple. Perhaps it starts with defining what you'd like the scope of the relationship to be. Later into the relationship, maybe it's a relationship health checkup. Defining what applications you'd like to run (a year from now, five years from now, fifty years from now) are all potential starting points.
 
 And here is a very good advice from the author:
 
"If you decide to go the open source route, make sure your partner knows it."

 

 

Computer is like Factory

Analogy between computer and factory is nicely described here.
 
The computer consists of the hardware (CPU, RAM, storage and all other devices) and the OS (processes and data). What do these correspond to in the factory? The CPU is a control booth with a phone and the RAM is a special waiting place for the workers. The storage device is a dormitory and the other devices are the rest of the machinery used in the factory.
The dormitory is occupied by the men and the women. Seeing as men like to be active they are the processes, the ones doing different tasks, while the women hold the instructions. They are the data stored in files. So, the women give instructions and the men do what they are told.
Besides these we have two more components.
The user (the person operating the computer) is the factory manager. Software applications (programs such as web browser, media players and others) are the external consultants.
 
The analogy description goes further, so read the rest in the original post.

DLM Memory is like Cave Echo

Before there was RAM, we had DLM ( Delay Line Memory). There were no semiconductors in the 60s so clever guys had to figure out a different way of storing data. This post in MAKE provides very good explanation and also an analogy for those of us who would not understand the technical lingo:

If you had a hard time remembering things for very long, and happened to live in a cave, you could just shout out what you didn't want to forget, and a few seconds later you would hear an echo to remind you. Of course, the problem with this is that an echo doesn't stick around for long, so you would have to shout again every time that you heard the echo, so that you could remember again in a few seconds. Assuming you could keep this up, you would never forget your idea. Of course, that would get really tiring after a while, so you would be much better off just writing it down.