Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>The Engineering team is well aware of the community feedback.

Does that mean Mozilla is aware how unpopular this is, but are going to go ahead nevertheless?

Is there even a single person who wants this feature to be removed?



Well, obviously the Visionary Leader wanted this feature removed. They’ll push against user feedback, quote Ford (”If I asked what the customers want, I would still be selling horses”).

We should have a name for the fallacy of ”Jobs/Ford/etc ignored user requests and they were geniuses. If I ignore users, I’m a genius”


The thing about leadership is it only makes you the leader; a leader is no such thing without a good team.

Jobs actively fought against the App Store within the company until someone finally convinced him it was actually worth doing. A bad leader would have just overruled his team, but a good leader will know when to back down because his team is right.


A leader is someone people choose to follow. Most bosses aren't leaders.


If you have romantic notions of what leaders and leadership is, then sure, that’s a wonderful definition!

Thing is, if you’re in a position of leadership, you’re a leader. If people answer to you and you are in charge of them in any capacity, office, battlefield, whatever, then you’re a leader. Sometimes even in an unofficial capacity if you take it upon yourself to be the get shit done guy and protect others in your group from fallout; this could be called assuming leadership, and if you do it well, people might turn to you as a leader and choose to follow you.

The President of the United States is a leader. He’s elected in a contentious election, and he is the leader of the government’s civil service and diplomacy corps. as well as Commander-in-Chief of the Armed Forces, even if there are people in their ranks that voted for a different guy.

Now whether a leader practices leadership, or is a good leader are entirely different questions. You don’t have to respect your leaders, or like them, for them to be leaders.


I think calling a position of authority a position of leadership is a mistake too. Someone assuming leadership shows the difference.

A contentious election is still an election. We have words like dictator and ruler for unelected political bosses.


It is an election in which members of the government and Armed Forces can expressly choose a different guy to follow and lose, whilst still having their top leader not only replaced, but empowered to replace every member in the chain of command replaced by the person they didn’t choose.

Which is totally legitimate, the President is elected through a constitutional process which is our law. That’s also why I think it makes a great counterpoint to your original assertion: you can choose who you want to follow, but who you actually follow isn’t always who you would choose.

If you join a company either because you like the CEO or you like the guy you’ll be immediately reporting to, everyone else in that chain was chosen by someone else. Your lack of choice in the matter does not absolve them of their responsibility to be leaders, the question becomes whether they have the qualities necessary to be good leaders. And if you are the CEO or directly report to him? Great! You win! Now you’re the guy others are looking up to and hopefully you have good leadership qualities yourself because people will look to you for leadership whether you want them to or not.


Not liking the person other people voted for doesn't change the fact people voted for them. We have words like commander for the military.

Accepting someone has power over you isn't following them. We don't call prisoners followers for example.

I think giving out titles only when people earn them encourages responsibility.


How many people chose to follow Jobs, though? If you got hired by Apple, you worked for him. Apple didn't have a democratic vote with every single employee every year and Jobs turned out to be the winner...

Or are you saying that Jobs wasn't a leader either?

Or maybe you mean that a leader is someone who people follow, and would choose to follow if they were given a choice?

Sorry, maybe kind of nitpicky, but I feel like you're on the edge of saying something important and accurate, but this isn't quite it.


I don’t mind looking for a better way to express the idea.

We don't call people with no choice followers usually. So I think following someone is a choice even when going where they tell you isn't.

It can be ambiguous. Some people joined Apple to work for Jobs. And he was famous for his management style. But I don't know how many people saw him as a leader and how many saw him as the boss.


“Visionary leader fallacy”


"Visionary overreach"


> Is there even a single person who wants this feature to be removed?

It's about cost of maintenance not people wanting a feature to be removed. And while this feature specifically doesn't have to high of a cost (I think) it will sum up if many "hardly used" features are left in place.

> >The Engineering team is well aware of the community > feedback. > > Does that mean Mozilla is aware how unpopular this is, but are going to go ahead nevertheless?

I think it means they decided it, then got feedback and now are potentially reevaluating it.

Also maybe the group of people using it isn't very high but very vocal/loud, in which case going ahead anyway would be reasonable.

Through I also would guess the group of people using that feature is also likely to have analytics disabled...

Having "analytics disabled" correlate with "using that specific feature" is always a major problem for data driven decisions, worse it's a well hidden and hard to estimate problem.


> Having "analytics disabled" correlate with "using that specific feature" is always a major problem for data driven decisions, worse it's a well hidden and hard to estimate problem.

You know, I’m generally a privacy conscious consumer and default to opting out of analytics, but if a company asked me to do a survey about how I use the product I absolutely would! I enjoy giving feedback, but am always going to pass on dragnet surveillance.

I’ve never seen this though. Perhaps I’m naive to certain business interests or statistical techniques, but it seems like such a survey would be a necessary part of a robust decision making process based on mass-surveillance gathered analytics for a product that doesn’t earn money by directly selling that data. (if you only make money by tracking users, I understand why you might not care about users who prevent it, but even then with the power of network effects I’d expect a business would at least want a finger on the pulse)

I mean, I don’t have a degree in stats, but from what I do know this is the kind of due diligence that the foundation of trust in statistics is based on. Maybe I’m just confused and someone can correct me, but I’ve come to see the selective enforcement of good statistical practices as one of the major problems in the world today, because a) I see it so much, b) it gives certainty where little is deserved, c) it prevents us from getting to truth.


> Having "analytics disabled" correlate with "using that specific feature" is always a major problem for data driven decisions, worse it's a well hidden and hard to estimate problem.

It's a bit worse than even this suggests. Using any feature is correlated with having analytics disabled, because the more of a power user someone is, the more they'll use "advanced" features (anything beyond "clicking in the URL bar and typing a search term"), and obviously power users are the only people disabling analytics.

So if anything there's an all-encompassing metrics bias saying "users want fewer features and less complexity".


> It's about cost of maintenance not people wanting a feature to be removed. And while this feature specifically doesn't have to high of a cost (I think) it will sum up if many "hardly used" features are left in place.

There is no maintenance cost as they are keeping the "touch" option. Unless checkboxes are somehow easier maintain than drop-downs.


I bet the QA team won't be sad. This looks like one of those features that requires a complete repass on a ton of UI.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: