Why Should I Care What Color the Bikeshed Is?_Health & Fitness

Why Should I Care What Color the Bikeshed Is?From freebsd.org/doc/en_US.ISO8859-1/books/faq/misc.html#bikeshed-painting.See phk.freebsd.dk/sagas/bikeshed for historical background;see also Poul-Henning Kamp's regular column TheBikeshed at the ACM."The really, reallyshort answer is that you should not. The somewhat longer answer isthat just because you are capable of building a bikeshed does not meanyou should stop others from building one just because you do not likethe color they plan to paint it. This is a metaphor indicating thatyou need not argue about every little feature just because you knowenough to do so. Some people have commented that the amount of noisegenerated by a change is inversely proportional to the complexity ofthe change."Subject: A bike shed (any colour will do) on greener grass...From: Poul-Henning Kamp Date: Sat, 02 Oct 1999 16:14:10 +0200Message-ID: Sender: [email protected]: Blind Distribution List: ;MIME-Version: 1.0[bcc'ed to committers, hackers]My last pamphlet was sufficiently well received that I was notscared away from sending another one, and today I have the timeand inclination to do so.I've had a little trouble with deciding on the right distributionof this kind of stuff, this time it is bcc'ed to committers andhackers, that is probably the best I can do. I'm not subscribedto hackers myself but more on that later.The thing which have triggered me this time is the "sleep(1) shoulddo fractional seconds" thread, which have pestered our lives formany days now, it's probably already a couple of weeks, I can'teven be bothered to check.To those of you who have missed this particular thread: Congratulations.It was a proposal to make sleep(1) DTRT if given a non-integerargument that set this particular grass-fire off. I'm not goingto say anymore about it than that, because it is a much smalleritem than one would expect from the length of the thread, and ithas already received far more attention than some of the *problems*we have around here.The sleep(1) saga is the most blatant example of a bike sheddiscussion we have had ever in FreeBSD. The proposal was wellthought out, we would gain compatibility with OpenBSD and NetBSD,and still be fully compatible with any code anyone ever wrote.Yet so many objections, proposals and changes were raised andlaunched that one would think the change would have plugged allthe holes in swiss cheese or changed the taste of Coca Cola orsomething similar serious."What is it about this bike shed ?" Some of you have asked me.It's a long story, or rather it's an old story, but it is quiteshort actually. C. Northcote Parkinson wrote a book in the early1960'ies, called "Parkinson's Law", which contains a lot of insightinto the dynamics of management.You can find it on Amazon, and maybe also in your dads book-shelf,it is well worth its price and the time to read it either way,if you like Dilbert, you'll like Parkinson.Somebody recently told me that he had read it and found that onlyabout 50% of it applied these days. That is pretty darn good Iwould say, many of the modern management books have hit-rates alot lower than that, and this one is 35+ years old.In the specific example involving the bike shed, the other vitalcomponent is an atomic power-plant, I guess that illustrates theage of the book.Parkinson shows how you can go in to the board of directors andget approval for building a multi-million or even billion dollaratomic power plant, but if you want to build a bike shed you willbe tangled up in endless discussions.Parkinson explains that this is because an atomic plant is so vast,so expensive and so complicated that people cannot grasp it, andrather than try, they fall back on the assumption that somebodyelse checked all the details before it got this far. Richard P.Feynmann gives a couple of interesting, and very much to the point,examples relating to Los Alamos in his books.A bike shed on the other hand. Anyone can build one of those overa weekend, and still have time to watch the game on TV. So nomatter how well prepared, no matter how reasonable you are withyour proposal, somebody will seize the chance to show that he isdoing his job, that he is paying attention, that he is *here*.In Denmark we call it "setting your fingerprint". It is aboutpersonal pride and prestige, it is about being able to pointsomewhere and say "There! *I* did that." It is a strong trait inpoliticians, but present in most people given the chance. Justthink about footsteps in wet cement.I bow my head in respect to the original proposer because he stuckto his guns through this carpet blanking from the peanut gallery,and the change is in our tree today. I would have turned my backand walked away after less than a handful of messages in thatthread.And that brings me, as I promised earlier, to why I am not subscribedto -hackers:I un-subscribed from -hackers several years ago, because I couldnot keep up with the email load. Since then I have dropped offseveral other lists as well for the very same reason.And I still get a lot of email. A lot of it gets routed to /dev/nullby filters: People like Brett Glass will never make it onto myscreen, commits to documents in languages I don't understandlikewise, commits to ports as such. All these things and more gothe winter way without me ever even knowing about it.But despite these sharp teeth under my mailbox I still get too muchemail.This is where the greener grass comes into the picture:I wish we could reduce the amount of noise in our lists and I wishwe could let people build a bike shed every so often, and I don'treally care what colour they paint it.The first of these wishes is about being civil, sensitive and intelligent in our use of email.If I could concisely and precisely define a set of criteria forwhen one should and when one should not reply to an email so thateverybody would agree and abide by it, I would be a happy man, butI am too wise to even attempt that.But let me suggest a few pop-up windows I would like to seemail-programs implement whenever people send or reply to emailto the lists they want me to subscribe to: +------------------------------------------------------------+ | Your email is about to be sent to several hundred thousand | | people, who will have to spend at least 10 seconds reading | | it before they can decide if it is interesting. At least | | two man-weeks will be spent reading your email. Many of | | the recipients will have to pay to download your email. | | | | Are you absolutely sure that your email is of sufficient | | importance to bother all these people ? | | | | [YES] [REVISE] [CANCEL] | +------------------------------------------------------------+ +------------------------------------------------------------+ |Warning: You have not read all emails in this thread yet. | |Somebody else may already have said what you are about to | |say in your reply. Please read the entire thread before | |replying to any email in it. | | | | [CANCEL] | +------------------------------------------------------------+ +------------------------------------------------------------+ |Warning: Your mail program have not even shown you the | |entire message yet. Logically it follows that you cannot | |possibly have read it all and understood it. | | | |It is not polite to reply to an email until you have | |read it all and thought about it. | | | | A cool off timer for this thread will prevent you from | | replying to any email in this thread for the next one hour | | | | [Cancel] | +------------------------------------------------------------+ +------------------------------------------------------------+ | You composed this email at a rate of more than N.NN cps | | It is generally not possible to think and type at a rate | | faster than A.AA cps, and therefore you reply is likely to | | incoherent, badly thought out and/or emotional. | | | | A cool off timer will prevent you from sending any email | | for the next one hour. | | | | [Cancel] | +------------------------------------------------------------+The second part of my wish is more emotional. Obviously, thecapacities we had manning the unfriendly fire in the sleep(1)thread, despite their many years with the project, never caredenough to do this tiny deed, so why are they suddenly so enflamedby somebody else so much their junior doing it ?I wish I knew.I do know that reasoning will have no power to stop such "reactionaireconservatism". It may be that these people are frustrated abouttheir own lack of tangible contribution lately or it may be a badcase of "we're old and grumpy, WE know how youth should behave".Either way it is very unproductive for the project, but I have nosuggestions for how to stop it. The best I can suggest is to refrainfrom fuelling the monsters that lurk in the mailing lists: Ignorethem, don't answer them, forget they're there.I hope we can get a stronger and broader base of contributors inFreeBSD, and I hope we together can prevent the grumpy old menand the Brett Glasses of the world from chewing them up, spittingthem out and scaring them away before they ever get a leg to the ground.For the people who have been lurking out there, scared away fromparticipating by the gargoyles: I can only apologise and encourageyou to try anyway, this is not the way I want the environment inthe project to be.Poul-Henning