Extract. Transform. Read.A newsletter from PipelineToDE Hi past, present or future data professional! After choosing a dataset, one of the most significant decisions you must make when creating displayable work is: How am I going to build this thing? For some, you may try to “vibe code” along with an LLM doing the grunt technical work. If you choose this approach, be warned: Nearly half of all “vibe code” generated contains security vulnerabilities and that’s before you even consider its ability to run. Others may immediately jump into an IDE, confident in their existing skills like Python. These two examples illustrate a conflicting decision you must make from the outset: Are you optimizing for “showing off” strong, existing skills? Or do you want to signal to an employer you can learn and employ new skills on the fly? This is the data practitioner’s Catch-22. Do you opt for a sure bet, a familiar tech stack, or do you take a risk and showcase an emerging or “hot” technology that might not be among your core strengths? Perhaps the biggest determining factor for learning vs. showing off is your time constraint. How much time can you dedicate to your build? If you’re working slowly over a few months, it might make sense to try to implement a new approach. If a deadline like graduation is rapidly approaching, you might want to stick to tried and true methodologies. There’s absolutely no shame in creating Matplotlib visualizations instead of using a BI tool like Tableau. It might not be as “pretty” but if you nail the business fundamentals, your work could outshine the slickest dashboards. To remove the guesswork from that critical decision, when to learn and when to rely on existing skills, you need a professional execution framework. This framework is the foundation of my new ebook resource, and I'd like to offer you a free sample today. It gives you a clear, documented plan to take any project from ideation to deployment without wasting time on dead ends or pondering Catch-22 scenarios. Thanks for ingesting, -Zach Quinn |
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.
Hi fellow data professional and Happy New Year! In the second half of 2025, I made a radical choice: I (largely) stopped blogging. Over the past year, Medium (where I host my content) made a series of changes that de-prioritizes technical content, leading to the departure of several major publications, including Toward Data Science. Pair that platform disillusionment with a bit of burnout, and the result is a feeling that it’s time for a change. For 75+ weeks, I’ve preferred concise,...
Hi fellow data professional - Merry Christmas and Happy Holidays! Since an email is probably one of the least exciting things to open on Christmas morning, I'll keep this brief. As a thank you for subscribing and reading the newsletter this year, I'd like to offer a gift: My FREE guide to web scraping in Python. Centered around 3 "real world" projects, the guide highlights the importance of being able to retrieve, interpret and ingest unstructured data. Get your guide here. Have a restful...
Hi fellow data professional! Once thought to be a purely back office role, data engineering is undergoing a radical transformation and gaining a new responsibility: Front-end deployment. The folks already deploying applications in this capacity are known, incidentally, as forward deployed software engineers or forward deployed engineers (FDEs). Before you worry about needing to learn JavaScript or other web programming paradigms, know that I’m referring to the preparation, deployment and...