3 ms·
You're not getting the point. Chrome never needed to slay itself, because there was no customer expecting delivery. It literally couldn't be late because ther
by cmrdporcupine 4y ago
You're not getting the point.
Chrome never needed to slay itself, because there was no customer expecting delivery. It literally couldn't be late because there was no set schedule. It was done when the engineers finished it.
Like many projects at Google. My experience in general is they don't do schedule-discipline well at all. And management there seems to think throwing ever more headcount at things will make them ship faster (it rarely does).
And there's very little accounting when promised dates are missed. Even by years. I worked on the software for Home Hub, and everything was supposed to get rewritten in Fuchsia, and they promised to be ready in like two quarters, almost immediately after we shipped it. They had unlimited headcount and the blessing of upper management, but failed schedule after schedule with no consequence. It took them another two and a half years.