21–30 of 86 posts
This article has been shared at least 10 times before on HN over the last decade. Amazing to see people organically find it over the years.
Including this one, 34 times :')
Reminds me of a story a friend related a long time ago about how to manage bosses. That probably applies to bike sheds. The general idea is to introduce a glaring mistake into any proposal you make. Then the boss (or whoever feels like bikeshedding) can "catch" that mistake upon which you congratulate them on their infinite wisdom, fix the mistake, and the project can move along. So to avoid the bikeshed color discus…
How does one do this without appearing incompetent?
I also think the idea here is to apply it to bosses who's self-worth seems to be tied to putting their mark on the product without being burdened by knowledge. (Because they'll want to change something regardless of the state)
Reminds me of a story a friend related a long time ago about how to manage bosses. That probably applies to bike sheds. The general idea is to introduce a glaring mistake into any proposal you make. Then the boss (or whoever feels like bikeshedding) can "catch" that mistake upon which you congratulate them on their infinite wisdom, fix the mistake, and the project can move along. So to avoid the bikeshed color discus…
https://blog.codinghorror.com/new-programming-jargon/#:~:tex...
Reminds me of a story a friend related a long time ago about how to manage bosses. That probably applies to bike sheds. The general idea is to introduce a glaring mistake into any proposal you make. Then the boss (or whoever feels like bikeshedding) can "catch" that mistake upon which you congratulate them on their infinite wisdom, fix the mistake, and the project can move along. So to avoid the bikeshed color discus…
How does one do this without appearing incompetent?
Comedy sketch writers would write a throwaway that was too off the wall to air, then include it in their proposal among others to make sure their darlings made it through.
I'm also reminded of the story of the Tetris contract in which a revision of the contract had an important change of a few words, and also an increase of some other fee. This fee change stole the attention and hid the other more insidious revision.
See also a rebuttal of sorts [1] from Brett Glass, the sole programmer singled out by name in phk's essay: > Poul-Henning's assertion that all such ideas should be dismissed as "bikeshedding" reflects this dismissive attitude, which can be just as damaging to a software project as taking too many suggestions (or accepting bad ones). At the time of the discussion I mention above, internal squabbles drove several talen…
Grabbing that domain, they must have quite an axe to grind. Not that the attack on them was any less childish.
Reminds me of a story a friend related a long time ago about how to manage bosses. That probably applies to bike sheds. The general idea is to introduce a glaring mistake into any proposal you make. Then the boss (or whoever feels like bikeshedding) can "catch" that mistake upon which you congratulate them on their infinite wisdom, fix the mistake, and the project can move along. So to avoid the bikeshed color discus…
Reminds me of a story a friend related a long time ago about how to manage bosses. That probably applies to bike sheds. The general idea is to introduce a glaring mistake into any proposal you make. Then the boss (or whoever feels like bikeshedding) can "catch" that mistake upon which you congratulate them on their infinite wisdom, fix the mistake, and the project can move along. So to avoid the bikeshed color discus…
The printed version, should, if dropped on a desk from about a foot, make a thud.
Then write the summary that is short, sweet, to the point, and nothing but glowing.
Every one will just smile and nod and agree with you.
This article has been shared at least 10 times before on HN over the last decade. Amazing to see people organically find it over the years.
Ask HN: How do you avoid bikeshedding? - https://news.ycombinator.com/item?id=30959723 - April 2022 (14 comments)
Why Should I Care What Color the Bikeshed Is? - https://news.ycombinator.com/item?id=29772108 - Jan 2022 (1 comment)
Why Should I Care What Color the Bikeshed Is? (1999) - https://news.ycombinator.com/item?id=12533079 - Sept 2016 (52 comments)
Bikeshedding - https://news.ycombinator.com/item?id=12403557 - Sept 2016 (31 comments)
Why Should I Care What Color the Bikeshed Is? (1999) - https://news.ycombinator.com/item?id=6188408 - Aug 2013 (31 comments)
Why Should I Care What Color the Bikeshed Is? - https://news.ycombinator.com/item?id=1739203 - Sept 2010 (2 comments)
Why Should I Care What Color the Bikeshed Is? - https://news.ycombinator.com/item?id=272246 - Aug 2008 (14 comments)
Why Should I Care What Color the Bikeshed Is? - https://news.ycombinator.com/item?id=25888 - June 2007 (4 comments)
Here is the thing. If you have a Convention Manual which calls for a certain color for bike sheds, then you use that. Failing that, if you have several other bike sheds of a certain color, then that's what you use, for consistency with existing bike sheds. The color of the bike shed only doesn't matter if it's the only bike shed, and there is no documentation which has already settled the matter.
The rule there is that it doesn't matter how many style guides you have or tools to auto-style your thing or whatnot people will still find something to nitpick and argue about. If the Convention Manual says all sheds shall be green they'll argue about what shade of green. If it says it should be Magellan Green they'll argue about whether it should be clear coated and what grit should be used to prepare the surface.…