4 ms·

I am not opposed to all questions. I am opposed to the questions that are typically asked by those who prefer open spaces. I am also not opposed to basic questi

I am not opposed to all questions. I am opposed to the questions that are typically asked by those who prefer open spaces. I am also not opposed to basic questions asked by those who are new to the field, but I am often asked basic questions by those with 3+ years of experience. Read a book.

nostrademons 16y ago
It's possible we just know different people who prefer open spaces, but the questions I'm frequently asked are more specific variations on "How does Google's serving and indexing pipeline work?" and "What are the best practices for building JavaScript-heavy webapps in an environment where latency matters?" There are obviously no books about those topics (well, there are some about the latter, but they're all wrong, and we have experimental data to prove it). And even if they were, they'd be out of date before they were published. Google's indexing system changed completely when Caffeine was launched last year - the only way to get information about it is to ask the people who're responsible for developing it. And the ecosystem surrounding the web is continually changing, and we keep running new experiments to keep up with it, because things that we were absolutely certain were true 5 years ago no longer are.
- absconditus 16y ago
  Most companies are nothing like Google.
- astrange 16y ago
  > What are the best practices for building JavaScript-heavy webapps in an environment where latency matters? Well, what are they?
  - nostrademons 16y ago
    At the moment, confidential. Google derives a competitive advantage from being fast. I've toyed with the idea of getting permission to release some of the results we've discovered, in maybe a blog series like what Crockford did for JavaScript at Yahoo. Google also derives a strategic advantage from the rest of the web being fast, and IMHO the benefits of making everyone else fast outweigh the benefits of being faster than everyone else. But I've already got a 20% project that takes up like 50% of my time, so I don't have time to organize something like that. Maybe later.

nostrademons 16y ago

It's possible we just know different people who prefer open spaces, but the questions I'm frequently asked are more specific variations on "How does Google's serving and indexing pipeline work?" and "What are the best practices for building JavaScript-heavy webapps in an environment where latency matters?" There are obviously no books about those topics (well, there are some about the latter, but they're all wrong, and we have experimental data to prove it). And even if they were, they'd be out of date before they were published. Google's indexing system changed completely when Caffeine was launched last year - the only way to get information about it is to ask the people who're responsible for developing it. And the ecosystem surrounding the web is continually changing, and we keep running new experiments to keep up with it, because things that we were absolutely certain were true 5 years ago no longer are.

absconditus 16y ago
Most companies are nothing like Google.
astrange 16y ago
> What are the best practices for building JavaScript-heavy webapps in an environment where latency matters? Well, what are they?
- nostrademons 16y ago
  At the moment, confidential. Google derives a competitive advantage from being fast. I've toyed with the idea of getting permission to release some of the results we've discovered, in maybe a blog series like what Crockford did for JavaScript at Yahoo. Google also derives a strategic advantage from the rest of the web being fast, and IMHO the benefits of making everyone else fast outweigh the benefits of being faster than everyone else. But I've already got a 20% project that takes up like 50% of my time, so I don't have time to organize something like that. Maybe later.