Earlier quoted context omitted.
I'm curious why there's this perception that the vast majority of Google engineers work on mundane stuff. Yes, there's mundane work in any job. There is less of it in Google than in other places, even including the startups I've worked at, because when you operate at Google-scale, even simple things become an interesting technical challenge. It's sorta hard for me to point out specifics because most of Google's inter…
> even simple things become an interesting technical challenge. It depends on your perspective. This also means that you can spin for a year or more just getting one feature out the door. I think I had about 10 meetings over six months on whether addresses for Google Checkout would contain two or three address lines, and whether we needed a separate field for France's CEDEX postal codes. Some of this was justified as…
On the plus side, you learn from many, many different perspectives this way. It's like Peter Norvig's advice in "Teach yourself to be a programmer in 10 years":
1.) Get involved in a language standardization effort.
2.) Have the good sense to get yourself off the language standardization effort as quickly as possible.
Great way to learn, perhaps not such a great way to get things done.