Former Chrome team member investigates difficulties developing Internet Explorer


What began as a former employee’s praise for Microsoft is now being criticized as “glorifying a toxic work culture” of Education Nonprofit, announced Monday that the development of Internet Explorer was a “sprint” for the team and how hard they worked The Google Chrome browser attacked Partovi, saying that the work culture on the Google Chrome project was nothing special and that everyone only had their 8-hour Adhere to the schedule.

Boodman’s response to Partovi seems to suggest that a company’s performance depends not only on its people working hard, but also smart. Boodman, who said working on the Chrome Project was one of the most defining experiences of his career, added, “Chrome was delivered without sprints,” and there was no drama, broken marriages and broken families.

Chrome shipped without sprints. The team came in at 9 a.m. and walked like clockwork at 5 a.m. (figuratively, people actually kept their own ~ 8 hour schedules) every work day for a couple of years. No drama. No broken marriages, no broken families.

– Aaron Boodman ???????????????? ‍ ???????? (@aboodman) August 16, 2021

Partovi’s Twitter thread described how Microsoft was trying to compete with Netscape Navigator, which held 95 percent of the market in 1995. The Explorer team only had nine people and was “desperately trying to grow as quickly as possible”. Partovi also said the Explorer team is the “hardest working team” he has ever worked with.

Unfortunately, there were divorces and broken families and bad things that came out of it. But I’ve also learned that even in a 20,000-person company, you can get a team of 100 people to work like their lives depend on it.

– Hadi Partovi (@hadip) August 14, 2021

But some of his tweets didn’t go down well.

Hey Cortana, show me “toxic work environment”

– Aditya Mukerjee, the Otterrific ???? ???? ️‍ ???? (@chimeracoder) August 15, 2021

Boodman, on the other hand, said the Chrome team, which managed to “deliver quality software without death marches,” was a “miracle” and explained how it came about.

I hear you ask, dear reader, how this miracle came about. How did the chrome team manage to deliver high quality software without death marches?

Funny that you should ask … It turns out that software projects actually benefit greatly from having senior technical leadership deeply involved.

– Aaron Boodman ???????????????? ‍ ???????? (@aboodman) August 16, 2021

In his next tweet, he described what he meant by “senior” and pointed out that it is common among senior members to “age management and leave typing to children.”

By “older” I mean roughly “old enough to have school-age children at home”.

By “involved” I mean “enter code” and “verify code”.

I know! In our industry, it’s more common for people like this to be left to management and typing to the kids.

– Aaron Boodman ???????????????? ‍ ???????? (@aboodman) August 16, 2021

“There are many benefits to having strong technical leadership, but one of them, of course, is that it leads to a healthier cadence. These people usually have to be home for dinner and are old enough to know that death marches don’t work, ”he added.

On the thread, Boodman also advised people working on software projects on how to build their business by employing experienced engineers to lead their teams.


Please enter your comment!
Please enter your name here