In February 2006, U.S. Vice President Dick Cheney accidentally shot and wounded Harry Whittington, a 78-year-old Texas attorney, during a quail hunting trip on a private ranch near Corpus Christi, Texas. Cheney was using a 28-gauge shotgun when Whittington stepped into the line of fire after retrieving a bird. The pellets struck Whittington’s face, neck, and upper torso.
Whittington was hospitalized and later recovered. The incident became a major news story, partly because the White House delayed releasing details for nearly a day, raising questions about transparency. Cheney later called the event “one of the worst days of my life” and publicly accepted responsibility.
The shooting has since become one of the most remembered and parodied moments of Cheney’s vice presidency.
What's missing from this story is that Dick Cheney had the man he shot do a press tour apologizing to Dick Cheney and his family for causing any duress.
>"Roses are red, violets are Blue, if I go to jail, you're gonna go too!" -Scooter Libby
>"Dear Dick: Remember when you shot me in the face? Well down here in Texas, when I go any place, they say 'There goes the guy Dick Cheney shot in the face!'" -Harry Whittington
Cold Opening: Dick Cheney briefs Condoleeza Rice - Saturday Night Live
>Rice: But they have information like the titles of the president's briefing on August 6.
>Cheney: No problem. What was that again?
>Rice: Bin Laden Determined To Attack Inside The United States.
>Cheney: Ok, THAT's bad. Uhh.
>Cheney: All right, let's practice. When they make you say that title, there's going to be an audible gasp in the room. So you've gotta cough, cover up the gasp. Ok, let's practice. [...]
I mean I can't give you my company code but my GitHub is not difficult to find. That said, I'm a little confused by your offer, because I feel like this doomed to fail because you don't have my context as to what I want improved?
Wow, it's almost as if you've never heard of crowd-funded development.
The software behind Firefox can still continue without Mozilla. It may have fewer developers due to reduced funding but I'd rather see slower development if it was moving in the right direction.
> I'd rather see slower development if it was moving in the right direction.
What makes you think it'd happen if full-time employees at Firefox cant do it? We can poop on the leadership over at Mozilla, but there are FTEs getting paid to work on Firefox.
You cant just replace with few people running passion project on weekends, and even get the remote success Firefox has.
Browser is extremely complex. HN is underestimating how much work goes into making a browser.
> What makes you think it'd happen if full-time employees at Firefox cant do it?
The full-time engineers are given work to do by incompetent Mozilla management. It's the management that are driving Mozilla into the ground and setting baffling goals. Remove the management and have work based on features that users want, then you can see Firefox develop in the right direction.
As an example of how to organise this, you could have a bounty system for feature requests. Users define a feature they want to see and in negotiation with developers set acceptance criteria for when it's delivered. Users can then assign money as an incentive to complete the feature request. In this way, users can ensure they support developers to deliver the features they want to see.
> Browser is extremely complex. HN is underestimating how much work goes into making a browser.
Nobody is underestimating this. Firefox is already a mature product that can serve a wide range of user needs. What it lacks is effective leadership. I could live with slower development if the development it had was based around features that users most wanted. I don't need Firefox to support every web feature under the sun, the features it already supports is good enough for the vast majority of websites. Letting the users call the shots about it's future direction will help to guard against irrelevancy.
> As an example of how to organise this, you could have a bounty system for feature requests. Users define a feature they want to see and in negotiation with developers set acceptance criteria for when it's delivered. Users can then assign money as an incentive to complete the feature request. In this way, users can ensure they support developers to deliver the features they want to see.
Could you actually provide any examples of large-scale software projects working this way, and not the usual way with coordination being done by special people or w/o any (e.g., by the devs)
Explain what problems are encountered with 1000 feature requests linked to bounties that aren't encountered with 10 feature requests linked to bounties.
reply