PsychoDeveloper @PsychoDeveloper

Chome ext. devs: keep adding shortcuts that overwrite the built-in ones and I'll shortcut your fingers off. #thankyouverymuch #WindowResizer

I've realised it's been over a year since I last tweeted. This is because I stopped using #PHP. I now use #Python. The #zen is palpable.

Remember kids, "Testing saves money, jobs, and lives." (Daniel Greenfeld) So if you don't Test, I'll find you, and I'll split you in two.

"# Dev workaround, remove when live" - found in code that's been live for 12 months. That dev is going to lose a finger.

Docs say "Parameter `mini` is required & must always be set to `true`" Why fucking have it then? Just get rid & make everyone's life easier.

While I'm at it, which cunt decided that #SimpleXML wouldn't throw an exception on a parse error? Ya, throw a Fatal error, that's good.

And why the FUCK would you use curl_* functions?! Just use file_get_fucking_contents. It #JustFuckingWorks.

Oh dear god, why can't PHP developers write code that fails gracefully when feeds/etc are't available?!??! Some twat is gonna get cut.

Bloody hate setting up VSFTPD. It never seems to want to play nice, despite following all the guides.

Really pisses me of when people get POST and PUT the wrong way round in #REST. PUT creates/overwrites resources, POST executes *actions*.

Aaaaand then I run into another bug with this #wordpress plugin. I've said it before and I'll say it again, I WILL HARVEST SPLEENS SOON.

When the fuck will #git get a `submodule remove` method? I don't want to have to delete X folders and edit Y files.

Aaaaand I've found the bug: `if( version_compare( $wp_version, '3.5', '<=' ) ) use_old_code();` which was always true. #ShittyPHPDevs

So it turns out that the #wordpress plugin I'm trying to use binds to an action that doesn't actually exist in the wp source.

You #PHP devs with code on #github. Yeah, you there. Learn to fucking tag shit. Version no's in your code == tag that shit up.

Oh FFS, why can't #wordpress plugin developers manage their fucking version numbers correctly? v1 in github, v1.1 on wp site, same code.

So, in the last few minutes #wordpress releases 3.5, so I upgrade. Retry plugin. No joy. I'm ready to END a cunt. #FuckThisShitInTheAss

Oh, it gets better: the #wordpress notification signup form doesn't work, so I can't get notified when 3.5 *is* released. #fuckingamazing

What's really nice is that #wordpress has announced the release date for 3.5: Dec 5th, 2012. Nearly here then! #fuckingridiculous

Finally find a #wordpress plugin that does 70% of what I need. Except it doesn't work. 'Cos it requires WP 3.5. Which isn't out yet. #FFS