You Can Build A Data Pipeline In <90 Min.


Extract. Transform. Read.

A newsletter from Pipeline: Your Data Engineering Resource

Hi past, present and future data professional!

Since today is a U.S. holiday, I won’t take much of your time; the good news is that, when conducted efficiently, building a data pipeline doesn’t have to take days, weeks or months.

In fact, you can build a data pipeline in as little as 90 minutes. Accelerating pipeline development depends on a thorough read of the documentation, a familiarity with your scripting language’s requests library and patience dealing with pesky data structures.

If you think, during this time, engineers are heads-down, you may have watched The Social Network too many times; personally, I like a little external stimuli while coding, which is how I ended up building a full dashboard during another American pastime–a baseball game. My secret? Distilling data with clean views, which I recommend over bloated source tables for both aesthetic and performance reasons.

Even optimizations like views have their limitations, leading to optimization ceilings. The best way to break through, aside from stubbornness, is a combination of incremental problem-solving and “big picture” data modeling to reassess resources and attack the problem completely.

Since I don’t want you to have to work any harder today, here are the embedded links as text:

If you’re celebrating America today, happy 4th!

Thanks for ingesting,

-Zach

Extract. Transform. Read.

Reaching 20k+ readers on Medium and over 3k learners by email, I draw on my 4 years of experience as a Senior Data Engineer to demystify data science, cloud and programming concepts while sharing job hunt strategies so you can land and excel in data-driven roles. Subscribe for 500 words of actionable advice every Thursday.

Read more from Extract. Transform. Read.

Hi fellow data professional! In undergrad, in pursuit of a coveted TV internship, I once cold messaged an alum of my school using an email I found on his acting reel. When we finally got on the phone it wasn’t the warm handshake connection I was seeking; he spent time grilling me on my intentions and skills. After I hung up I thought “what a jerk.” In my yet-to-be-developed mind I thought as long as I went to the effort of getting someone on the phone they’d reward that initiative with a job,...

Hi fellow data professional! This week I’ve gotten back into something I haven’t even attempted since my college intern days: Meal prepping. Prep is a priority for me since I’m watching my son (and our pets) solo while my wife is away for work. And, I hate to say it but, I somewhat agree with Sam Altman’s controversial quote about not understanding how people parented before widespread AI adoption; when used properly, AI-generated “parental assets” like meal plans, budgets and workout...

Hi fellow data professional! I learned one of the most important personal branding lessons in the basement of Arizona State University. I was seated at my desk in the Post Office/Writing Center as my coworker, a fellow writing tutor, reviewed my resume. “The content is good, but I won’t remember this. There’s no branding.” She thought for a second. “You know what? Change the font color to navy. Your brand is now blue.” I laughed but she was serious and the interaction imprinted on me not the...