Documentation can be a make-or-break for the success of a data initiative, but it’s too often considered an optional nice-to-have. I’m a big believer that writing is thinking. Similarly, documenting is planning, executing, and validating. Previously, I’ve explored how we can create latent and lasting documentation of data products and how column names can be self documenting. Recently, I had the opportunity to expand on these ideas in a cross-post with Select Star. I argue that teams ca...
