There's nothing else I can do. / 내가 더 할 수 있는게 없어.

There's nothing else to do. / 더 할 일은 없다.

If nothing else, / 없다 하더라도,

What else do I have to prepare? / 내가 더 뭐 준비해야 할 것이 뭐지?

What else can explain it? / 달리 설명이 안되지.

Playlist posibil :

01. Creeping Death
02. For Whom The Bell Tolls
03. Ride The Lightning
04. Harvester Of Sorrow
05. The Unforgiven
06. Leper Messiah
07. ...And Justice For All
09. No Remorse
10. Fade To Black
11. Master Of Puppets
12. Whiplash
13. Nothing Else Matters
14. Sad But True
15. One
16. Enter Sandman

Encore:

17. Last Caress
18. Motorbreath
19. Seek & Destroy

Asa fuse-n '99 , long long time it was , heh ?

Real joy to see you back here tonight . Nothing else matters.

Not having one is not a bad thing, well I think that’s the best thing you could ever do in life is not have an expectation at all , not from anybody as the more u have it the less u get it , the less u get the more sad you are and it leads to frustration and also depression, irritation, and at last hatred for that person, it might lead to some other things as well, like having a fight, or loosing confidence in yourself as well as people around you, SO I would suggest rather then being  weak by loosing it , why not , not have it all, hey I am not talking about confidence but EXPECTATIONS.

Well there is another category of expectations you have and these are the ones you have from you yourself, they are the ones who are the most dangerous ones, if they are satisfied then fine good and a happy story but what if they are not. that’s a very demanding situation you are in, the ones you have from yourselves and they are not satisfied , that’s pathetic man, that’s ridiculous, you are good for nothing , well ,well, that’s the story we tell our self and then at the most try to commit suicide, that’s the extreme only a minor percent of us do that but yes we do. So here’s a solution for that, why not have another set of expectations before you if the earlier ones are not satisfied,

There something I studied in school these were called logic gates, they actually gave us options in a problem as to how can we solve them the key words were IF , THEN, ELSE, XOR , NOR , etc. But in the end we always ended with the right answer to the problem , that is how our life has to be like, any situation you are in ,any problem you have  in life there is always a solution for that , the world does not end if you have failed in an exam, if you haven’t got a good job, you wife runs away with your best friend, your fourteen year old daughter is pregnant and your son is doping around, well what’s the problem man, live your life, give them time, take your chances, take your son to a doctor, try helping him out not because you think he needs help but because he actually needs one, there no escape to being worried, but there a solution for that. Your daughter , well god help her, this age and pregnant , well what can u do now, either get it killed but that’s against humanity, but if she delivers the child she is going to transform into a women, which unknowingly she has already , your wife , oh she is found someone better and its your turn now, a second chance WINK. Try it the logic gates work, apart from fun and sarcasm , it actually works. TRY it .

You'll be finding in this blog, regular information on the latest technologies and technics on every domain related to the Survey Job both on Land and Offshore.

If you ever have a suggestion on a article or a commentary, feel very welcom.

Wish you good reading.

C.B

i'm waiting for my body to lead the way

.

Dizem que à 3ª é de vez. :)

Portanto para este primeiro post posso completar o titulo do blogue assim:

IF blog.succeed() THEN continue

ELSE

blog = new Blog()

DO  blog.WritePost() WHILE TRUE

A little late on this but, the Everything Else Exhibition will host it's opening exhibition today ( Thursday, June 19th) from 6 to 8PM at the Franklin Parrasch Gallery in New York City.

No worries though the exhibit will run until August 30, 2008.  The gallery will house works from such artist as Jason Adkins, Bryan Bowie, Anthony Campuzano, and KAWS just to name a few.  As some of you know KAWS is well known for his vinyl creations and the exhibit will feature a 4 foot KAWS Companion and 50 x 60 KAWS interpretation of the Smurfs.

Visit Franklin Parrasch Gallery website for more info and location.

-"c.h.a.s.e."

Selon que des variables aient certaines valeurs ou non, le programmeur peut décider de créer une nouvelle variable, extraire une ligne d'observation, etc.

SAS propose plusieurs syntaxes pour exprimer ces conditions.

• Dans le data step et la procédure SQL, pour extraire un sous ensemble de records sans autre action le WHERE est probablement le plus adapté. De plus, dans d'autres cas que le data step et la PROC SQL l'option WHERE est aussi utilisable (PROC SORT, PROC FREQ, ODS OUTPUT...).
• Sinon, dans un data step, on rencontre le IF et le SELECT et dans une procédure SQL, CASE WHEN est disponible. 

Ce sujet sera divisé en 3 articles à commencer par la syntaxe du IF. Dans huit jours, le prochain rendez-vous sera consacré au SELECT. Enfin le dernier article de la série s'intéressera au CASE WHEN.

1. Le minimum ou presque

"S'il pleut, alors je prend mon parapluie, sinon, je le laisse au bureau." Dans cette phrase, on repère trois mots : si, alors, sinon. Traduisez par IF, THEN, ELSE. C'est trois mots, version anglaise, forme la syntaxe de base.

Dans l'exemple suivant, on considère les variables AGE et SEX pour créer la variable PP_NY (per protocol population, no/yes) : "Si ma variable âge est supérieure à 13 et qu'il s'agit d'hommes alors ma variable pp_ny=1, sinon pp_ny=0."

data class;
   set sashelp.class;
   if age > 13 and sex='M' then pp_ny=1;
   else pp_ny=0;
run;

On remarquera l'usage de l'instruction finale ELSE pour incluse tous les cas non pris en compte précédemment.

2. Multiplier les combinaisons

Dans ce second exemple, une instruction ELSE IF a été ajoutée. Ainsi tous les hommes de 13 ans ou moins pour lesquels on connaît l'âge sont sélectionnée dans cette seconde instruction. Enfin, les valeurs restantes correspondent aux lignes d'observations où l'âge est manquant ou concernant les femmes.

data class;
   set sashelp.class;
   if age > 13 and sex='M' then pp_ny=1;
   else if age > .z and sex='M' then pp_ny=0;
   else pp_ny=.;
run;

ELSE IF : il est préférable d'utiliser le ELSE IF, plutôt que le IF pour des raisons de performance et pour éviter des erreurs d'étourderie.

• Par performance j'entends : seules les observations qui ne sont pas valides dans la première condition sont lues pour évaluer la condition suivante. C'est un temps très précieux quand on traite une grosse base de données. 
• Par erreur j'entends : en aucun cas, des observations peuvent-être sélectionnées par deux instructions. Ainsi si PP_NY=1, il n'y a aucune chance qu'il devienne PP_NY=0 après exécution de la seconde instruction.

Important : dans l'exemple précédent, j'ai volontairement choisi de lister plus d'une variable pour définir ma condition. En effet, si vous avez une seule variable en entrée et une seule variable en sortie, un informat suffit. Plusieurs avantages se cachent derrière :

• le programme est allégé
• l'accès aux valeurs est plus évident puisque les formats font partie des informations données en début de programme.

Voici ce que cela donnerait si on ne considérerait que la variable AGE pour définir la variable PP_NY.

proc format;
   invalue age_pp
   ._-.z    = .
   low-13   = 0
   13<-high = 1;
run;

data class;
   set sashelp.class;
   pp_ny=input(age,age_pp.);
run;

3. Parenthèse sur les valeurs manquantes 

On a fait très attention de ne pas inclure les âges manquants pour définir PP_NY=1/0. La valeur .z est une valeur manquante spéciale "special missing". SAS en compte 27.

L'intérêt des valeurs manquantes spéciales : le but des special missings est d'offrir d'un éventail de valeurs pour distinguer les valeurs manquantes. Prenez le cas d'une variable indiquant le contraceptif médicamenteux pris par le patient. S'il s'agit d'une femme et que l'information n'est pas fournie, on mettra manquant (un point). Par contre, s'il s'agit d'un homme, on marquera .A pour "non applicable". Un format permettra ensuite de représenter . par MISSING et .A par N/A.

L'ordre des valeurs manquantes : l'ordre des missings et special missings est important à connaître. Cela vous expliquera pourquoi j'ai utiliser .z et non . dans l'exemple précédent. Vous pouvez vous reporter à la Online Doc : Missing Values. En résumé cela donne :

• ._ pour le plus petit,
• . juste après,
• .A
• ...
• .Z pour le plus grand des special missings
• valeurs négatives
• valeurs positives

Alternative avec la fonction MISSING : sachez qu'une autre solution pour exclure tous les valeurs manquantes (missing et special missing), c'est d'utiliser la fonction MISSING quia pour autre avantage de s'appliquer autant aux valeurs textes qu'aux valeurs numériques. C'est très pratique quand on ne connaît pas à l'avance le type de la variable. Dans la PROC SQL, WHERE... il y a aussi "WHERE x IS MISSING".

4. Plusieurs actions quand une condition est remplie (DO-END)

Si une condition est rempli, il peut s'avérer nécessaire de faire plusieurs choses. Par exemple, on peut à la fois créer une nouvelle variable et sortir la ligne d'observation.

Dans l'exemple ci-dessous, la variable SEX ne prend que les valeurs 'M' et 'F'. Dans ce cas précis, au final, il y a plus de records à la fin. Tout d'abord, tous les records sont extraits et POP est défini comme étant égal à 1. Ensuite, pour les records masculins, les records sont sortis une deuxième fois et notre variable POP est alors égale à 2.

data class;
   set sashelp.class;
   pop=1;
   output;
   if sex='M' then
     do;
        pop=2;
        output;
     end;
run;

I love the guys who stand around the outside like they are in it, but are as far away from players on the other team as they can get.

We walked around parts of the park and I took a few photographs. When I started snapping around the Bloody Pond, I found one photo with a few odd things. Although I took 24 photos around the pond, only this one photo contained something unexplainable.

This is the white whatever it is in the tree. I do not claim to know what it is but the following is what I found on another website:

On the battlefield, there is a pond known as "The Bloody Pond" where many injured and dying soldiers went to cool their thirst during the heat of the day, during the Battle of Shiloh. It is said that, on certain days, when the sun hits just right, the water looks blood red; Just as it did during that battle. There is also the ghost of a woman in a white dress, possibly the wife of one of the soldiers or officers that helped nurse the men. She appears to women and children who become lost and become saddened or frightened by the battlefield. She is a helpful spirit who tries to calm and soothe those who are in need of comfort or help, but quickly disappears when someone else comes upon her and the person she is trying to help.

This is the smaller white spot in the tree.

Can you see the figure in the woods?

If you would like to be emailed the original, full sized digital photo, email tnhauntings@writersbeacon.com.

You're a part time lover and a full time friend
The monkey on you're back is the latest trend
I don't see what anyone can see, in anyone else
But you

I kiss you on the brain in the shadow of a train
I kiss you all starry eyed, my body's swinging from side to side
I don't see what anyone can see, in anyone else
But you

Here is the church and here is the steeple
We sure are cute for two ugly people
I don't see what anyone can see, in anyone else
But you

The pebbles forgive me, the trees forgive me
So why can't, you forgive me?
I don't see what anyone can see, in anyone else
But you

I will find my nitch in your car
With my mp3 DVD rumple-packed guitar
I don't see what anyone can see, in anyone else
But you

Du du du du du du dudu
Du du du du du du dudu
Du du du du du du dudu du

Up up down down left right left right B A start
Just because we use cheats doesn't mean we're not smart
I don't see what anyone can see, in anyone else
But you

You are always trying to keep it real
I'm in love with how you feel
I don't see what anyone can see, in anyone else
But you

We both have shiny happy fits of rage
You want more fans, I want more stage
I don't see what anyone can see, in anyone else
But you

Don Quixote was a steel driving man
My name is Adam I'm your biggest fan
I don't see what anyone can see, in anyone else
But you

Squinched up your face and did a dance
You shook a little turd out of the bottom of your pants
I don't see what anyone can see, in anyone else
But you

Du du du du du du dudu
Du du du du du du dudu
Du du du du du du dudu du
But you <3

Hoje veremos sobre o comando WHILE, é bem simples de usar e facilita um muito vida dos programadores, no primeiro post foi visto que foi preciso inserir várias vezes a expressão dessa forma:

nume = nume+2;
System.out.println(nume);
nume = nume+2;
System.out.println(nume);
nume = nume+2;
System.out.println(nume);
nume = nume+2;
System.out.println(nume);
nume = nume+2;
System.out.println(nume);

Mas imagine se você tivesse que escrever isso umas 500 vezes.. é ia ser bem difícil, cansativo, chato e ocuparia muitas linha de código atoa..

Agora entra a utilização do comando while.
Java Para Iniciantes 1

Java Para Iniciantes 2

Primeiro vamos entender o comando em portugol:

Enquanto (<isso for valido>) repita

<comandos e/ou expressões>;

fim Enquanto

em java:

while(true){

//comandos e/ou expressões

}

Usarei a seqüência de Fibonacci para o comando while.

A seqüência de Fibonacci é a seguinte:

1,1,2,3,5,8,13,21,34,55,89,144,233,377,...

Funciona assim, o termo atual mais o termo anterior gera o próximo termo, e como isso fica matematicamente?

valor(1) + valor(2) = valor(3)
valor(2) + valor(3) = valor(4)
valor(3) + valor(4) = valor(5)
valor(4) + valor(5) = valor(6)

...

Se você não entendeu a acesse esse link ele explica melhor ;)

Bom continuando, Agora vamos aplicar isso:

/**primeiro declaramos as variáveis
vamos precisar declarar valor atual, anterior, soma e a variável para o contador
vejamos
**/

int anterior = 0, atual = 0, soma = 1, contador = 1;

//todas variáveis como valor inteiro

/**a soma já começa com 1

pois este será nosso primeiro resultado

**/

Agora Precisaremos criar um contador para não deixar passar de 14 resultados:

se (contador <= 14) faça

Contador <= Contador +1;

//acima estamos atribuindo ao contado um valor a mais

//do que ele ja tem

fimse.

Em Java:

if (contador<= 14){

contador

}

Até aqui ta fácil, é hora de criar a lógica para realizar as contas;

de acordo com a fórmula o valor atual se transforma no anterior podemos fazer isso por atribuição:

anterior=atual;

//aqui 'atual e 'anterior passam a ter o mesmo valor

Em seguida temos que atribuir o resultado da soma que declaramos com o valor 1 anteriormente;

atual = soma;

/**'atual deixa de ter o valor igual o 'anterior e assume o valor do resultado no caso a 'soma **/

Agora usaremos uma expressão para atribuir a soma a adição de atual+anterior dessa maneira:

soma=atual+anterior;

/**soma deixa de ter o mesmo valor de atual e passa a ter um novo valor**/

o código está assim:

int anterior = 0, atual = 0, soma = 1, contador = 1;

if (contador <= 14){

anterior = atual;
atual = soma;
soma = atual + anterior;

}

para while usaremos a condição (true) ou seja ele executará tudo que estiver dentro do while até que você mande parar. para controlar isso usaremos o break que sai do laço em que está inserido.

Dessa forma, repetirá tudo dentro do while até que a condição do if se torne falso e caia no else onde terá o break.

veja o código agora:

int anterior = 0, atual = 0, soma = 1, contador = 1;

while (true){

if (contador <= 14){

anterior = atual;
atual = soma;
soma = atual + anterior;

}else{

break;

}

Só que ainda não temos um contador para fazer com que a condição do if se torne falso

para isso dentro do if teremos que atribuir +1 para a variável contador existem duas maneira de fazer isso

a primeira:

contador = contador+1;

ou a melhor, mais simples e fácil:

contador++;

Não podemos esquecer de imprimir os resultados no console

System.out.print (soma + ", ");

Dessa forma acima os resultados sairão assim 1, 1, 2, 3, 5, ....

o resultado completo:

public class Fibonacci {
public static void main(String[] args) {

int anterior = 0, atual = 0, soma = 1, contador = 1;
while (true){
if (contador <= 14){
System.out.print(soma+",");
anterior = atual;
atual = soma;
soma = atual + anterior;
contador ++;
}
else {
break;
}
}
}
}

veja o código edentado:

Dica:

para economizar linhas no caso de termos apenas uma linha do bloco do podemos como no mesmo caso do else acima podemos fazer assim:

sem precisar de nenhuma chave para o comando.

else brak;

Part of the volunteer work I do with WN is to help them connect with congregations. In looking around at web sites for churches in OKC, I came across this statement. I will refrain from naming the congregation because, quite honestly, they probably aren;t the only one in town that feels this way. They're just the only ones with enough (insert euphemism here) to say it out loud.

We ARE what YOU once were.
We believe what you once believed.
We worship as you once worshipped.
If YOU were RIGHT then,
WE are RIGHT now.
If WE are WRONG now,
YOU were WRONG then!!!

Wow. Nothing says Jesus loves you more.

So

For better or worse, I am readjusting in an attempt to create something that reflects me and my world and the thing I care about and who I am. Plus stuff I bump into as I wander the internets. So hopefully all of the folks that stop by because they are looking for Geof Manthorne or the name of the OKC NBA franchise will have something else to check out as they pass through.

We'll see. Or at least I will.

1. Passer un message

Une condition en langage macro : ici, une macro est définie. Des instructions globales sont exécutées, si le paramètre de la macro est vide. Cette condition est donc définie avec une instruction du langage macro %IF ... %THEN ... %DO; ...; %END;

Un message dans la log : l'objectif est d'informer l'utilisateur sur la nécessité d'une valeur pour le paramètre INPUT_VAL. Pour faire apparaître ce texte d'ERREUR dans la log, l'instruction du langage macro %PUT fera le travail.

Pas besoin de guillemets avec %IF ou %PUT : le paramètre d'une macro est une forme de macro variable. Pour retrouver sa valeur, son nom est donc entouré d'un symbole & et d'un point. Si cette valeur doit apparaître dans une chaîne de caractères entre guillemets, il faut impérativement utiliser des guillemets doubles. Dans le cas contraire, comme ici dans une instruction %IF ou %PUT, on se passe de guillemets pour résoudre la macro variable.

%macro test_param (input_val=,output_val=);
%if &input_val. = %then
   %do;
      %put ERREUR: Le macro paramètre INPUT_VAL= est obligatoire;
   %end;
*suite du programme;
%mend test_param;
%test_param (input_val=,output_val=);

Personnaliser son message : quand SAS rencontre une erreur, il utilise le mot ERROR dans la log. Pour distinguer ce message des votre, vous pouvez ajouter un mot-clé comme le nom de la macro. Par exemple : "ERROR - TEST_PARAM: the INPUT_VAL= macro parameter is mandatory.".

2. Gérer les caractères spéciaux : il est fréquent d'avoir des valeurs autres que les chiffres et les lettres de l'alphabet comme valeur pour un paramètre de macro. Vous aurez souvent besoin de définir l'emplacement des données sources et celui où les outputs seront sauvegardées. Pour cela, les paramètres auront des valeurs du type c:/mon_projet/mesdonnees ou encore c:/mon_projet/mes_resultats. Il existe des macro fonctions : %BQUOTE et %NBRQUOTE pour tenir compte de la barre inclinée (slash) et d'autres caractères spéciaux.

• %BQUOTE : les symboles suivants sont gérés avec la fonction %BQUOTE() : ' " ( ) + - * / < > = ¬ ^ ~ ; , blanc AND OR NOT EQ NE LE LT GE GT
• %NBRQUOTE : si, en plus, vous avez les symboles & (et) et % (pourcentage), il faudra faire appel à la macro fonction %NBRQUOTE().

SAS online DOC :

• %BQUOTE et %NBRQUOTE Functions
• Using the %BQUOTE and %NBRQUOTE Functions

3. Enjamber un programme

Si la condition n'est pas remplie, on peut demander à SAS d'ignorer une partie du code grâce à la syntaxe de %GOTO. Il était également possible de demander à SAS d'arrêter son exécution en plein milieu. Certes, enjamber le code permet d'avoir une log plus propre, puisque seuls nos messages apparaissent. Mais surtout, cela permet de poursuivre l'exécution du programme. Ainsi, si un appel de macro ne fonctionne pas, rien n'empêche de continuer la soumission d'autres appels de cette macro.

Dans un premier temps, il s'agit de définir une balise. A partir de cette position, SAS pourra continuer son exécution. Ici, la balise s'appelle FIN_PGM. Elle est ajoutée juste avant la fin du la macro.

Dans un second temps, si le paramètre est vide, SAS est prié d'ignorer le code qui suit jusqu'à la balise. Pour cela, dans la condition, l'instruction %GOTO est ajoutée.

%macro test_param (input_val=,output_val=);
%if &input_val. = %then
   %do;
      %put ERREUR: Le macro paramètre INPUT_VAL= est obligatoire;
      %goto fin_pgm;
   %end;
*suite du programme;
%fin_pgm:
%mend test_param;
%test_param (input_val=,output_val=);

The temperature is 67.
if the temperature is lower than 50 degrees

    You should wear a coat

else

    You'll be fine without a coat.
end if

Here is how the statement would look with the variables declared.

This simple applescript can be modified to use ranges rather than a set temperature. For instance, if the temperature is between -200 and 50 degrees and 51 and 200 degrees. The lower and upper range is set to an extreme [at least for IL] so that nothing could be left out.

Em C:

# include <stdio.h>

int main(int argc, char** argv)
{
    int x = 0;
    int y = 1;

    if(x > y)
        printf("%d eh maior que %d\n", x, y);
    else
        printf("%d nao eh maior que %d\n", x, y);

    x = y--;

    if(x > y)
        printf("%d eh maior que %d\n", x, y);
    else
        printf("%d nao eh maior que %d\n", x, y);

    return 0;
}

Em C++:

# include <iostream>

using namespace std;

int main(int argc, char** argv)
{
    int x = 0;
    int y = 1;

    if(x > y)
        cout << x << " eh maior que " << y << endl;
    else
        cout << x << " nao eh maior que " << y << endl;

    x = y--;

    if(x > y)
        cout << x << " eh maior que " << y << endl;
    else
        cout << x << " nao eh maior que " << y << endl;

    return 0;
}

Em Java:

public class IfElse
{
    public static void main(String args[])
    {
        int x = 0;
        int y = 1;

        if(x > y)
            System.out.println(x + " eh maior que " + y);
        else
            System.out.println(x + " nao eh maior que " + y);

        x = y--;

        if(x > y)
            System.out.println(x + " eh maior que " + y);
        else
            System.out.println(x + " nao eh maior que " + y);
    }
}

O velho problema das chaves nos if/else aninhados:

Sabemos que ao usar apenas uma instrução dentro de um if ou de um else, as chaves são opcionais. Mais de uma instrução, no entanto, torna obrigatório o uso das chaves. Vejamos um problema comum com o uso das chaves em if/else aninhados:

# include <stdio.h>

int main(int argc, char** argv)
{
    int x = 5;

    if(x == 5)
        x = 4;
        if(x == 3)
            x = 2;
    else
        x = 0;

    //imprima x

    if(x == 5)
        x = 4;
        if(x == 3)
            x = 2;
    else
        x = 1;

    //imprima x

    return 0;
}

O que ocorrerá com o valor de x neste código? Teste-o e tire suas conclusões. A dica que eu posso dar é que pode ser resolvido fazendo isto:

# include <stdio.h>

int main(int argc, char** argv)
{
    int x = 5;

    if(x == 5)
    {
        x = 4;
        if(x == 3)
            x = 2;
    }else
        x = 0;

    //imprima x

    if(x == 5)
    {
        x = 4;
        if(x == 3)
            x = 2;
    }else
        x = 1;

    //imprima x

    return 0;
}

Teste os dois códigos e perceba que uma instrução else sempre pertence a o último if, no caso deste if/else conter apenas uma instrução. Uma dica: para evitar problemas, sempre use chaves em if/else, não importa se ele tiverem mais de uma instrução ou apenas uma.

return 0

Stop by lvimages.wordpress.com and watch the work in progress if you are so inclined.

Here's the word from AskMen.com's editor in chief.
Hello Oklahomans! -- Thanks for all your posts. We certainly admire your quick defense of your capital, and please understand that its place on this list isn't a commentary on it as an economic center, a sports town, or a place to live and raise a family. This article was commissioned and written as a lighthearted travel feature. What guided us in choosing the cities that we did? In seeking out the world's least travel-friendly destinations, we looked for diversity in terms of what characterized each of them as such, hence the reference to "Type of Hell" within each subheader. So when it came time to choose a city that was characterized by natural disasters, OKC -- home to some of the world's most frequent and powerful tornadoes -- was a natural choice.

James Bassil
Editor-in-Chief

Of course, in generating this kind of response, the good folks at AOL travel and askmen got exactly what they wanted. By dropping OKC they guarantee that they will be back on the radar a second time (like on this blog). But whatever.

So world - come to Oklahoma City. Just watch out for those blizzards.

1. Weather in OKC is unpredictable. I have to give them this one. Of course this is also true of almost anywhere in the midwest and the meteorologists in OKC are among the best in the world at what they do, so. . .

2. We get blizzards. Huh? In the almost 30 years I have lived in OKC I can remember maybe 5 times where it snowed more than 6 inches in a single storm. According to the National Weather Service, OKC averages an 8 inch or great snow event every 5-10 years.

3. It's windy here. Yep. It's windy a lot of places. The average annual wind speed is higher here than a lot of places, but is no greater than the average at Laguardia Airport in NYC and is lower than that of Boston.

4. We are in the "path" of Tornado Alley. Again, guilty. But the data show that OKC is actually number 9 on the list of US city tornado scores.

5. The May 3, 1999 tornado devastated "much of the city". Was it bad? Yes. Much of the city? Seriously. Someone is watching too many made for TV disaster movies.

Someone clearly needed an American city to poke fun at and we got picked. Maybe the author is a (used to be) Seattle Sonics fan. Or maybe they are just sad from looking out the window at the weather in New York.