Join 📚 Kevin's Highlights
A batch of the best highlights from what Kevin's read, .
Starting Hand Standards
A reasonable set of opening requirements at most tables would be as follows:
**Early position**: Ten high or better badugis; Smooth 7 high tris or better
**Hijack**: Jack high or better badugis, Smooth 8 high tris or better
**Cut-off**: All badugis, 8 high tris or better, A2 and A3
**Button**: All badugis, 9 high tris or better, A2, A3, 23, A4
Badugi Rules and Basic Strategy
countingouts.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;
Here’s what the entity resolution query looks like:
I’m joining the table with itself on state + zipcode
to reduce the search space and
using string similarity thresholds
for filtering potential duplicates.
In entity resolution methodology this is known as “blocking.”
Fundamental Data Engineering Concepts - Part 2
Ergest Xheblati
...catch up on these, and many more highlights
Readwise