In an exhaustive interview with The New York Times, Dr. Eric Schmidt, CEO of Google, shares some of his experiences and insights into technology development at the search giant.

On product roadmaps:

Conventional software is typically built, tested and shipped in two- or three-year product cycles. Inside Google, Mr. Schmidt says, there are no two-year plans. Its product road maps look ahead only four or five months at most. And, Mr. Schmidt says, the only plans "anybody believes in go through the end of this quarter."

On Google's culture:

Google’s quicksilver corporate culture can be jarring for some employees, even for Mr. Schmidt. He recalls that shortly after joining the company and its young founders, Sergey Brin and Larry Page, he was frustrated that people were answering e-mail on their laptops at meetings while he was speaking.

"I've given up trying to change such behavior," he says. "They have to answer their e-mail. Velocity matters."

On rapid development and executive support:

Early this month, Google released new cellphone software, with the code-name Grand Prix. A project that took just six weeks to complete, Grand Prix allows for fast and easy access to Google services like search, Gmail and calendars through a stripped-down mobile phone browser...

...Grand Prix was born when a Google engineer, tinkering on his own one weekend, came up with prototype code and e-mailed it to Vic Gundotra, a Google executive who oversees mobile products. Mr. Gundotra then showed the prototype to Mr. Schmidt, who in turn mentioned it to Mr. Brin. In about an hour, Mr. Brin came to look at the prototype.

"Sergey was really supportive," recalls Mr. Gundotra, saying that Mr. Brin was most intrigued by the "engineering tricks" employed. After that, Mr. Gundotra posted a message on Google's internal network, asking employees who owned iPhones to test the prototype. Such peer review is common at Google, which has an engineering culture in which a favorite mantra is "nothing speaks louder than code."

I like that--*nothing speaks louder than code*.

On releasing software:

As co-workers dug in, testing Grand Prix's performance speed, memory use and other features, "the feedback started pouring in," Mr. Gundotra recalls. The comments amounted to a thumbs-up, and after a few weeks of fine-tuning and fixing bugs, Grand Prix was released. In the brief development, there were no formal product reviews or formal approval processes.

On hiring:

Another draw is Google’s embrace of experimentation and open-ended job assignments. Recent college graduates are routinely offered jobs at Google without being told what they will be doing... "We look for smart generalists, who we can be confident can fulfill any need we have," he explains. "We hire someone, and who knows what need we’ll have when that person shows up six months later? We move so fast."