Saturday, May 26, 2012
Oh God.

Oh God.

mymysororitygirl:

Me: You look like a mad scientist. 

Logan: This is my third eye.

Can’t stop the Science, Nat.

Friday, May 25, 2012
leasthelpful:

Ah yes, the ol’ “promise one thing, deliver that same thing later” scam

leasthelpful:

Ah yes, the ol’ “promise one thing, deliver that same thing later” scam

Thursday, May 24, 2012
  • Morgen: Hey Logan do you have any idea -
  • Logan: No I have no idea what ANYTHING is and I hate you

spetharrific:

“There are only two hard things in Computer Science: cache invalidation and naming things.”

The world’s two worst variable names | Andy Lester (via spooningfork)

intention revealing names. it’s not terribly difficult with just the smallest bit of effort. i suppose thedistanceinsidious and i should argue about this now or something xD it’s less relevant with throwaway code, but if someone is going to look at your code (including your future self) it is quite beneficial to at least have an idea what things are.

diving through legacy perl code right now is a pain only mitigated slightly when i land somewhere that is at least somewhat anchored conceptually. just thoughts.

and yes: cache invalidation is a difficult problem x__x

I hate to fall into the trap of predictability, but naming things IS incredibly hard.

Namespaces and proper scoping help, but any sufficiently complex “real world” [read: enterprise] problem will usually escape into a combination of magic names (Ex: “sumCustomerValues”), extremely verbose names that don’t tell you anything (Ex: “customerUniqueKeyForSomeLegacyPurposeWeForgotAbout”), and really magic names. (Ex: “tmp_x” as an integral component in production code) 

Don’t even get me started about corporate internal coding standards policies. Those things are brilliantly bad at creating “clean” code. Only verbose, uniformly-unreadable code.

Even hobby projects lend themselves to the naming problem, and that’s honestly for the same reason OOP has many shortfalls: things are complex.

(Source: ekline)

c1qfxugcgy0:

help I’m running out of pictures of SC2 pro players doing the ¯\_(ツ)_/¯ emoticon

I’m dying right now. The public outcry is the most entertaining thing that I’ve seen today.

Everyone is retarded.

And it’s hilarious.

ee-oh-ee-oh:

i find it peculiar how, despite the algorithm that i used to draw these being left almost entirely up to chance, we can still attribute form within a noise of shapes..

This is pretty neat. If you’ve got the algorithm handy, I’d love to see it.

It looks a bit like some kind of fractal with noise, but I can’t tell with any degree of certainty.

c1qfxugcgy0:

problemsleuth:

ive beEN LUHAIGBG AT THSI FRICKNE GIF FRO LIKE 0395843583409583409 MINTIES NWO ADN I JUTS CATN GT OVR IT EHS JUS MLRJ LIKE MWALKIGN NAD THNE TH ON EKJ KLJSKDFKSD GUY IS NUJST POP IN TH HEDAD ADN OLL IES OVR A FRICK BUIDLIGNG  ADN EJS JSUT SO XOCMFUSED  WAT HJTH FUCK JUST GVKAAPPEN KSKJ IMVKFM ;LKSFD LLAJVKDIVDMKLFGNDFKGDF

CSS disasters: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22.
Some notes: (CSS reformatted for clarity)
if (document.all) {
  document.onmouseover = doRainbowAnchor;
No. Don’t make links strobe through rainbow colors when you mouse over them.
body, div, p {
font: 10px Lucida Sans Unicode, Tahoma, Verdana}
No. Don’t make the text 10 pixels tall. Never do that. (Also, you don’t have to include div and p in that selector: they’re both descendants of the document body.)
body, a, a:hover {cursor: url(http://static.tumblr.com/f50xx01/bVDm1u5c8/mar.png), progress;}
No. Don’t change the cursor to a pokemon. Don’t change it at all, in fact, leave that shit alone.
iframe#tumblr_controls {opacity: 0.2;}
No, don’t fade out the Tumblr controls. Never do that. Leave that shit alone.
<img alt="tumblr themes" src="http://static.tumblr.com/thpaaos/dHHkt0jor/install_theme.png" style="position:absolute; right:3px; top:32px;">
Here’s where I get to escape my broken AAC-player routine, and complain about something I haven’t whined about a hundred times before. Namely, themes that put “Install this theme!” buttons next to the standard tumblr controls.
I’m not sure if I hate it.
Sure, the button’s displayed even if the reader isn’t actually a Tumblr user, which makes it totally useless for that segment of readers. And sure, it apes a standard UI element in a totally dishonest way, like banner ads that pretend to be Windows alert boxes. But it’s used in a theme by one of the Tumblr devs, so I guess it’s okay.
But check this shit out:
iframe#tumblr_controls:hover{-webkit-transition: opacity 0.7s linear;opacity: 1}
a img:hover {-moz-transform: scale(1.02);

So when you mouse over the install theme button, it scales it up by 2%, which just makes it blurry, but not a whole lot bigger. (Again! Why does this keep happening?)
But when you mouse over the controls, it just fades them in, but doesn’t upscale them. Two completely different visual actions for what, to the user, are the same class of button. Combine that with the giant ugly gap between the tumblr_controls row and the install theme button, and you have a magnificent trainwreck of UI design.

c1qkeyboardsmash, warrior of the internet.

c1qfxugcgy0:

problemsleuth:

ive beEN LUHAIGBG AT THSI FRICKNE GIF FRO LIKE 0395843583409583409 MINTIES NWO ADN I JUTS CATN GT OVR IT EHS JUS MLRJ LIKE MWALKIGN NAD THNE TH ON EKJ KLJSKDFKSD GUY IS NUJST POP IN TH HEDAD ADN OLL IES OVR A FRICK BUIDLIGNG  ADN EJS JSUT SO XOCMFUSED  WAT HJTH FUCK JUST GVKAAPPEN KSKJ IMVKFM ;LKSFD LLAJVKDIVDMKLFGNDFKGDF

CSS disasters: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22.

Some notes: (CSS reformatted for clarity)

if (document.all) {
  document.onmouseover = doRainbowAnchor;

No. Don’t make links strobe through rainbow colors when you mouse over them.

body, div, p {
font: 10px Lucida Sans Unicode, Tahoma, Verdana}

No. Don’t make the text 10 pixels tall. Never do that. (Also, you don’t have to include div and p in that selector: they’re both descendants of the document body.)

body, a, a:hover {cursor: url(http://static.tumblr.com/f50xx01/bVDm1u5c8/mar.png), progress;}

No. Don’t change the cursor to a pokemon. Don’t change it at all, in fact, leave that shit alone.

iframe#tumblr_controls {opacity: 0.2;}

No, don’t fade out the Tumblr controls. Never do that. Leave that shit alone.

<img alt="tumblr themes" src="http://static.tumblr.com/thpaaos/dHHkt0jor/install_theme.png" style="position:absolute; right:3px; top:32px;">

Here’s where I get to escape my broken AAC-player routine, and complain about something I haven’t whined about a hundred times before. Namely, themes that put “Install this theme!” buttons next to the standard tumblr controls.

I’m not sure if I hate it.

Sure, the button’s displayed even if the reader isn’t actually a Tumblr user, which makes it totally useless for that segment of readers. And sure, it apes a standard UI element in a totally dishonest way, like banner ads that pretend to be Windows alert boxes. But it’s used in a theme by one of the Tumblr devs, so I guess it’s okay.

But check this shit out:

iframe#tumblr_controls:hover{-webkit-transition: opacity 0.7s linear;opacity: 1}
a img:hover {-moz-transform: scale(1.02);

So when you mouse over the install theme button, it scales it up by 2%, which just makes it blurry, but not a whole lot bigger. (Again! Why does this keep happening?)

But when you mouse over the controls, it just fades them in, but doesn’t upscale them. Two completely different visual actions for what, to the user, are the same class of button. Combine that with the giant ugly gap between the tumblr_controls row and the install theme button, and you have a magnificent trainwreck of UI design.

c1qkeyboardsmash, warrior of the internet.