Skip to content
HomeVideosBooksBlogs
AllTop postsTopics
Podcasts
HistoryListsWatch laterLiked videosFollowing

The videos, books, blogs and podcasts Hacker News keeps recommending, all in one place.

VideosBooksBlogsPodcastsAboutPrivacySettings

Data from Hacker News, HackerTube, HackerBooks, HackerBlogs and Open Library. Credits · Not affiliated with Y Combinator.

HomeVideosBooksBlogsPodcasts
Ctrl K
    U

    Unofficial Google Data Science Blog

    unofficialgoogledatascience.com · Company blog · on HN since 2015

    Google data scientists write unofficially on data analysis, forecasting, machine learning, and internal tooling.

    Visit blogHN submissions
    Data & VisualizationAI & Machine LearningTech Industry
    What HN says

    Commenters praise the blog and often cite its post on replacing Sawzall with a Go-based DSL, and its advice on exploring data first.

    Stats for nerds
    23HN people shared it
    26linked in comments
    636story points
    Dec 2023last shared
    2016people per year2023

    Top posts on HN

    1. 1
      Practical advice for analysis of large, complex data sets
      6 people · 345 points · first shared 2016 · 32 comments on HN
    2. 2
      Causality in machine learning
      1 person · 127 points · first shared 2017 · 65 comments on HN
    3. 3
      Humans-in-the-loop forecasting: integrating data science and business planning
      2 people · 62 points · first shared 2019 · 6 comments on HN
    4. 4
      Replacing Sawzall – a case study in domain-specific language migration
      5 people · 48 points · first shared 2015 · 5 comments on HN
    5. 5
      Next generation tools for data science
      3 people · 20 points · first shared 2016 · Discussion on HN
    6. 6
      Experiment Design and Modeling for Long-term Studies in Ads
      1 person · 9 points · first shared 2015 · Discussion on HN
    7. 7
      How to get a job at Google as a data scientist
      2 people · 3 points · first shared 2015 · Discussion on HN
    8. 8
      An Introduction to the Poisson Bootstrap
      1 person · 3 points · first shared 2019 · Discussion on HN
    9. 9
      On procedural and declarative programming in MapReduce (2015)
      1 person · 2 points · first shared 2020 · Discussion on HN
    10. 10
      Our quest for robust time series forecasting at scale
      1 person · 2 points · first shared 2017 · Discussion on HN

    What HN people wrote when they linked it

    • in9Dec 2023

      Lately, I've been enjoying a lot of posts in this blog right here:

      https://eugeneyan.com/writing

      My company just hired some new VPs from Amazon, and the writings in that blog convey a bit of the Amazon WOW. It's pretty insightful stuff.

      Also, many posts from Julia Evans :D

      More concretely, here are a few blog posts I go back to occasionally:

      https://doordash.engineering/2019/02/20/experiment-rigor-for-switchback-experiment-analysis/

      https://www.unofficialgoogledatascience.com/2019/12/humans-in-loop-forecasting-integrating.html

      https://www.unofficialgoogledatascience.com/2016/10/practical-advice-for-analysis-of-large.html

      https://eugeneyan.com/writing/ml-design-docs/

      https://eugeneyan.com/writing/what-i-do-before-a-data-science-project-to-ensure-success/#first-draw-the-map-to-the-destination-one-pager

      https://www.fharrell.com/post/addvalue/

      https://www.fharrell.com/post/stat-ml2/

    • shoyerFeb 2017

      Before you try any sort of ML, explore your data [1, 2]. Exploratory data analysis may very well tell you that there is absolutely no point in making a fancy predictive model at all. If a few heuristics get you 90% of the way to an optimal solution, then don't even bother to start on machine learning, unless that last 10% is going to provide significant value.

      [1] https://en.wikipedia.org/wiki/Exploratory_data_analysis

      [2] From one of my mentors: http://www.unofficialgoogledatascience.com/2016/10/practical-advice-for-analysis-of-large.html

    • ebikelawAug 2018

      I guess you meant outside of google? Google's logs analysis is often done in "Lingo" which stands for Logs In Go. I assure you that logs analysis is very CPU bound.

      http://www.unofficialgoogledatascience.com/2015/12/replacing-sawzall-case-study-in-domain.html

    • mikecbNov 2016

      I love this blog. They had a great post describing a privacy preserving query proxy: http://www.unofficialgoogledatascience.com/2015/12/replacing-sawzall-case-study-in-domain.html

    • danmuxAug 2016

      And this : http://www.unofficialgoogledatascience.com/2015/12/replacing-sawzall-case-study-in-domain.html replacing Sawzall with Golang :|

    Related

    Insight Data Science Blogblog.insightdatascience.com85 people

    Generating custom photo-realistic faces using AI

    Insight Data Science Blog
    Company · last shared 2022
    Simply Statisticssimplystatistics.org85 people

    The future of education is plain text

    Simply Statistics
    Publication · last shared 2026
    Google Research Blogresearch.google584 people

    Google Titans architecture, helping AI have long-term memory

    Google Research Blog
    Company · last shared 2026
    Uber Engineering Blogeng.uber.com525 people

    Why Uber Engineering Switched from Postgres to MySQL

    Uber Engineering Blog
    Company · last shared 2025
    Statistical Modeling, Causal Inference, and Social Sciencestatmodeling.stat.columbia.edu350 people

    Suspicious data pattern in recent Venezuelan election

    Statistical Modeling, Causal Inference, and Social Science
    Publication · last shared 2026
    Google AI Blogai.googleblog.com596 people

    Google Duplex: An AI System for Accomplishing Real World Tasks Over the Phone

    Google AI Blog
    Company · last shared 2026
    Stitch Fix Multithreadedmultithreaded.stitchfix.com87 people

    Engineers Shouldn’t Write ETL

    Stitch Fix Multithreaded
    Company · last shared 2025
    Sourcegraph Blogabout.sourcegraph.com156 people

    An ex-Googler’s guide to dev tools

    Sourcegraph Blog
    Company · last shared 2024