All our Bayesian are belong to them

This just forwarded from a friend (emphasis and added link(s) mine)... ...and no, he doesn't work for Google. I ...think... that this is just a coincidence...

Apparently, I offend their chief.

No, I'm not including the probably-a- poison-pill GIF that was attached.

What coder or designer among us doesn't thrill to recognize eternal verities such as:

"you want your boss told you support in your own code."

We've ALL been there, haven't we? I know that *I* always wanted my boss told me support in *my* own code.

Did I ever get? NO! I had no. I had to move every zig! For great justice.

The appended Bayesian word-salad evidently based on a stroll through the HeadFirst stuff made me laugh. I hope you get at least a smirk out of it, Kathy!

{Ed: "Kathy" here is Kathy Sierra, who blogs at "Creating Passionate Users"}

....

---------- Forwarded message ----------
From: V____ W___ <nowayamigonnagivethisjerkafreelink@uh-uh.not>
Date: Oct 8, 2006 4:07 PM
Subject: you offend our chief
To:

more complex. deep understanding of why someone struggles Design Patterns, you'll avoid science, and learning theory, to learn how those You'll easily counter with your

principles will help patterns look in Singleton isn't as simple as it sounds, how the Factory to learn how those You'll easily counter with your a design paddle pattern.
when to use them, how or on the real relationship (and impress cocktail party guests) be wrong (and what the embarrassment of thinking

that you can hold your to do instead). You want environment. In other support in your own code. Something more fun. used in the Java API

you have. You know

applications. You same problems. Singleton isn't as simple as it or on the real relationship them to work immediately.

the embarrassment of thinking to do instead). You want , and how to exploit you get to take principles will help the embarrassment of thinking

them to work immediately. same problems. is so often misunderstood, Something more fun.
about inheritance might You want to learn the
better at solving software

Patterns--the lessons

and experience of others, the next time you're Head First Design Patterns up a creek without
the patterns that with
own with your co-worker

to do instead). You want

a book, you want your boss told you support in your own code. the latest research in
someone struggles design problems
you get to take

so that you can spend

better at solving software you don't want to NOT to use them). Facade, Proxy, and Factory

on your team. Head First book, you know at speaking the language
sounds, how the Factory the next time you're matter--why to use them,

Head First Design Patterns them to work immediately. someone struggles somewhere in the world You want to learn the to use them (and when your boss told you
In a way that makes you

texts. If you've read a of the best practices
is so often misunderstood,
In a way that lets you put want to see how
or on the real relationship

brain in a way that sticks. , and how to exploit better at solving software of patterns with others the embarrassment of thinking
you get to take In their native the patterns that the next time you're
up a creek without science, and learning theory, Head First book, you know more complex. the same software
(and impress cocktail party guests)

format designed for the way
Design Patterns, you'll avoid between Decorator, Facade You want to learn about design problems, and better want to see how

the embarrassment of thinking on your team. You're not

between Decorator, Facade of the best practices

environment. In other a design paddle pattern. , and how to exploit better at solving software
and experience of others, your time is too important
reinvent the wheel

brain in a way that sticks.