John Poelstra

Entries from February 2008

Miserable Job

February 23, 2008 · 1 Comment

Have you ever had a job you did not like?

This book–described as a page turner by one reviewer–is a fable illustrating what separates good jobs from bad ones. I think it also speaks clearly to the keys for success in any situation where a group of people is trying to accomplish a common goal. The story moves quickly, and while contrived at times, makes Patrick Lencioni’s three main points clear.

Lencioni contends that there are three primary contributors to a miserable job which he describes in the following way:

Anonymity

People cannot be fulfilled in their work if they are not known. All human beings need to be understood in a position of authority…. People who see themselves as invisible, generic, or anonymous cannot love their jobs, no matter what they are doing.

Irrelevance

Everyone needs to know that their job matters, to someone. Anyone. Without seeing a connection between the work and the satisfaction of another person or group of people, an employee simply will not find lasting fulfillment.

Immeasurement

Employees need to be able to gauge their progress and level of contribution for themselves. They cannot be fulfilled in their work if their success depends on the opinions or whims of another person, no matter how benevolent that person may be. Without tangible means of assessing success or failure, motivation eventually deteriorates as people see themselves as unable to control their fate.

Lencioni concedes that immeasurement is not a word in the dictionary sense, yet contends that creating this word is the best way to makes his point.

Thinking back to different jobs I’ve had, it is fairly easy to sort out the winners and losers based on this criteria. In some cases it is clearer now why I was dissatisfied and moved on.

While Lencioni’s target audience is the traditional employeee employer relationship, these same attributes carry over into most forms of satisfying work–including open source projects. Naturally in most cases community members are not paid or employees in the traditional sense.  And if a project is failing in all three areas, most people won’t stick around. The whole notion that open source projects thrive and succeed simply because a bunch of people “got together to scratch a common itch” is too simplistic and not sustainable long term.

Unintentionally, I’ve been thinking a lot about irrelevance and immeausurement as I’ve worked with Jon Stanley to help relaunch the bug triage effort. Who wants to invest time trying to make a dent in 13,000 open bugs if it does not appear that their efforts are relevant? Who wants to triage bugs day after day if there is no way to measure their progress? Who wants to incur the occasional wrath of frustrated bug reporters and package maintainers if no one recognizes their efforts? Long term, even if people feel that their efforts are relevant and showing measurable progress, they will eventually get discouraged if they do not feel their individual efforts are recognized–anonymity.

The punch line here for anyone interested in helping with Fedora bug triage is that we are doing our best to make sure it is is not a miserable job :-)

The concept of immeasurement puts a positive spin on metrics–often the bane of many individual contributor’s existence. Lencioni suggests how miserable basketball players would be if no score was kept and the winning team was selected by a group of subjective judges. Or how miserable a baseball pitcher would be if his performance was judged by the gut level of his coach instead of the statistical results of his performance. As a counter point, Lencioni also suggests that if the people being measured consider the metrics onerous, the wrong things are probably being measured and are not helpful. Naturally, the best measurable items are usually ones that the measuree agrees are relevant and important, and thus buys into.

This is a great book for anyone that does work of any kind. Its target audience is encouraging managers and CEOs to treat their people well and the compounding benefits that can result. Employees can take just as much away. It is also a great read for anyone unhappy in their present job.

Lencioni suggests asking potential new employers how they treat their employees in terms of anonymity, relevance, and measurement during the interview process. If you don’t get a good sense about these three areas the chances of finding a new satisfying job are probably low. This book also helps explain why a job that appears very mundane to you could be very satisfying to someone else.

Another highly recommended by book by Patrick Lencioni is The Five Dysfunctions of a Team. It includes a number of great insights into well functioning teams and how to lead them. It is a short quick read, told in the same fable style as Three Signs of a Miserable Job.

Categories: Bug Triage · Productivity
Tagged: , , , ,

Fedora Jigdo

February 19, 2008 · 6 Comments

I first became interested in using jigdo (Jigsaw Download) during the test releases for Fedora 8. I was spending a lot of time getting the DVD ISOs over bittorrent and was annoyed that in all probability I already had packages necessary to compose the release, but not in its official form from the rawhide trees I mirror locally.

Jigdo has the ability to start with a base image and build ISOs based on local (or remote) packages. I gave it try with some of the Fedora Unity Respins, helped test one of the Fedora 8 respins, and recently built the Fedora 9 Alpha ISO myself using jigdo.

There has been noticeably more interest in jigdo on the fedora-list@redhat.com mailing list over the past few months. This is interesting considering how summarily dismissed jigdo has been as “not being needed” by some of the regulars on the fedora-devel-list. The first time I heard jigdo mentioned was at the Red Hat Summit 2007 during the Revisor session. When I asked some of the Fedora veterans why Fedora didn’t use it I was told it was unreliable, full of memory leaks, and “that old thing from Debian”.

Is this the same disconnect between the folks who think CD releases of Fedora don’t matter and those that do? A classic “developer doesn’t think user wants or needs what the user says they need”? CD releases will be back for Fedora 9 and I think one of the reasons was the complaints from users on fedora-list.

The other arguments I’ve heard against doing jigdo is that it would not benefit enough users or would cause confusion by adding “yet another method to obtain Fedora”. I don’t find any these arguments strong enough to believe Fedora should not provide jigdo as a download option.

Looking at the Fedora Unity’s jigdo statistics people are using jigdo to get Fedora. How many more people could we get Fedora to if it was a mainstream option and how big is the risk if we try?

Speaking from personal experience I think providing direct jidgo support by Fedora would be a great thing. I have never had problems with jidgo or problems with the ISOs it creates. It provides a good alternative for people who cannot use bittorent or have limits on how much bandwidth they can use in a given period.

Who knows, maybe it will become a reality: http://fedoraproject.org/wiki/Features/JigdoRelease

Categories: Fedora
Tagged: ,

GTD Now

February 3, 2008 · 1 Comment

Nice to see a few recent posts on GTD (Getting Things Done) on Planet Fedora by Paul Frields and Luis Villa. I haven’t had time to read the book yet, but I have heard really good things about it. I have listened to the excellent interviews with David Allen (author) by Merlin Mann from 43folders. They are all full of good ideas. All the interviews are here.

A great book I came across while perusing 43folders is The Now Habit. I started with this book because procrastination can get in my way more than being organized. Maybe once I finally read GTD I will find that this hypothesis is wrong.

For some reason the subtitle: A strategic program for overcoming procrastination and enjoying guilt-free play struck me funny, but the content inside is solid and not that long of a read at approximately 200 pages. Included are several practical exercises and tools I found helpful too.

Either way, both books can definitely sharpen Execution.

Categories: Productivity

Execution

February 1, 2008 · 1 Comment

Robert Safian, editor of the excellent magazine Fast Company, writes a thought provoking introduction titled “Inspiration and Perspiration” in the latest issue.  It is the background to the issue’s cover story about Dirty Jobs’ Mike Rowe for the February 2008 issue.

Here are some sections that struck me as I thought of about the Fedora Project:

But Rowe’s story also allows us to examine an underappreciated aspect of economic success: the genius of expertly executed craftsmanship.  It is the glue that cements ideas, on one end, and hard work, on the other, to fuel productivity.  Either type of asset is squandered if inappropriately deployed.  Execution is the great differentiator in our global economic competition.

Then commenting on another article about architectural problems with MIT’s Stata Center, Safian notes:

…the problems more likely stem from how Gehry’s design was brought to life than from any flaws in the design itself.  Even a brilliant concept may be destined for trouble if not married to brilliant execution.

And in conclusion:

How do we balance the importance of creative ideas with the imperative of erecting buildings that don’t leak or software that doesn’t crash or TV shows that actually entertain?

Is it a reach to apply this to Fedora in the sense that we may have excellent creative ideas, innovative new features, all free and open source software, and the best intentions for better community engagement?  And yet if we fail to execute we fail to differentiate ourselves as a project?

Categories: Fedora · Productivity