Join 📚 Kevin's Highlights

A batch of the best highlights from what Kevin's read, .

![](https://userimg-assets.customeriomail.com/images/client-env-99697/1673856105019_Screenshot%202023-01-16%20at%201.31.12%20PM_01GPWSJF2XFFR85V6GX7MMS6AR.png)

The Meditations Newsletter #015

Alex from Sunsama

This statement governs my principles regarding my activities as a content creator. I’ve made this information public for transparency, consistency, and fairness in my dealings with viewers, readers, employers, and sponsors alike. It is a list of my expectations from others, but it also a list of what others can expect from me.

My Ethics Statement

nicolevanderhoeven.com

When we unpack the common threads of how various people define data engineering, an obvious pattern emerges: a **data engineer** *gets data, stores it, and prepares it for consumption* by **data scientists**, **analysts**, and others. We define data engineering and data engineer as follows: **Data engineering** is the *development*, *implementation*, and *maintenance* of **systems** and **processes** that take in raw data and produce high-quality, consistent information that supports downstream use cases, such as analysis and machine learning. **Data engineering** is the intersection of *security*, *data management*, *DataOps*, *data architecture*, *orchestration*, and *software engineering*. A **data engineer** *manages the data engineering lifecycle*, beginning with getting data from source systems and ending with serving data for use cases, such as analysis or machine learning.

Fundamentals of Data Engineering

Reis, Joe;Housley, Matt;

...catch up on these, and many more highlights