Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Comment from the inside of Bing (Score 4, Interesting) 129

Bing came during the dark phase of MS- during the rule of SteveB. Steve put a culture in MS which was very toxic and obnoxious. Stack ranking had made people self centric, and they we not willing to help their peers, often obfuscated the code, and people went to the extreme of code stealing of others, and making it run under their names. Buttering the managers was common, and "I against you, us against them, and so on" was the mantra.

Bing had no answer to "why choose Bing over Google". During the all hands, this question was asked several times, but never answered satisfactorily by any one. DuckDuckGo figured out the answer- because they redefined user privacy. Bing had no such philosophy because they were blatantly copying Google.

In Bing, people from Yahoo India had come, with their stale ideas and the environment was completely political inside. Instead of writing code, and solving the issue of query share gain in a logical and original way, people generally were asking- "Look what does G show on SERP. Let's try and copy the result". As soon as a new uncharted territory (aka sub-vertical of queries) was found, the whole team would pounce upon it and try to hijack the project.

Even, some women (not all) were promoted because they had illicit affair with their program managers, and that was evident. Often, they would be called inside the chamber, and they would sit beneath the desk, and would be presenting the demo to him. These type of women were promoted on techniques which were shipped, and rolled back within 6 months because the issue ceased to exist, and some other team changed their web pages to more Bing-friendly way.

It was this era which saw exodus of brainy people, who did not want toxicity in their lives. In words of an ex- Principal engineer, "I was not able to make a dent in MS, but in the new company, whatever I do, I see a direct impact happening". The new company he joined was also in the league of giants.

The technology part was not matured inside Bing to be of any use then. The expressive power of language inside Bing was not sufficient enough to tell the ranking algorithm about the exceptions to be considered. As a result, Bing ranker would not work well on a generic playing field like internet.

Another issue that plagued the Bing team was query share distribution. we are talking which type of query has what percentage. Given that Bing used to get only 25% of the traffic volume of Google, the query share used to unrealistic, and most common question used to be- "as per our queries, what is the query share gain?" even though common sense told that queries of particular type should be prevalent.

Next issue was using unnecessary jargon to obfuscate the failures in training various rankers, or finding the query share. The jargon would usually make the talk convoluted, and cumbersome, and the main crux would be lost. Often, the discussions wold stretch hours, with almost no concrete plan to resolve the issue, but instead, tentative exploratory plans, which usually led nowhere.

managers had no clue about machine learning or artificial intelligence. they wanted a series of if-else statements, if that's what took to bring out results in a month's time. they had no time to train a model, test its scores on different metrics, and then ship. they just wanted quick outcomes, which seldom happens in the realm of AI / ML. There were no Ph.Ds initially in the engineering team, neither were any architects or Individual contributors giving design to teams to work upon. People were on their own.

Due to above scenario, usually people who got promoted were either proved loyalists, or the politicking ones. In any case, meritocracy was tossed out of window.

such a culture reflected the nature of top management, which was being copied by their juniors.

With Satya Nadella at helm, stack ranking was abolished for good, and the culture of trust was reinforced. People were pushed now to show results and were held accountable irrespective of the jargon they used, or the hype they created around themselves. However, Bing took too long to come in profit, and that too, too little.

Comment Systemic issue of toxic cesspool (Score 1) 111

Samsung has become a toxic cesspool in technical division- Korean counterparts try to steal good projects from engineers abroad and try to sell it as their own. They track with hawk's eye on who is doing what. As soon as they see if there's anything special going on, they swoop and try to snatch it.

Another set of issue is dominance- Learning department and security depart dominate over engineers. Engineers' belongings are checked when they are leaving, and not when they enter the building. If anything is found, engineers are humiliated and blamed as if they were "stealing" anything. Learning department imposes yearly coding tests, and people are given dedicated time for weeks to compete through that.

All these issues together drove away the cream of the engineers, resulting in the politicking ones staying in, and the quality of software going downhill.

Comment Lessons that weren't meant to be learnt (Score 1) 224

What lessons were learnt from Vista? Windows 8 and 8.1 were horrible messes in themselves, even the microsoft employees didn't use it on their machines. People in the org got a mail saying that if they didn't use 8 in at least one of our machines, they'd be marked as employees not aligning to microsoft's business priorities. Despite this, what many of the managers, and their employees installed it on Hyper V and deleted the instance! So, technically, no one wanted 8.

What lessons were learnt, were learnt half heartedly- PM (Program Manager) org wasn't defined neatly- they could pick up any task, so they picked up nothing- only conducting scrums which would be often be two hours long. What kind of scrum would it be? "I'm blocked at X point" "Because of who are you blocked?" and the finger pointing witch hunting would begin.

What lessons were learnt when MS teams didn't learn the art of working together? What was lacking? the dev culture. The Ballmer's regime had seen lots of privacy keeping tactics developed within teams- people didn't want to lag behind in the stack ranking race, knowing that someone who scores less than 3 would never be able to make up.

Lessons which were learnt were not circulated to top management. No workable strategies were defined, no steps were taken to improve work culture and no grass-root level changes were incorporated in the working of teams. Losing teams were always fire fighting and managers and program managers would keep on asking the SDEs and SDE IIs about what features could they add. It was chaos everywhere. Why did this happen? because the top management wasn't clear of the goals. They couldn't break the goals into small, workable chunk, always blaming the reportees that they were not able to break the work chunk. Even in the article, the author mentions about product being monolithic- why would a product be monolithic? because the higher ups didn't have the structured thinking to break down the issue (read "design") at hand.

The author conveys that he's not ashamed for the handling of affairs at that point of time- the fact that the CEO himself had to pay attention to WinFS file system itself is a signal that things are going towards grave, and there's a need to go back to drawing board.

The problem is not about managing thousands of people for a product, the problem is sitting together, and discussing openly who'd do what, and stick to that plan. Wherever there's no plan, chaos fills in the gaps. This was what was happening at Microsoft in many of the orgs. The HR policies, combined with oldies trying to be new blood, and ignorance / arrogance combined with lack of structured thinking was and is still killing the company which got in spotlight for a while.

Why wasn't the time spent at the beginning of the cycle, and close monitoring, and meticulousness maintained are never the questions on which the author ponders! When you are not pondering, you are not ashamed. When you're not ashamed, you don't learn. And then you rant. Even here the vision is not 20/20 in hindsight.

Comment Re:be same, not equal: Bring value to group, not s (Score 1) 1416

I would suggest, read his memo again. Nowhere does he say women are inferior to men. Mostly he claims that they might not be interested, etc. He says they are different from men. I don't think being different is crossing the line. Difference is like vector, it has components, and can not be compared directly!

Comment Re:be same, not equal: Bring value to group, not s (Score 1) 1416

We all know of products that don't work if you're left-handed, or have a strong Scottish accent, or some other thing created by a homogenous group of designers making unconscious assumptions.

Let us take any group. If there is a value added by including that group, I agree, include them. But from where does the number X% come from? Where does the code of conduct come from? In India, the scene is- Hindus and Muslims are uncomfortable talking (even good) about each others' religions. Men and women, likewise, feel uncomfortable discussing their differences or deficiencies. Why should they, when they are anyways going to be penalised. Management should either ask everyone to not raise the sex related topic, or let everyone discuss it freely. "We are progressive, but we act in haste" is a bad logic to work on.

When there's a need to be filled, there are SME (subject matter experts) who know what customisation would be needed in current design to suit the other party. For example, by just hiring women developers, or hiring 50% women, one can not make products which are women oriented. A woman can partly be true about herself, but she can not know what exactly goes where.

Google misfired on this one. They wanted to create an open world where women, if they will, would get into CS without any oppression too. What they created was a secluded world where women are the holy cows and by questioning (which is fundamental to democracy) one would become a villain.

Comment Re:be same, not equal: Bring value to group, not s (Score 1) 1416

Supporting free speech is the best option.

+1

Also, people should be allowed to think, but they should be guided to corroborate their thoughts with evidences and facts. When the issues are emotional, facts become best guides. They may hurt for a moment, but eventually, you come to terms with the truth. In this poor guy's case, if he was wrong, probably, he'd take it to heart and will not improve much, thus the egalitarian world idea was defeated for this and many such individuals.

Comment Re:be same, not equal: Bring value to group, not s (Score 1) 1416

My assumption is that this guy is a PhD, and from Harvard, and working in G. He has sufficient brilliance to understand where the line is drawn. Instead of discussing his train of thought, and showing him "WHY" along with "WHERE" he was wrong, he'd have understood.

Code of conduct is written by people- and it can have issues. Let's not hurry up saying that the rule is cast in stone and will never change. May be there's an issue, may be not. But when a person (probably a thinking person) spent 3400 words' worth of time penning the article, he might have spent some time thinking.

If sexism is the thought that needs to be eradicated, it must be shown where is the issue in that, again and again, whether it's hundred or thousand times, immaterial.

Firing the person has done what, you have seen that. The whole situation turned lose-lose. It was the worst resolution ever.

Also, why should there be a number, like X% women (or put any other name of group, like Chinese, foreign students, aliens, blacks / browns etc) must be in this org?

What the people want is a fair world towards everyone. For that, the rules and discipline should be inculcated, rather than fixing a number. Let the number be flexible, as in a free market. Those who feel good about the cause will come and join. This will show the real picture of how many women are interested in say, literature vs Computer Science vs say, just being home makers? Ideally, this should be the case. Numbers are constructs which force people without reason.

Comment Re:be same, not equal: Bring value to group, not s (Score 1) 1416

"Our co-workers shouldn’t have to worry that each time they open their mouths to speak in a meeting, they have to prove that they are not like the memo states, being “agreeable” rather than “assertive,” showing a “lower stress tolerance,” or being “neurotic.”

Had they shown him the psychology journals and that the studies show otherwise, he'd have stood corrected. Probably with a warning to write substance backed claim, he'd have a better depth. What did that guy learn? What message was passed to the world and other employees?

Slashdot Top Deals

Anything cut to length will be too short.

Working...