drupal

Drupal SF meetup

Blog

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.

Leaving Las Drupal

Blog

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.

Took me long enough

Blog

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.

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.

Gah.

I'm so annoyed at myself.

At least I managed two posts from it. :\

Vicious cycle, this

Blog

Back when I worked at PDI, my group was in constant battle with the production engineering team. There were never more than four of us in the lighting TD group, and at least five in the PE group. It seemed we were always butting heads with half the group.

The fundamental difference between the two groups was that my group was trying to get work done, while the PE group was trying to build an infrastructure "the right way." The Right Way™ often meant "don't do anything until we build it and say it's okay to use," which inevitably took two weeks longer than my group had time. We were in production and production had schedules and we didn't have time to wait. If the tools weren't coming, we built the tools. If the problems weren't being solved, we solved them. Seems simple on paper.

Despite the near constant head-butting, I, thankfully, became good friends with Kevin Cureton who worked in that group. I miss Kevin a lot. I miss talking to him. I miss solving problems with him. I miss his stories and adventures and expertise and laughter. He has moved on from PDI to EA and I think from there, too. I don't know exactly where, as I've lost touch with him. I'm deeply saddened by this fact.

Kevin often went to bat for me when there was some conflict, and defending me when I was doing something totally bizarre but effective.

Thinking of the group, of the five people in it who I recall, I butted heads with 3 of them. One was a dick, one was an idiot and one was just clueless. Of the other two, one was Kevin, and therefore awesome, the other was Mitch Amino, who I liked very much, even though he was quiet and I think sometimes thought of me as near insane.

During one particular incident, I had wandered up to the PE group's area and told them I had implemented some feature that I no longer recall what it was. One of the PE group's people whose name I don't recall, waited until I left, then exploded about how dare I do this or that or something, that I didn't know what I was doing, what the frack did I think I would accomplish?

Kevin listened to his coworker rant. After he had calmed down, Kevin politely pointed out that I and my group keep about forty lighters from asking the five of them question after question after inane and clueless question. If the four of us weren't there, the five of them would have to provide support for the forty lighters that sat downstairs and have considerably less knowledge than I or my group did. Kevin then asked, did his coworker want to support forty lighters, because he sure as heck didn't want to.

The ranting coworker shut up.

And was pleasant to me after that.

I noticed the change and asked Kevin about it. He told me what happened, and I was grateful that I went from head-butting 60% of the group to head-butting 40% of the group. Very grateful. As grateful as Kevin's coworker was, because I was saving this guy many, many hours of work.

I think of this story as I sit on the other side. I know I should be grateful when I look at the modules being written in Drupal and see the modules that I have on my to-do list already written, just there for me to download. The modules that have been on my to-do list for over a year, sometimes more. I should be glad that someone else has put forth the effort so that I no longer have to.

And eventually I'm sure I will be happy and grateful for the modules and the completed work. But right now, I'm a little bitter that I wasn't able to actually write them. That my to-do list is a mile long and never seems to get shorter. And when I realize I finally have the time to these projects, I don't have the motivation.

Vicious cycle, this.

Warm fuzzies

Blog

Across the Drupal developer list, an email came across two days ago:

> ...
> The current Module Developers Guide is a great start.  But misses some
> of the details that make everything "click" for a new Drupal coder.

In the Drupal handbook, there is a great resource called "Creating
modules - a tutorial":

http://drupal.org/node/17914

Needs to be updated in places (was written for 4.5), but despite this,
it still does an excellent job of teaching you the basics of Drupal
module development. Grokking the menu callback system, and its central
role as the foundation of almost any page request in Drupal, is
probably the biggest challenge for new developers. Also a challenge is
getting your head around the "hook magic", and how all of that
actually works, and then understanding a few of the more important
hooks in detail (e.g. hook_block, hook_help, hook_nodeapi). This
tutorial will help you to at least begin to overcome these challenges.

Given that I wrote that tutorial, the email gave me warm fuzzies.

Crepes and cars

Blog

Drove up to the City for dinner tonight. I was meeting up with Roland from Bryght, who was down from Vancouver for a conference.

Every time I drive up to the City, I feel guilty. Guilty that I'm not using the mass transportation system that (nominally) works. Guilty that I'm spending over $5 in gas to get there, only to spend another $3 driving around looking for a parking space, and another $5 to drive back.

And yet...

I met Will Pate of Flock, Sarah, Steve, Paul, Roland, Ivan, and Dimitri at the dinner. Tantek, Messina and Tara were all there, too (YAY!). Tara's leaving Riya this Friday, nominally because the new Marketing VP is going to be a suit guy, and because the engineers developing the social software don't actually use the social aspects of the software, and hence have no clue how to build it. Neil showed up later, as did James Walker (having spent over an hour cumulative waiting for connections from BART to MUNI).

I had offered to drive Roland back to Sunnyvale, where he was staying with a friend for the conference. After James showed up, said hello, and socialized for a bit, we started gathering to leave. "Hey, you have a car? Can you drive me to ...?" By the time we actually left the restaurant, I had 5 people in my car, ranging from a quick Haight dropoff, to Palo Alto, Mountain View and Sunnyvale (all of a mile from my house for the last two).

Sure, the car is expensive, non-environment friendly, big and sometimes annoying.

But it sure is convenient at 11:30 at night when you need to be 40 miles away from your current location.

Pages