Extract. Transform. Read.A newsletter from Pipeline Hi past, present or future data professional! When I worked at Disney, the absolute worst thing you could say to a guest was “No.” It’s not so much that Disney guests would hear “yes” throughout their vacation; they just wouldn’t hear no. And that’s why, as a developer and individual contributor, it’s important to master what The Art of Being Indispensable At Work author Bruce Tulgan calls the “good no.” A bad no is a no said to something that could be feasibly accomplished. A good no is a no uttered in an effort to establish or reiterate priorities, like telling a stakeholder “No that dimension can’t be added to the pipeline during this sprint because it will require a new request to a separate API endpoint.” Good nos can also put requests into the context of larger team and organizational goals; for instance, saying “no” to production-izing an ML model that only generates 15 rows of data that isn’t relevant to larger initiatives is, without a doubt, a good no. It’s not just the sentiment of a denied request that can irritate a stakeholder or colleague. The word “no” just doesn’t sound good. It’s sharp. Definitive. If I can’t say “yes” to someone, I focus on fulfilling two needs that are almost as good:
Providing context: “I can’t put your query into production because I’m currently working on x initiative which impacts our team’s OKR for this quarter.” Offering an alternative: “Unfortunately, I don’t have the bandwidth to take on a backfill of your requested scope. Instead, I can backfill the data to the prior quarter so you can at least see data within the last 90 days, which is what your dashboard seems to focus on.” Even if you’re not working in a data role currently, this lesson can be applied to the bane of most students’ existence: Group projects. Putting your efforts into context can help avoid scope creep and make sure you don’t end up with a disproportionate amount of work. And so you don’t end up with too much work, here are this week’s links as plain text.
Questions? zach@pipelinetode.com Thanks for ingesting, -Zach Quinn |
Top data engineering writer on Medium & Senior Data Engineer in media; I use my skills as a former journalist to demystify data science/programming concepts so beginners to professionals can target, land and excel in data-driven roles.
Extract. Transform. Read. A newsletter from Pipeline Hi past, present or future data professional! If you haven’t heard "Happy New Year" enough in the past week… let me be, hopefully, the last to say it as we embrace all 2025 has to offer. Beginning a new year comes with the inevitable conception (and ultimately ignorance) of a new year’s resolution. Instead of focusing on one abstract goal to improve, I’d like to suggest, instead, that you form lasting habits, especially when it comes to...
Extract. Transform. Read. A newsletter from Pipeline Hi past, present or future data professional! In 2024 I published roughly 75 stories, mostly about data engineering or technology; understandably, with the pace of life and media, you most likely missed something I hope you’ll find valuable and actionable. Keeping with one of my core beliefs, that data-driven tools should result in both professional enrichment and reduce personal problems, my methodology for picking stories out of that...
Extract. Transform. Read. A newsletter from Pipeline Hi past, present or future data professional! If you’ve ever seen the legendary American sitcom Seinfeld, you might be familiar with the fictional holiday the characters create, festivus, “A festival for the rest of us.” As a rejection of conventional winter holidays like Christmas/Haunnukah, a core part of festivus is the “airing of grievances.” While I have yet to attempt this in real-life, I’ve spent the past two years airing my...