Just before I left for Origins, the poster you see off to the right was delivered to my home. It’s an artistically-lettered print of a poem by Neil Gaiman, entitled “Before You Read This.”

It’s a wonderful poem, and I deeply appreciated getting it. But there was no note. I had no idea who sent it.

It took a little while, but I found it was my partner in crime, Kris Johnson. I wanted to thank him publicly for being such a swell guy, and for getting me something because, in his words, “I knew you’d like it.”

The great thing about the poem (which will be framed and placed over my desk in my office), is that it invokes more images than it describes. What I mean is, as you read it, it pulls ideas to the forefront of your mind, and so far, I’ve found that it jumpstarts my creative process. Like a meditation.

If you want to have a little fun, follow the link and read the poem from the end to the beginning. To twist things, read some of the stanzas as “Before You Write This.” It takes on whole new meanings.

Buy one for yourself from the talented Todd Klein.

In this episode of of the podcast, I talk a little bit about coming back from Los Angeles, the state of my various projects, and go into some details about the fiun had at Origins 2009 this year. Also, a bonus rant/ramble about why people like me are the Game Vendors’ Worst Nightmare:

Links for this show:

• Pinax
• Origins 2009
• War, Season 5 of Heaven
• Fluxx and Family Fluxx
• Are You The Traitor?
• Necessary Evil
• The Cthulhu Mythos Encyclopedia

Names dropped: Kris Johnson, Jim Van Verth, Mur Lafferty, Ken Newquist, David Moore, Erin Moore, Natalie Metzger, Andy Steigle, John Cmar, Laura Burns

Download the show here.

Podcast: Play in new window | Download

I’m not sure about you guys, but the world is wearying me more easily these days.

It might be the last two years of absurdly hard work on my part, it might be the move back home. It might be starting a new job.  it might be all of these things, but I feel like it goes deeper than that.

Sleep can recharge the body, but how does one recharge the soul?

That’s where the weariness lies, I think. Life fatigue — the spirit is weak.  The speed at which things happen, the constant barrage of media, of the tasks you MUST do, the sense of false urgency that surrounds us today.

I was out in L.A. when I realized that I spent so much time “reasoning” things out (read: whistling in the dark), trying to control situations around me, that in the end, I felt like it was all slipping through my fingers because you cannot hold on to so much. My wife calls it living in my head. Critical thinking is good, but sometimes it’s better to feel; to drink in life instead of breaking it down so you can digest it.

The soul doesn’t exist to consume the world. It’s meant to experience, revel in, and produce beauty.

I know that all of you reading this are busy people, so I ask you, how do you take care of your soul?

Phil Plait’s latest article flew past me on Twitter today, and I was speedy enough to catch it and give it a read.

Read this before continuing: http://blogs.discovermagazine.com/badastronomy/2009/03/24/from-distant-planets-to-the-deep-blue-sea/.

I happen to agree with him that even in times like these we need to fund scientific research, in fact, I’d point out that especially in times like these. When the economy is uncertain, it’s all too easy to gaze into the complexity of the problems that face us and want to run screaming into the arms of a comfortable superstition to make us feel better.¹

Good science brings hope. It’s good for the country’s morale. When we make progress, when we understand more about the world around us, we are made a better people. We have a goal, beyond trying to figure out just how to undo what the greed of a few has wrought.

I want to cry when I see how NASA has fared in the last 20 years, perhaps longer, because the boneheads in Congress lack the foresight to embrace science as a priority. My father worked for NASA, and I was lucky to be one of those kids exposed to the Wonder of space and science at an early age. I want my children to have the same, but these days, NASA gets more press when things go wrong than when things go right. That’s an injustice of the highest kind.  We take the Space Shuttle and other advances for granted, forgetting what marvels they are.

I could not agree more with Dr. Plait’s final statements:

It is not only possible, but I believe mandated, that all of us who love science and want to further the knowledge of humanity support each other’s endeavors. The public does in fact have a great interest in many fields of science, including space exploration, ocean exploration, biological exploration…

The key word there is exploration, and there’s enough Universe out there for everybody.

1. No, I’m not talking about Atheism or Religion here. I’m talking about the unreasonable ticks that arise in every one of us when faced with something out of our control.[back]

photo credit: Jonathan D. Blundell

Working as a team lead in any company is especially challenging. A lead developer straddles the gap between the coders and management, forced to take communication from one side and relay it in a manner the other can understand. It’s tricky business, and it’s not something you learn in school.

Here are a few tips I’ve picked up in the last few years, some of them learned the hard way. I hope they’ll serve you well.

1. Provide Solutions: Management is looking for your expertise, even when they think they know better. Temper your speech. It’s easy to get into the habit of saying “No, that won’t work because…” Don’t throw up barriers. You’ve gotten this far in your career because you’re good at what you do, so use your experience to find the creative solution.
2. Accept Input: Listen to your developers. There are days that they’ll know more about the current state of the codebase than you well. If you are lucky, you are leading people who are talented in disciplines that you are not. Listen to these people, accept their input.
3. Make The Call: Eventually, the discussion has to end. Take the data and make the best decision you can. That’s your job.
4. Play It Straight: Be honest. When you screw up, take the blame. When it’s your team, deal with it.  Trying to hide errors just compounds the problem. Without honesty there can be no trust.
5. Share Knowledge: The most fun I have with my team at Mahalo is when we are talking about tech, sharing ideas, new code, and new methods of getting the job done. This is real team-building. As developer, we prize knowledge above most other things. Share it with your team. Learn from them as well. Don’t be afraid to ask someone to teach you a skill you’ve wanted to learn.
6. Keep It Short: Management doesn’t really care how an HTTP Request Handler works.  Keep your explanations short and to the point. Ask if they want more detail. Understand that speaking techie will alienate non-techies, and will cause a slight distrust of what you’re saying. If you cannot avoid giving a technical answer, keep it short and sweet.  It’s not their job to know how it works, they just want to know it works.
7. Choose Your Battles: Your development team will inevitably want things that management cannot provide, and management will always mandate things that are not easy to do. It’s your job to find the middle ground. That will usually mean compromise, and while it’s not pretty, it’s how the sausage is made.  Save the digging in of heels for when you really need it.  An extra button or a different way of processing a form is not worth the trouble, in general, but a new form that causes the entire database to change is worth the fight. You’re not just there to take orders…you’re the caretaker of the project. Give feedback, and if you are overruled, determine how far you’re willing to take it. Be realistic in your assessment: is it a true battle to be fought or merely an inconvenience?
8. Keep A Journal: Keep a journal of the projects you run. Take notes, so you can remember why decisions were made. There will be times that you’ll look at some piece of code and you’ll have no idea why it’s doing what it’s doing. Your journal will save you from the ever-embarrassing “I dunno.”