Today's my first day working at Doyle's company. Warren suggested last night that the org chart for the company be rewritten so that Doyle is my direct boss. Although the concept is quite humourous, I prefer Doyle's suggestion of "put all the Drupal developers in one department, THEN put me over you."
Doyle suggested we carpool to his work this morning. Since I wasn't sure what the various parking protocols were, what the office hours were, and how I was going to get into the building to work, I enthusiatically said yes.
Starting at a new company always has issues, whether it's for a new full-time job or for a new contracting position. Today was no expection to that "issues" rule. However, having someone who I could talk to, and ask what was up, having Doyle just right there, oh, my, made starting the new job so much easier than I was expecting.
On the way home, Doyle asked me, "So, how was your first day?"
It was good, so I told him so. I also told him how much I LOVED that I could just turn to someone and start asking technical questions, and he immediately knew not only what I was talking about, but could converse with me intelligently about the task at hand, and offer suggestions.
He turned to me and exclaimed, "I KNOW!" It took me a few moments to realize that he, too, was missing having someone with the same expertise and experience as he had.
I smiled. I hadn't realized just how much I had missed working with Doyle.
I went up to the City tonight for the San Francisco Drupal meetup. Hannah and I took the train up together, with my taking a taxi to the meetup location.
There were about 15 people at the meetup, ranging in experience from previous release co-maintainer (Neil Drumm, who, honestly, is fabulous, we lurves him) to just installed it and tried it once. Also known as the range of Drupal user ID from 5088 to over 200000+. Most of the people at the meetup were developers instead of just users, which made me happy.
The presentation was for the patterns module, made by Chris Bryant. The module and surrounding infrastructure address the site setup problem where profiles fal short (in particular, with module add-ons and configurations). One of the surprising features of the module is that, even though it automates a lot of site setup, it does so through form submissions instead of accessing the database directly.
I wish I could say that I was the dynamic, outgoing person I want to be in these situations, but I wasn't. I wasn't uncomfortable, per se, but I was definitely with a group of people I didn't know. I ended up leaving soon after the presentation, and walked back to the train station. It wasn't nearly as far as I thought it was.
I surprised Kris today. I told him I was done with Drupal. He couldn't believe his ears and asked for clarification. What did I just say?
I told him again that I was done with Drupal. I unsubscribed from the mailing lists. I left the IRC chatrooms (fortunately, my ongoing donation subscriptions to the organization that runs the IRC servers guarantees my nickname will remain mine, even if I don't log in regularly any longer). I closed my always-open browser windows that showed the Drupal API search page. I put away all of my Drupal work. I'm done.
I wish I could say I'm walking away because I accomplished everything in Drupal that I wanted to do. Unfortunately, that's not the case.
In reality, I'm tired of dealing with certain elements within the Drupal community. I'm not particularly interested in fighting the battles of incorrect perceptions, of overloaded projects, of unrecognized abuse and of difficult-to-do tasks that should be easy.
Tired. And done.
Life's too hard already to waste time dealing with I'm-not-a-jackass jackasses. I have other things to do than wage that war. Fun things like larning new systems.
Like, say, Wordpress.
I really hate when a simple task, something that I think should take an hour tops, not only takes me longer than that hour, but takes me longer than that hour because I want to do it correctly. Sometimes I wonder if my level of "Good enough" is too high. Eh, probably.
Today's example: yesterday a post came through on the Drupal support mailing list:
Does anybody know of an existing module which will extract tags from
the body of a post (i.e. a line like "Tags: tag1 tag2 tag3") and pass
them to the taxonomy system to tag that node?
I've had a skim through the Taxonomy related module list on drupal.org
and didn't spot anything...
Looking at this request, writing such a module should have taken an hour, maybe, right? Well, as I started working on the module, there were features I wanted, details that, well, would bug the crap out of me if they didn't work right. They were small things (is the trigger word "tags" or "tag" or "tagaroo", or is the tag line removed from the post after processing), but ones that, well, if someone gave me the module, I'd want.
So, in they went.
And my hour "give back to the community" turned into a retarded 4 hour project.
Four hours not spent on client work. Four hours not spent on my big projects. Four hours that I really could have used better elsewhere.
I'm so annoyed at myself.
At least I managed two posts from it. :\