What are Google’s most surprising product failures?


What are Google’s most surprising product failures? by Lewis Lin

Answer by Lewis Lin:

Here’s my list of Google product failures:

  • Google Wave. It could have been Slack.
  • Orkut. It could have been Facebook.
  • Google+. It could have been Snapchat or Whatsapp.
  • Google Hangouts on Air . It could have been Facebook Live or Periscope.
  • Google Answers. It could have been Quora.
  • Google Catalog Search. It could have been Pinterest.
  • Dodgeball. It could have been FourSquare or related social networking site.
  • Google Notebook. It could have been Evernote.
  • Google Page Creator. It could have been Squarespace.
  • Google Video. It wasn’t YouTube.
  • Google Glass. It should have waited until it was Google Contact Lens before it launched in the consumer market.
  • Google Knol. There’s plenty of information that can be Wiki-fied like dev documentation for open-source projects. Cloning Wikipedia was not the first thing that needed to be Wiki-fied.

Why did these products fail?

It’s not so much that the Googlers were lazy or incompetent. I’m positive they were hard working and committed. It’s more that product design is so hard that even the best companies can’t succeed 100% of the time.

Craig Lawrence pushed me to think a bit harder as to why Google failed. Despite hard work and commitment, here are reasons why Google failed so often:

  1. Lack of vision. There are only so many people who can predict the future. Sundar Pichai was one of those rare individuals who saw the Chrome browser and Chromebook OS opportunity, despite daunting odds and endless customer naysaying.
  2. Lack of resources. When I was at Google, I believe Google Notebook had half an engineer working on it a few months out of the year. Hard to defend the fort if the guard tower is empty.
  3. Lack of insight. The Google Wave and Google Glass team worked hard, but both teams missed the critical insight that others realized. That is, Slack realized work messages belong to channels. And Google Glass was too dorky to wear in public.
  4. Lack of focus. Google+ included everything but the kitchen sink. It was an authentication service. And a commenting plug-in. And an address book. And a multi-user video conferencing feature. It felt and was designed by committee.
  5. Lack of trying. I believe Marisa Mayer once said, “There are great (product) ideas that are executed poorly.” In other words, we shouldn’t conclude an idea is flawed because it failed. After Google Answers shut down, it was wrong to conclude that the Internet didn’t want a Q&A service. It was more appropriate to conclude that Google Answers just implemented Q&A the wrong way.

What’s the best way to avoid product failure?

From an organizational perspective, the best solution I’ve seen is the spinoff.

I’ve seen Expedia achieve good success after it was spun off from Microsoft.

And Expedia, apparently having seen the spinoff tactic work successfully, helped TripAdvisor flourish by spinning them off as well.

What are Google’s most surprising product failures?

L’Innominato ha un nome: Alessandro Manzoni


Sottoosservazione's Blog

Stefano Andrini per “Avvenire

«L’Innominato sono io». Parola di Alessandro Manzoni. La rivelazione, inedita, è stata lanciata dall’italianista Ezio Raimondi nel corso delle Giornate dell’Osservanza organizzate a Bologna per ricordare il centenario della conversione dell’autore dei Promessi sposi avvenuta nel 1810. Un’occasione per affrontare il tema della metanoia e della conversione sia sotto il profilo filosofico (Massimo Cacciari) e linguistico (il rettore dell’Università Ivano Dionigi). 

Raimondi ha ricordato che Manzoni non amava parlare della sua caduta da cavallo avvenuta il 2 aprile 1810, quando in mezzo alla folla la moglie svenne e lui si ritrovò in una chiesa dove fu investito da una nuova epifania. «Non c’è da meravigliarsi – ha affermato l’italianista – di questo suo pudore. Qui pesa l’umiltà dello scrittore: preferiva i temi romantici, dire “noi” piuttosto che “io”, non aveva neanche come il cardinale Newman il riferimento malizioso agli scrittori. Eppure introduce nel romanzo…

View original post 504 more words

My son got an offer from a 1-year-old startup by some very senior folks from Google. The pay is good and product idea is good, but it’s a…


My son got an offer from a 1-year-old startup by some very senior folks from Google. The pay is good and… by @mdroz8

Answer by Mike Karmindro:

Get your son to put in his 2 weeks notice.

Whether you realize it or not, your question has a wealth of information that makes this decision a no brainer.

Here's my assessment on the situation.

Startup founded by X-Senior-Googlers.  Enough said about the team, esp if they are engineers.

And the pay is goodYou mean he won't have to take a big pay cut in exchange for more potential financial reward (via options),  more interesting/challenging work, an amazing learning experience (being able to work with very smart people),  having a significant impact on a company's success, and acquiring skills that may help him to start his own company one day?  Awesome.

The company is 1 year old.  What does that tell me?  The hires in the early stage of a startup are key to the success of the company.  I consider 1 year still pretty early.     I know nothing about your son, but if these X-Googlers want to hire him this early, he's got to be pretty bright and good at what he does.   These founders are going to be super picky about who they hire, and they chose your son.  Congrats.

Also I'm willing to bet these guys have a pretty good shot at raising money from investors (if they haven't raise plenty already).  Investors know a lot of successful startups are built from former x-employees from top companies like Google.

OK, let's play devil's advocate here.  Let's look at your biggest fear, which is probably the company fails and your son is left without a job.  First, it's going to look great on his resume that a startup built by x-googlers hired him as an early employee.  And remember, your son is probably quite in-demand if these guys want him on their team.  So he's probably going to find another job pretty easily.  And don't forget the amazing experience he just acquired.

I feel very strongly about this because I don't want your son to miss a golden opportunity in his career, especially one that in my opinion has zero risk for him.  I almost walked away from an offer I got from a startup without nearly as good circumstances as your son has, and it turned out to be the single best decision I ever made. 




My son got an offer from a 1-year-old startup by some very senior folks from Google. The pay is good and product idea is good, but it's a…

Have you been hired by Google, Facebook or Microsoft (or another big company) for your performance on programming contests/challenges lik…


Have you been hired by Google, Facebook or Microsoft (or another big company) for your performance on … by Hieu Pham

Answer by Hieu Pham:

In my Junior year at college, I got internship offers from Facebook, Microsoft and Google. Considering my profile at that time, I think the only reason that they wanted me was my contests experience. My team was ranked 2nd in the regional ACM ICPC contest the prior year, and I was yellow on TopCoder, purple on Codeforces.

How do I achieve this? There are several steps.

  1. At the document round, I put my contests performance into my resume, and highlighted that I want to work in algorithm. Usually, for internships, this would bring you to the interview round.
  2. At the interview rounds, answer the questions as flawlessly and quickly as you can. These questions are usually fairly easy if you have any background in programming contests. Don't do anything like "First give a slow algorithm, and pretend as if you were trying to optimize it…", as taught at Hacking a Google Interview. IMO, it's quite dishonest and most interviewers would recognize that.
  3. If you answer all the questions very fast, you may ask for more questions. In case the interviewer did not prepare more, it's your responsibility to come up with questions for him or her. To do so, it is important to do some research about your interviewer beforehand. Stalk their Facebook, LinkedIn, whatever, for their background, school, and interest and prepare about 5 thoughtful questions about them and their team. You would be extremely lucky if your interviewer is involved in programing contest. It was once my case, where I just asked how my contest experience can fit into his team's work.

Good luck!

Have you been hired by Google, Facebook or Microsoft (or another big company) for your performance on programming contests/challenges lik…

Dozen Arrested For Feeding Homeless In Orlando



Photo Credit Mark
via: GovtSlaves.info
June 19, 2016

Members of the organization Food Not Bombs were in good spirits as they passed out corn on the cob, rice, beans and other vegetarian dishes to the homeless and hungry in an Orlando park. This cheer was interrupted when police officers on bicycles arrived and arrested five of the volunteers.

This is not the first time this scene has played out for members of Food Not Bombs.

Since June 1, a dozen members of the group have been arrested for violating a new Orlando city ordinance that prohibits sharing food with large groups in downtown parks more than twice a year.

The mayor of Orlando even branded them “food terrorists.”

Food Not Bombs is an international political organization that protests war, poverty and the destruction of the environment, according to their website. The group meets to distribute food twice a week in downtown Orlando’s…

View original post 148 more words

What are the negatives in working in a too-good-to-be-true offices like Google?


What are the negatives in working in a too-good-to-be-true offices like Google? by Sadia Hdydi

Answer by Sadia Hdydi:

I was offered a job at a company (not Google) with similar perks: free food on site, a margarita machine that was always on, campus gym, etc. I was in my 30s and a single mother. Those “perks” were a massive turn off for me, because I knew that they signaled a desire for employees whose entire life would revolve around work. When I brought up my concerns to the recruiter who was trying to convince me to take the job, she said, “Oh, don’t worry. There are a couple of people who have on their calendars, ‘No meetings after 6:00.’”

I didn’t want my coworkers to perceive me as a slacker because I had life responsibilities outside the office. Instead, I went to do essentially the same job for a company that paid the same amount, but gave me the flexibility to be both the mother and employee that I want to be. I spend 8–10 hours in the office most days and am happy to put in extra hours once my children are asleep, but from 6:00 pm–9:00 pm on weekdays and on weekends, my attention and time belongs to my children.

I work smart and hard, instead of long. An all-inclusive job environment is great for recent college graduates, but those of us who see our careers as an important part of life, rather than all of life, don’t enjoy or want those perks.

What are the negatives in working in a too-good-to-be-true offices like Google?

Why don’t more programmers use regular expressions?


Why don't more programmers use regular expressions? by Jonathan Neve

Answer by Jonathan Neve:

I happen to enjoy regular expressions immensely. So immensely, that in my more rational moments, I feel the need to moderate my enthusiasm by warning people that they actually can't (or at least shouldn't) be used for everything.

The truth of the matter is anything that can be done without a regex probably should be. Of course, I don't mean that literally (since technically, there's nothing that can't be written without a regex), but some problems really lend themselves to regexes, whereas most don't.

In cases that can be solved simply without a regex, the plain solution will most of the time be:

  • Faster to write
  • Faster to debug
  • Faster to run

So again, much as I enjoy using regexes, and perhaps in fact because I enjoy using them so much, I need to hold myself back from using them everywhere. There are times when regexes absolutely shine, such as:

  • Scripts/throw-away/"write-only" code
    Write fast and don't worry about maintaining it
  • One-off search or search and replace
    If you need to grep the list of running processes to find and kill any process matching a certain pattern or started after a certain time, you can do it much faster and easier with a little one-liner involving a simple regex than you could any other way.
  • Very complex text manipulation
    Sometimes, runtime performance doesn't matter much, but using regexes can save a considerable amount of time by avoiding the need to write an all-out, full-blown parser.

    For example, I recently wrote a little Perl script to convert code written in Borland C++Builder to Delphi. This is made possible by the fact that both environments share the same standard libraries, so it's "just" a matter of converting the C++ to Object Pascal. In about 1000 lines of code, most of it regexes, I actually got it to work up to about 95% (100% would probably not be possible). It only took me a few months, no idea how I could have done that without regular expressions.

So in conclusion, I would say that regular expressions are a wonderful and highly addictive tool that should be added to the arsenal of every programmer, yet we must resist the urge to forget all the other unromantic, boring (and, sadly, often better) ways we have of doing simple things.

It should also be noted that the extended notation (/x, also known as the kill-joy option*) allows for turning cryptic regular expressions into readable chunks of code with whitespace and comments, and it might help break the elitism of the regex-writer-band if we were to use this option to make regexes that are intelligible to an actual human. Yeah, it spoils some of the fun, I know, but still…🙂

In case you're thinking I'm exaggerating the quasi-cultishness/elitism of regex users, what do you think it shows that one of the most popular ressources online for help with regexes and Perl in general is called perlmonks.com? The Monastery Gates

*Not really, but that's how it can feel at times…

Why don't more programmers use regular expressions?