[ETR #73] Your Data Project's Catch-22


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

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! Next time you think you’ve tried everything in your job search, remember: I once worked with a guy who got hired at a national broadcast network on the strength of his parody rap. The intern, Jake, didn’t have a network or elite contacts, but he wanted an internship at The Tonight Show, a competitive role with over 10,000 applicants per semester. So, he recreated a shot-for-shot parody of a song previously performed on the show, rewritten with lyrics specifically...

Hi fellow data professional! For the past month I’ve been working on my most ambitious personal project: Purchasing and renovating a house. The first major upgrade? Replacing 70+-year-old windows. And while there’s probably a tech work comparison to gutting a legacy system to build anew, what I want to focus on is the deal I brokered and how you can use similar leverage in your interviews. Because I got $1200 off a house’s worth of windows as a result of market research, due diligence and a...

Hi fellow data professional! Big news from my home base of Orlando: Disney hired a new CEO with a pay package of nearly $40 million. If you read beyond the headline you’ll see that his base salary is “only” 2.5 million with the possibility of up to a 250% target incentive and some $26-ish million in stock options. This is why you, the job seeker, need to think beyond base salary and look at TC. Total compensation. Thanks to labor transparency laws passed in hiring hubs like New York and...