Reaching 20k+ readers on Medium and nearly 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.
[ETR #18] What Makes Data Engineers Say "No"
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 |
Extract. Transform. Read.
Reaching 20k+ readers on Medium and nearly 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.
Extract. Transform. Read. A newsletter from Pipeline Hi past, present or future data professional! While many tech-oriented companies have (in one way or another) reneged on remote working arrangements, my employer made an extreme gesture to demonstrate its commitment to the ongoing office-less lifestyle: It removed an entire floor of our two-floor New Jersey office space. Other companies, like Spotify, have unveiled slogans like “Our employees aren’t children. Spotify will continue working...
Extract. Transform. Read. A newsletter from Pipeline Hi past, present or future data professional! The only thing worse than summer temperatures (if you’re in the western hemisphere, that is) is a summer job search. Conventionally, summer isn’t the best time to apply for work; you could probably tell this if you’re currently working and find yourself accepting an overwhelming amount of OOO cal invites. If you are braving the heat of the job market, I want to share a more targeted and...
Extract. Transform. Read. A newsletter from Pipeline Hi past, present or future data professional! Well, it finally happened; AI has replaced a build I created and I’ve been made redundant. Thankfully, the person that created the AI integration was also me. And I did this on personal time so this isn’t an apocalyptic scenario. I’ve previously written about a handful of tools I created to optimize the “busy work” of blogging. One of the ways is by adding links to past relevant articles and...