(![]+[])[+!+[]]+(![]+[])[!+[]+!+[]]+([![]]+[][[]])[+!+[]+[+[]]]+(!+[]+[])[+!+[]+!+[]+!+[]]+([![]]+[][[]])[+!+[]+[+[+!+[]]]]+[+!+[]]+[+![]]+((([+!+[]])<<3)+1)

The following examples are not exactly syntactically correct, but they were made up to fit into a twitter post.

i=0;
while(!teeth.brushed) {
print "for the " + ( i++ ) + "time, go brush your teeth!";
}
or
kid.addEventListener("MomOrDadSaysSomething", doIt);

I’m sure I’ll be adding more and updating as I think of them…

I wanted to transfer a 30 second song to my phone. 30 seconds, 432K. Should be as simple as drag and drop. Few seconds worth of time. But here it is two hours later, and I still haven’t gotten the file on there.

This is ridiculous.

First iTunes tells me it’s synced to a different library and must erase all my data, even though I only have one library and sync on only one computer. Then it has to backup everything on the phone before syncing. And we all know how long that can take sometimes. 50 minutes later, the sync starts. But then iTunes stops responding and then crashes. My phone then decides to reboot. I restart iTunes and plug the phone back in. Click sync, and now, it is backing up again.

So, it’s going to take over two hours to transfer a 432K file over USB? Seriously?

Fuck you Apple, right in your Steve Jobs butt.

Just open up a terminal window and enter the following:
defaults write com.apple.mail PreferPlainText -bool TRUE

To return back to normal, just enter the same thing, but set it to FALSE.

Recently I was attempting to create some cron jobs to run PHP scripts on a DV server or at MediaTemple, with PHP installed as an Apache module (rather than CGI). I was able to execute the php file, however all of my include and require statements were totally failing.

My first idea was to set the include paths in PHP. This failed and the scripts still reported errors. My next attempt was to use absolute paths for my includes. This correctly found the includes, but resulted in safe mode errors.

I finally resolved the issue by creating a custom .ini file for PHP, making the appropriate setting changes and then supplying that ini file as an argument to PHP in the cron command.

SSH into the server, and copy the ini file. Something like:
#cp /etc/php.ini /var/www/vhosts/domain/includes/cron/php.ini

Now open up the new ini file in vi or emacs (I’m not getting into that debate). First you’ll want to disable safe mode by changing the line “safe_mode = On” to “safe_mode = Off”. Next, you can comment out the openbase_dir setting by changing the line “open_basedir = “/usr/share/pear” to be “; open_basedir = “/usr/share/pear”. And finally, set the includes path for your php scripts.

The last step is to make sure you execute the correct command in cron. Remember, you’ll need to pass the custom .ini file as an argument to PHP. Something like:

php -c /var/www/vhosts/domain/includes/cron/php.ini /var/www/vhosts/domain/includes/cron/test.php


This isn’t rocket science, and probably a no brainer to some. But, I found it useful and hope someone else does too.

The best thing about this, is I can leverage existing PHP code without having to write a ton of junk in PERL (yuck). Less code = less frustration.

I just received this gift from a friend upon his return from a trip to Korea. I’m not sure if I should be proud of the fact that he said he thought of me when he saw this or not. Nonetheless, I love this thing. My kids love it too. The fun doesn’t stop with the toy itself. Reading the instructions can provide a laugh or two as well.

And of course, I couldn’t resist. It just begged the sound track.

So what next…

I’m not sure if what I did and what I am about to tell you next is the correct way to deal with the situation, but I guess in a few days we’ll see if I’m the proud owner of a worthless hunk of aluminum.

Step 1

Tilt the laptop so the moisture drains away from where the logic board is. The board is approximately located towards the back and extends down to about where the space bar is. It starts on the left side and ends about where O and P keys are.

Step 2

Unplug and power down as quickly as you can. The faster you do this, the more likely you are save your system from getting fried. Don’t worry about shutting down your system properly at this point. You’ll probably survive that, it’s the hardware we’re worried about. So – press and hold that power button until the screen goes black.

Step 3

Set your laptop on top of something absorbent like a towel, and get some air moving. Heat is probably a bad idea, so it’s probably best to just use a fan. Remove the back cover to expose the components inside. There are 10 screws holding the back plate on. It is probably a good idea at this point to find a small container to place all of your screws in, so you avoid losing them.

Step 4

Warning the next step will void your warranty.

Remove your battery from the system. Apple, being the jackasses they are, use special screws to hold the battery in place. After a trip to RadioShack, the MacStore and my local hardware store I found that nobody carries the correct screw driver for this. However, I found that my cheapo precision screwdriver set has a flat head 2.4mm one that will work anyway.

Make sure your warranty isn't important to you before proceeding!

Step 5

Dry up any excess moisture you can. And keep that fan running

Mmmm. Coffee...

Step 6

Finally, and most importantly, DO NOT give in to the temptation of putting things back together and firing up your laptop before it’s had a chance to completely dry out. If you do, you might fry something (if it isn’t already). I plan on leaving my as is for a few days just to make sure.

Gratuitous nerdy shot. Hey, I thought it looked neat and was curious how well my macro settings worked on my Cannon XSi Rebel.

http://www.youtube.com/watch?v=-E6q-m1tLn8