Tip for coders
 

When running a split test on some coding changes you've made, remember to also take out the if/else block for the last code change you tested. Otherwise you end up throwing away a week's worth of data because you've been testing the WRONG FUCKING THING!!!! :mad::mad::mad:

Yeah, I hate when I do that :(

.

I left an if/else in one time.

Bitch took my house.

Dont think i ever use if else for testing purposes.

This advice won't be of any use to you then.

Another tip for coders: get some sun.

"else" really isn't needed after every "if" ..
I can give you a bunch of examples ...

Personally.. it would make a mess of the code to write to write a empty else after every if.
You don't always need a final else ...

I think most programmers are well aware of that but it is worth repeating for any newbs out there.

With that said, many of us refer to the conditional structure as "if then else" whether there is a literal else indicated or not. Not putting an else says to do nothing:

if this condition then do this else do nothing

is the same as

if this condition then do this

.

Also don't change permalinks when G indexed 30k pages :Oh crap

Old habits die hard.

Don't understand what you all are talking about, but ok...

#