Keeping Up With Data — Week 16 Reading List


I was very happy to read about two Czech tech companies in the news this week. First, GoodData moved into the Data as a Service space with the announcement of its cloud-native analytics platform GoodData.CN. And then the news about ProductBoard raising $72 million in a series C arrived yesterday. Well done to both!

  • The Future of Data Lineage — Beyond a Diagram: The purpose of data lineage is not to have a nice diagram to look at. The purpose is to solve data engineering problems: What is the impact of this infrastructure change? Why is this dashboard broken? Is anyone using this table? How is this field calculated? Where are the PII data? Having lineage data can help answering these. That’s its true power. (Dan Mashiter @ Alvin)
  • Run Your Data Team Like A Product Team: Solving customers’ needs, not just answering their questions should be the focus of a data team. My product management knowledge is very limited, so I struggled a bit with the product management analogy. However, the practicalities about a data team focusing on their (internal) customers, striving for business impact rather than outputs and the importance of 2-way communication are deeply aligned with my experience. “Data teams should be 3–10% of the total headcount,” suggest the authors. But I’m less sure about that. (Locally Optimistic)
  • Don’t hire top talent; hire for weaknesses. I’ve been repeatedly told by recruiters that I’m writing the worse job descriptions. That’s because I don’t want to put an ideal candidate on the paper. First, I’m afraid that I might be wrong (not knowing what I don’t know). And second, I know I won’t find that ideal candidate. I always struggled to explain the ambiguous approach to recruiting that I’m taking — talking to interesting candidates (ignoring the ‘absolutely required’ items in the job ad) and testing how could they help the current team better. This article speaks my mind. (Benji Weber)

I’m finally back on the bike! I don’t even remember when I last had three weeks off. Well, I know what I’ll be doing this weekend!

Thanks for reading!

Please feel free to share your thoughts or reading tips in the comments.

Follow me on Medium, LinkedIn and Twitter.




Data scientist with corporate, consulting and start-up experience | avid cyclist | amateur pianist | Interim CDO at

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Introduction to Apache Airflow

Creating a TF-IDF in Python

Increase the Accuracy of Your CNN by Following These 5 Tips I Learned From the Kaggle Community

Reading excel file in pyspark (Databricks notebook)

Concepts You Have to Know for Data Science Interviews — Part II. Probability

CS371p Fall 2020: Barrett Schonefeld

An introduction to Probability Sampling Methods

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Adam Votava

Adam Votava

Data scientist with corporate, consulting and start-up experience | avid cyclist | amateur pianist | Interim CDO at

More from Medium

Keeping Up With Data #64

Key Learnings from the Next Generation of Analytics Practitioners

How asking a simple question bridged the gap between data science and data engineering