I’ve used this in the past when I was doing more analytics and it worked great. It’s interesting that you bring up the “good documentation” piece now because I credit this package with finally teaching me what is…
Can you explain the "float" observations and argument?
Engineering: - Infrastructure (500M MAU) - Web Dev - iOS Dev - Android Dev - Design - UX - Localization Data: - Ranking timelines - Ad performance - Recommendations - Business analytics - R&D Product: - Coordinating…
What? This is a really interesting technical design post outlining how they use technology to solve real problems at scale.
Or - or, and just hear me out, there are occasional real world complications that cause unforeseen errors and people only talk about the tail end of poor predictions rather than the 95+% good experiences.
I’ve used this in the past when I was doing more analytics and it worked great. It’s interesting that you bring up the “good documentation” piece now because I credit this package with finally teaching me what is…
Can you explain the "float" observations and argument?
Engineering: - Infrastructure (500M MAU) - Web Dev - iOS Dev - Android Dev - Design - UX - Localization Data: - Ranking timelines - Ad performance - Recommendations - Business analytics - R&D Product: - Coordinating…
What? This is a really interesting technical design post outlining how they use technology to solve real problems at scale.
Or - or, and just hear me out, there are occasional real world complications that cause unforeseen errors and people only talk about the tail end of poor predictions rather than the 95+% good experiences.