Extract. Transform. Read.A newsletter from Pipeline Hi past, present or future data professional! I recently participated in a technical design meeting that was derailed by a single, fundamental question. “Why?” Despite the fact that I worked with the particular data source we were discussing for nearly two years, I fell into the common trap of going “on autopilot” and failing to question the initial need for the data. At this point, you would think asking “why” of years’ worth of work would be offensive. Instead of myself or other team members getting defensive, it led to a productive conversation about not just refining our approach to ingestion, but also inspired talk of how we can manage stakeholder expectations and softly encourage them to “do more with less.” Fortunately, you don’t need to derail a meeting to leverage what I call a productive why. Asking occasional, tactful “whys” can position you as a critical thinker and thought leader (or at least an enthusiastic thought contributor) within your org. When appropriate, consider asking…
I realize you may not be in a professional role; nonetheless, I’ve found a lot of value can result from occasionally asking “why” even when you’re simply writing code. For instance, I was a habitual user of Pandas’ .append() method. Unfortunately, to my disappointment, Pandas 2.0 deprecated .append() in the past year. I easily could have panicked and said “Iterating and appending key values to an empty data frame is how I’ve always converted JSON to a data frame. What am I going to do?” But being forced to adapt to the change made me think about what prompted that habit initially. To learn what that motivation was plus how a simple "why" nearly left me tongue-tied in an interview, read the latest on Pipeline. And so you don’t have to question where those hyperlinks go, here they are as plain text.
Questions? zach@pipelinetode.com 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! It’s baseball season in the U.S., a game defined by the "on-deck" line up. Before a player takes a big swing at the plate, they are already there, weighted bat in hand, timing the pitcher (who has to move a bit faster now thanks to the pitch clock), fully prepared for their moment. They don’t start looking for their helmet only after the umpire calls them up. In your early career perhaps you're considering "taking a big swing" by applying for that dream role at a...
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...