Tag Archives: 25 Coding Techniques

Learn to Code and Decode like Q

UPDATE: Dr. Birx Confirms Anyone Who Dies WITH Coronavirus, Regardless of Any Underlying Health Condition, is Being Counted as a COVID-19 Death

Basically a big crime on humanity made by very sick people.

There is a big difference between dying with the virus and from the virus.

How to discover more on the Q boards:

  1. Mouse over abbreviations.
  2. Follow blue, numbered links to 8chan or 4chan boards.
  3. Click on “Answers” button in the bottom right of the post for suggested decoding.

Find Q here:

https://qanon.pub/

https://qntmpkts.keybase.pub//

https://qanonmap.bitbucket.io/

PROBLEM > REACTION > SOLUTION

Bill Gates (Rockefeller puppet) plays a central role in the solution to COVID-19 outbreak. Beyond financial gain, beyond voting manipulation, are there other implications to be considered?

Specifically: MODERNA is one of the Vaccine makers he is backing. But they are working on a completely NOVEL solution using mRNA and CRISPR technology.

This wreaks of rushing something dangerous in under the duress of a crisis without considering the consequences.

Here is an article by James Clapper (of all people) citing CRISPR based attacks on DNA as one of the top threat matrices to the country’s national security:

https://http://www.technologyreview.com/2016/02/09/71575/top-us-intelligence-official-calls-gene-editing-a-wmd-threat/

Anon, please expound upon the unanticipated consequences of approving this treament, and how it could be weaponized in this crisis?

My first thought is to slip in something else which creates another health crisis….and then have the solution available to that problem you created….cycle and repeat until all money depleted from accounts spent on solutions.

—————

The Coronavirus is not a living organism, but a protein molecule (DNA) covered by a protective layer of lipid (fat), which, when absorbed by the cells of the ocular, nasal or buccal mucosa,(mucous of the cheek) changes their genetic code, (mutate) and convert them into aggressor and multiplier cells.

As the virus is not a living organism but a protein molecule, it is not killed but decays on its own. The disintegration time depends on the temperature, humidity and type of material where it lies.

This protein is very fragile; the only thing that protects it is a thin outer layer of fat. That is why any soap or detergent is the best remedy, because the foam CUTS the FAT, which is why necessary to vigorously rub for 20 seconds or more, to make a large quantity of foam). By dissolving the fat layer, the protein molecule disperses and breaks down on its own.

HEAT melts fat; this is why it is recommended one use water above 25 degrees Celsius (77 degrees Fahrenheit) for washing hands, clothes or other surfaces. In addition, hot water makes more foam and that makes washing more effective.

Alcohol or any mixture with alcohol over 65% DISSOLVES ANY FAT, especially the external lipid layer of the virus.

Any mix with 1 part bleach and 5 parts water directly dissolves the protein, breaks it down from the inside.

Oxygenated water helps long after soap, alcohol and chlorine, because peroxide dissolves the virus protein, but you have to use it pure and it hurts your skin.

Since this “virus” is not a living organism like bacteria; Antibacterial soaps containing antibiotics cannot kill this protein, but will rapidly effect disintegration of its structure.

It is advised to not shake used or unused clothing, sheets or cloth. While it is glued to a porous surface, this “virus” is inert and will disintegrate after 3 hours on porous fabrics , 4 hours on copper, because it is naturally antiseptic; and wood, because it removes all the moisture and does not allow the “virus” to become airborne, 24 hours on cardboard, 42 hours on metal, and 72 hours on plastic. Using feather dusters or shaking cloth, the “virus” molecules can float in the air for up to 3 hours, and can be inhaled embedding in the mucus membranes of the nose.

The “virus” molecules remain very stable in external cold, or artificial as air conditioners in houses and cars. They also need moisture to stay stable, and especially darkness. Therefore, dehumidified, dry, warm and bright environments will degrade it faster.

UV LIGHT on any object that may contain it breaks down the virus protein. For example, to disinfect and reuse a mask UV Light is perfect. Be careful, it also breaks down collagen (which is protein) in the skin, eventually causing wrinkles and skin cancer.

The virus CANNOT penetrate healthy skin.
Vinegar is NOT useful because it does not break down the protective layer of fat.

Spirits (whiskey) or vodka is ineffective as the strongest vodka is 40% alcohol, and you need 65%.

A good mouthwash can be substituted if it contains at least 65% alcohol.

The more confined the space, the more concentration of the “virus” Conversely the more open or naturally ventilated, the less.

We all know we have to wash our hands before and after touching mucous, food, locks, knobs, switches, remote controls, cell phones, watches, computers, desks, TV, etc. and especially after using the bathroom.

Hands dry out from constant washing, because these viral molecules can hide in the micro cracks. So it is advised to use a thick moisturizing cream the thicker the moisturizer, the better. Also it is a good idea to trim ones fingernails so that the “virus” does not hide under them.

Source:

Fall Cabal

Fair Use Notice: Images/logos/graphics on this page contains some copyrighted material whose use has not been authorized by the copyright owners. We believe that this not-for-profit, educational, and/or criticism or commentary use on the Web constitutes a fair use of the copyrighted material (as provided for in section 107 of the US Copyright Law).

Kirk Lafler Shares 25 Coding Techniques!

25 Best Practice Coding Techniques for SAS Users By Kirk Paul Lafler, Software Intelligence Corporation

As SAS software becomes increasingly more popular, best practice coding techniques and guidelines become ever so critical. SAS software provides users with a powerful programming language for accessing, analyzing, manipulating, and presenting data. This tip addresses useful coding techniques for all operating system platforms.

  • After running a SAS program, immediately review the SAS log for notes, warnings, and error messages. Avoid turning off SAS System options that turn off SAS log notes, messages, and warnings.
  • Turn on the SOURCE2 SAS System option to display included source code on the log. Best practice coding techniques should mandate inclusion and display of any and all information that is available during a SAS session.
  • Considering procedures like PROC SQL and PROC REPORT for code simplification. Because multiple processes can be frequently accomplished in a single procedure step, I/O may be reduced.
    When a DATA step or PROC can do the same job, consider using procedures whenever possible. Procedures are tried-and-proven throughout the world’s SAS installations, testing requirements is considerably less.
  • Create user-defined format libraries to store formatted values in one place. User-defined format libraries have the added advantage of making programs easier to maintain since formatted data values are not hard coded.
  • Include RUN statements at the end of each DATA or PROC step (to separate step boundaries) to print benchmark statistics on the SAS log immediately following each step.
  • Document programs and routines with comments. In addition to the value associated with explaining program logic, comments should provide important information about complex code and logic conditions in a program. This helps to document important program processes as well as minimizes the learning curve associated with program maintenance and enhancement for other users.
  • Assign descriptive and meaningful variable names. Besides improving the readability of program code, it serves an important element in the form of documentation.
  • Construct program header information to serve as program documentation for all programs. The following example illustrates the type of information that can be added so others have a useful documented history.
  • Simplify complex code and operations into smaller, more manageable parts. By splitting complex code into two or more programming statements, a program becomes easier to read as well as more maintainable.
  • Specify SAS data set names when invoking procedures to help improve documentation efforts as well as preventing an incorrect data set from being processed.
  • Utilize macros for redundant code and enable autocall processing by specifying the MAUTOSOURCE system option.
  • Create macro libraries to store common macro routines in one place.
  • Create permanent libraries containing information from daily, weekly, monthly, quarterly, and annual runs. The type of libraries consists of scripts, SAS programs, SAS logs, output lists, and documentation of instructions for others to follow.
  • Create views based on user input to simplify and streamline redundant, complex and/or burdensome tasks. Consider creating views in a central view library to support maintenance and documentation requirements.
  • Code for unknown data values. This will prevent unassigned or null data values from falling through logic conditions.
  • Store informats, formats, and labels with the SAS data sets that use them. Informats, formats, and labels should be stored with important SAS data sets to minimize processing time. An important reason for using this technique is that many popular procedures use stored formats and labels as they produce output, eliminating the need to assign them in each individual step. This provides added incentives and value for programmers and users, especially since reporting requirements are usually time critical.
  • Construct conditions that would render data unusable and abort (or end) the program. This prevents unwanted or harmful data from being processed or written to a data set.
  • Test program code using “complete” test data particularly if the data set is small or represents a random sample of a large data set.
  • Set OBS=0 to test syntax and compile time errors without the risk of executing any observations through a DATA or PROC step.
  • Use the PROC SQL VALIDATE clause to test syntax and compile time errors in PROC SQL code.
  • Specify the NOREPLACE system option to prevent permanent SAS data sets from accidentally being overwritten while writing or testing a program.
  • Take advantage of procedures that summarize large amounts of data by saving and using the results in order to avoid reading a large data set again.
  • Add options that are frequently used into the SAS configuration file. This eliminates the time and keystrokes necessary to enter them during a SAS session.
  • Add statements that are frequently used into the SAS autoexec file. This eliminates the time and keystrokes necessary to enter them during a SAS session.
  • Source: 25 Best Practice Coding Techniques for SAS Users By Kirk Paul Lafler, Software Intelligence Corporation