Last few weeks, I had to explain quite a few times what it is I am doing now. Time for a summary.
I am not a WordPress Developer.
And I develop in Ruby. And Rails. And then some more.
I also don’t develop with or for Drupal.
After my decision to stop all Drupal Work I’ve honed my Rails skills. Improved my understanding of OO patterns, software architecture. Got to love TDD and BDD, and hardly ever regretted my decision.
I am a webdeveloper. Developing in Ruby, Rails. And using other tools.
We do dissect our WordPress sites. To find why the heck something is (still) slow. And I oversee some WordPress plugin development: our Hosting plugin that makes WordPress talk to our, yes, Ruby backends. But I am not a WordPress Developer. And neither did I leave Drupal for WordPress as some seem to think.
A webdeveloper at an online bookstore needs to know about the world of selling books. And when you’re a developer for an online 3D-printing-service you will visit many 3D-printing conferences. That is what confused some folks: suddenly they see me tweeting about WordCamp and assume I’m now building WordPress sites. It’s merely one of the best sides of being a software-developer: that you’ve get to know so many diverse industries, because you need to capture that industry in software. I’ve now been given the chance to capture the industry of managing many, varying WordPress-sites in a fine piece of software. Which is about all the WordPress development I’ll be doing.
(And next up, are Chef, fine-tuning our Sinatra, Slim and Rails apps, building a nifty logging-platform, A RESTFull (probably composer-based) update-system for plugins, core and themes, a RESTFull Backup-service and a giant load of other infrastructural projects).