3 hours later I discover why my unset destroyed our json.

"When encoding an array, if the keys are not a continuous numeric sequence starting from 0, all keys are encoded as strings, and specified explicitly for each key-value pair."

Thanks obama.

No, why would you make sure your not working with a database over a year old. Totally our fault, we're jackasses for telling you to do it over again.

I've created instructions for myself the next time I encounter cpanel.

rallen@rallen ~ $ cheat cpanel
#SSH'ing into the fucking cpanel
#Figure out combination of 5 usernames and passwords given by client to log in.
#Pray that WHM isn't involved.
#Ignore several ssl warnings and cancel several .htaccess password prompts.
#Call in to enable that shit.
#Wait no less than 15 minutes on hold.
#SSH enabled.
#Create public private key pair.
#Notice the ppk conversion for windows 'devs'. Sigh.
#Copy key pair to ~/.ssh/
#chmod that shit to 600.
#Note for the user name it's not anything the clients given you or what you've named the key. Look in the cpanel for the /home/<user> directory.
ssh -i ~/.ssh/key <user>@<dedicatedip>

I wrote an application to demo at a convention coming up. Which feeds tcp data from arduino devices to real time d3 maps via websockets.

Demoing today, and the owner starts talking about a project he saw that which lit up some lights to a device in the room via the internet. In this same meeting he casually mentions he wish he had developers who could do that type of stuff.

The disconnect is massive and soul breaking.

Friday. 4:51pm. 5 sites all decide to go down in tandem. OFC.

If I have one more developer commit database credentials to code I'm going to have a red stapler moment and burn something to the ground.

I currently work in a php shop where 90% of the devs don't know composer. #drupalFTW