Hello! Arnie here. This is a two-parter. The first, a simple explanation about a complex phenomenon: gene expression. The second is wisdom from one chapter of a wonderful book about a horrible topic: genetically engineered biological systems (food crops).
PART ONE
I learned about the following gene expression tidbit back in 2018 when I started studying Darwinism for nine months. I'm not a scientist, and I typically hope to find the Joe 6-pack explanation of technical matters. We’re going to look at 2 diagrams re-imagined by me because I forget what book they were in!
But first, a third diagram showing what common folk are given to believe is the way genetic engineering takes place. The lab pros snip out part of a DNA section, and then glue it into some other strip of DNA.
For this exercise we're going to deal with three bodily traits: blue eyes, stomach pH, and toe hair. My first diagram shows the common understanding of what they do: there's a section of the DNA strand that governs blue eyes, and you can snip that out and put it somewhere else you want blue eyes.
In the second example, look more closely at the colors in the little blocks. They are stacked 3 high to symbolize codons. Codons, also called triplets, are considered the minimum size unit composed of base pairs that convey some kind of instruction. The all-blue codons pertain only to blue eyes. However, the 3‑colored codons not only pertain to blue eyes within the supposed “blue eye segment”, but there are a few others outside the snipped region. The scattered 3‑color codons are also involved in other characteristics ─ they are multi-purpose. Furthermore, some of these multi-purpose codons affecting the two other characteristics lie within the contiguous purported “blue eye” sequence of codons.
Hmmm. Not so simple anymore. This is incredibly complex science-y stuff. But, as unschooled as I am, I still have the vague feeling that someone is LYING about what THEY claim to be capable of, in the modifying of living organisms.
PART TWO
Now we will consider information from the 2015 book Altered Genes, Twisted Truth How the Venture to Genetically Engineer Our Food Has Subverted Science, Corrupted Government, and Systematically Deceived the Public by Steven M. Druker. This 300-plus pager is as close to a whodunit as I've ever seen, for a science book, and guess what ─ we're the murder victim. It's the story of how powerful interests cloaking themselves in science foisted upon the public dangerously mutated food crops.
You've probably seen several polls over the years where the public was asked if they wanted GMO food in their grocery stores and the typical result was 90% saying “hell no”. After GMO food was just pushed through anyway ─ thanks to the FDA doing nothing to ensure safety ─ we then had battles about labeling the poisonous filth. [Sidenote: FDA annual budget: $6.5 billion].
Did you know that a pig or a cow, if offered two food troughs ─ one natural corn and the other GMO corn ─ will invariably choose the natural food. Kinda makes us dumber than a [>insert animal here<], dontcha think?
We will be learning from Chapter 11 of the book, comparing bioengineering practices to those of computer software development and implementation. First, please view the table of contents for this book. Many of the themes could be superimposed upon our current COVID $camdemic debacle. You can see the author had concerns which are fully relevant today.
The informational characteristics of DNA are often compared to computer software and data. However, author Druker explains in detail how the practices used in genetic bioengineering are far less careful and disciplined compared to computer engineering, or ─ he adds ─ to any kind of engineering!
As complex as computer software might become, its overall design purpose, and its constituent elements, remain discoverable, analyzable, and fixable because the engineers involved created it all in the first place.
This is de facto not true of the bioengineers. Granted, they have made fascinating discoveries, however, there continue to be new shocking revelations throughout the years. At this stage we might say they are like Piper Cub mechanics modifying a Boeing 777X ─ or worse.
Software engineers routinely avoid what they term “spaghetti code” ─ and you immediately intuit why ─ it’s a tangled mess. Drucker explains that what is more desirable is what’s cutely termed “ravioli code” ─ discreet packets arrayed end to end in a linear fashion. In fact, most computer software operations are linear in structure. Mother Nature’s software is spaghetti within spaghetti on top of spaghetti.
Highly advanced computers can utilize parallel processing, and you've no doubt heard of this. In this configuration syncing the two processing streams is critical, and if the syncing becomes too complex, the desire efficiencies are lost because the system bogs down regulating itself.
In living organisms, cellular and metabolic communications natively use parallel processing and are able to whizz right along 24/7 with no problem. Additionally, these parallel information sharing tracks can number well over two.
In 2006, a research group reported a code superimposed on the amino acid code, that contributes to regulating information. Soon after others came to light and by the end of 2013 seven additional regulatory codes had been discovered, and their description published in the journal Science in December (The Hidden Codes that Shape Protein Evolution).
It is here we will mention combinatorial inflation. We've all seen a briefcase lock with three dials 0 to 9. That small gizmo is capable of 1000 number combinations. With five dials you've increased your variety to 100,000 and with 10 dials to 10 billion. We’re conceiving each dial as a codon, referencing the 8 parallel regulating streams mentioned above plus adding the two that we suspect haven't been discovered yet. Even if you halve the numbers for each dial, a five dial configuration yields 3,125 possible sequences (five codons, five parallel regulators).
We've all used passwords and typically own far more of them then we'd wish. So, we know that if your password is M4p6&w6vCp7Vek, then M4p6&v6wCp7Vek won't work. Just because something has 3,125 possible sequences doesn't mean that four or five of them are close enough to be OK.
In 2014 an Indiana University team announced the identification of thousands of “new genes, transcripts, and proteins” in the fruit fly ─ one of the most analyzed genomes in history. Furthermore, of the 1,468 discovered, 536 were in zones officially regarded as gene free.
Sounds like someone thought they washed the whole car but later discovered they missed a spot.
GLYCANS. This is the last thing I read about during my Darwinism binge, and it set my head spinning. Glycans are polysaccharides attached to cell surfaces.
The glycocalyx, also known as the pericellular matrix, is a glycoprotein and glycolipid covering that surrounds the cell membranes of bacteria, epithelial cells, and other cells.
They are now known to be a whole other system of cellular and metabolic communication heretofore completely unknown. In my archive notes about this I wrote in the margin “This form of communication is so complex that scientists are kind of whining about it!”
This is the bacteria Bacillus subtilis, showing the glycocalyx shag carpet covering:
Here is a magnified image of the polysaccharides’ filamentous array:
Here is an artist’s rendition of the glycan forest you would see in Honey, I Really Shrunk the Kids:
Here is a screen shot of a technical guide to glycans. I have no clue what any of it means:
Computer programs are subjected to a great deal of test testing before release, and then public usage becomes another test in itself ─ you've heard the term beta testing. Defects and difficulties always arise and sometimes upon being addressed create further tangential problems. A rule of thumb is that 20% of product cost is in development and pre-release testing, and an additional 50% is incurred post-release due to further testing and correcting.
Earlier, computer programming was notorious for needing corrections because one element of the total program created glitches in another element. Insulating those elements, one from the other, has been important in the advancement of computer software.
The regulatory rigor of testing computers deemed life-critical is even more involved. Think of the FAA and flight system software, or the FDA and medical device software involving radiation. Plus, producers in such markets are motivated toward accuracy outside of the regulatory framework, to reduce liability and maintain market reputation. Later changes ─ even small ones ─ are treated as completely new systems, needing full testing and disallowing the doctrine of “substantially equivalent”.
In the US, the testing of GE [genetically engineered] crops is virtually nonexistent. They have been classified “substantially equivalent” to natural crops (and this what most of Druker’s book is about). More stringent testing in the EU is still only short-term ─ maybe 90 days ─ which is but a brief moment in the life of a complex organism.
But when faced with radical alterations to the most complex and intricately interconnected information systems on earth, made in a haphazard manner by people who don't understand the system's rules and contours and can barely begin to fathom the full effects of their interventions, regulators have for years allowed the resultant food-yielding organisms to be marketed as long as a superficial case can be made that they're substantially similar to their conventional counterparts -- despite extensive evidence that such radical tampering can render the food toxic. And in the United States, such equivalence is automatically presumed, with no requirement for even the most superficial of efforts. [Druker][Ed. food crops, not food animals]
So, why so picky with computers? Here’s one example:
The European Space Agency took ten years and $7 billion to build Ariane 5, a giant rocket which was to put two 3-ton satellites into orbit. Just 39 seconds after launch, the entire device exploded into a million fragments, destroying a $500 million cargo.
The cause of this was a small computer program trying to insert a 64-bit number into a 16-bit space. The error arose from using code from the earlier Ariane 4, which had worked just fine, but was not compatible with the new system.
Now for an example of biotech fumbling the ball:
In 1989 a strange malady began spreading across the land in a limited yet notable fashion. It was soon labeled EMS (eosinophilia-myalgia syndrome).
During that year, thousands of people throughout the United States experienced the onset of severe muscle and joint pain accompanied by swelling of the legs and arms, extensive skin rashes, and significant breathing difficulties. Some also developed congestive heart failure, while others succumbed to complete paralysis, with a respirator required in order to breathe. But even if they avoided these latter two outcomes, most of those with the basic set of symptoms suffered greatly. [Druker]
Within a fairly short time epidemiologists discovered the commonality among the sufferers was the use of L-tryptophan. This was the start of another mystery: why was this happening now? There were numerous brands of L-tryptophan being consumed, and no particular one was up for blame. The investigators then looked at the [far fewer] source manufacturers of L‑tryptophan. It then became clear that the problematic cases arose from the L-tryptophan produced by Showa Denko KK, Japan’s fourth largest chemical company and the biggest supplier of L-tryptophan to the United States.
L-tryptophan is manufactured by inducing bacteria to produce the substance via fermentation in large vats, followed by a filtering process to isolate the product. It was soon learned that Showa Denko head started using genetically modified bacteria which produced the L‑tryptophan at an elevated rate.
[Please note: The L-tryptophan story thus far is a textbook example of what epidemiology is supposed to be ─ contrasted with the fake epidemiology we have recently been subjected to ─ whereby THEY declare an epidemic based on nothing, and then declare martial law rather than say “take two aspirin and call me in the morning”].
Now the L-tryptophan story becomes simply disgusting. The FDA, following the desires of the cabal, was only worried that the Showa Denko manipulations would give a bad reputation to bioengineering ─ at the time a young darling of the scientific world. Furthermore, this is only a year after the introduction of Prozac, and L-tryptophan is well-noted for “calming the nerves”.
So, the FDA outlawed ALL L-tryptophan. This yielded multiple benefits to the agency: 1. Play-act like THEY care about public health. 2. Put forth an example of why THEY should come down hard on all health supplements – long part of their wish list. 3. Protect the reputation of the fledgling bioengineering industry (notice I said industry, not science). 4. Protect the interests of their sugar daddy and overlord, Big Pharma.
Oh, how this reminds us of the tug of war between HCQ and Ivermectin versus Remdesivir and the jabs!
By the way, it appears L-tryptophan is again available, and was only banned for about 10 years. I would assume Prozac and its ilk were such a success that L-tryptophan didn't win, place, or show, and was no longer deemed a competitor. Several years ago, a friend told me about her friend who was depressed, and knew the full story of Prozac-type drugs, and how ineffective and dangerous they were, but took them anyway because she “had to do something”. That's powerful stuff.
Software engineers create programs, whereas bioengineers merely tamper with existing programs ─ these being living organisms.
Software engineers make revisions to programs, whereas the bioengineers’ efforts are more akin to hacking.
This kinship is especially striking in light of the fact that in both hacking and bioengineering, the inserted segments of code act like a virus. Not only do they gain entry by breaching the program's defenses against foreign incursions, once inside, they operate independently of, and inimical to, the aims of the invaded system -- while commandeering its resources in order to do so. [engineer quoted by Druker]
Another engineer quoted by Druker:
When I started to investigate the technology, I wanted to discover how it stacked up against software engineering, so I began questioning computer professionals. Over the ensuing years, I've talked with many; and once they're apprised of the basic facts, they invariably react with astonishment -- usually accompanied by a substantial dose of indignation. One astounded programmer exclaimed, "That's like taking a snippet of code from the program in a toaster oven and splicing it into an airplane guidance system -- and yet assuming that nothing will be disturbed."
We now see endless writing about the COVID jabs, and each week a different take on the matter. The spike protein remains in the muscle …no, the spike protein travels into the bloodstream. The spike protein collects in the ovaries …oh yeah, and it bypasses the blood brain barrier. The jab doesn't change your DNA …no, wait, the jab changes your DNA. If Bill Gates changes your DNA, he's going to own your body...
Let's set this aside and look at something fully established. Corn was genetically modified, with the provocative narrative that it would be immune to pesticides and/or herbicides, which would solve all our problems. Roundup ready crops. Now after THEY have sold a gazillion gallons of glyphosate, the dastardly poison is ubiquitous ─ it's detectable in everyone's body and is now admitted to cause Cancer.
When CNN admits something inconvenient to the cabal you know you're in deep doodoo. The foregoing comparison between software engineering and genetic modification points up two things, in my mind. THEY care that computers function properly ─ especially since they are to be one of the central tools of our enslavement. The perplexing lack of rigor in the management of experimental gene altering technology is most probably due to the following:
I'm sure there will be some readers of this post who will criticize me for not knowing exactly what I'm talking about. Fair enough. Just hold that thought the next time you're fed or injected with some substance resulting from artificial genetic damage.
Thank you for visiting, and please tell others about the wonderful writers active on Substack these days. LIAR$$WORLD has a free subscription so you can pay-subscribe to other Substackers who have greater expenses than me. If you have a question about this post, here is a point of contact.
Absolutely brilliant! Thank you making a complicated subject fascinating!
Well Done! I love & appreciate a Laymans breakdown of complicated stuff!
Btw, I was sent here from Patrick Jordan/ Vaccinefraud.com....For a reason.
So I subscribed cuz I like what I see :)