Member-only story

Data Engineers Who Don’t Do This 30-Minute Exercise Will Waste Hours of Development Time

Save time, sanity and keystrokes with this low-tech strategy.

Zach Quinn
Pipeline: Your Data Engineering Resource
6 min readOct 10, 2022

--

Tired of the Titanic dataset and want ideas to inspire a unique, marketable portfolio? Learn how with my free project guide.

Developer in the middle of an analog clock.
Developer in the middle of an analog clock. Photo by Kevin Ku on Unsplash.

I would describe my coding style as aggressive.

I slam keys when I type, I furiously click mice and, on occasion, I’ve been known to toss items from my desk.

It’s a good thing I work from home.

As a new engineer, I often got frustrated with my coding tasks and, at points, have even had trouble beginning projects.

Initially, I spent too much time on code and not enough on the reasoning, project requirements to satisfy and incremental problems to solve.

A Ridiculously Simple Way to Jump-Start Data Engineering Projects

I noticed a dramatic improvement in my ability to understand and execute my tasks when I did one ridiculously simple thing.

I created a written outline for my project.

I didn’t make it a technical requirements document, proof of concept or any other formality.

--

--

Pipeline: Your Data Engineering Resource
Pipeline: Your Data Engineering Resource

Published in Pipeline: Your Data Engineering Resource

Your one-stop-shop to learn data engineering fundamentals, absorb career advice and get inspired by creative data-driven projects — all with the goal of helping you gain the proficiency and confidence to land your first job.

Zach Quinn
Zach Quinn

Written by Zach Quinn

Journalist—>Sr. Data Engineer; new stories weekly.

Responses (5)