nerdiness devours me
ultimatenerd:

An oldie but goodie. Mouseover text: “Apple uses automated Schnapps IVs”

Absolutely hilarious :D

ultimatenerd:

An oldie but goodie. Mouseover text: “Apple uses automated Schnapps IVs”

Absolutely hilarious :D

So a Saturday night, I turned off the light, locked the door and sealed the windows. It was time to check out this Japanese creation. […]

A few hours later, I had forgotten everything about Python. Stupid language. Ruby was where it was at, and I instantly started recommending it to all my code-buddies. It’s such an awesome language, why not spread the joy? They said I was a fanboy, and told me to gtfo. And I quickly realized what had happened.

Ruby is evil


Reading this article really makes me want to get back to my basics which are like the authors basics, HTML & CSS. Ruby and Rails can’t hurt either, along with a little linux, opensource and the lot. I hate myself being so Microsoft desktop development contaminated due to my dayjob…

davidkaneda:

Simple loop example:

HAI
CAN HAS STDIO?
I HAS A VAR
IM IN YR LOOP
UP VAR!!1
VISIBLE VAR
IZ VAR BIGGER THAN 10? KTHXBYE
IM OUTTA YR LOOP

KTHXBYE

Yes please. (via jayrobinson)

OMG, IT’S A TARP!

We can all recognise good-quality database code: It doesn’t break with every change in the server’s configuration, or on upgrade. It isn’t affected by concurrent usage, or high workload. In an extract from his forthcoming book, Alex explains just how to go about producing resilient TSQL code that works, and carries on working.

I know all of these types of emails, although I think that the last type is a myth…

The normal nomenclature for { and } is “open-brace”, “close-brace”, or “open-curly”, “close-curly”. From this day forth, I propose a new nomenclature. From now on, it shall be known as “open-mustache”, “close-mustache.
{{ mustache }} (via dhotson)