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 #17] Warning: Your Google Cloud Function Might Fail Next Week
Extract. Transform. Read.A newsletter from PipelineTechnically, this title is misleading. Not because your Google Cloud Function won’t fail. It may. And we’ll get to that. I promise. But because Google Cloud Functions are now called Google Cloud Run functions, selecting a name that reflects a fusion between Cloud Run and Cloud Functions, which were previously two distinct Google Cloud Platform products. While both products leverage serverless architecture to run code, Cloud Run was geared more toward those developing apps while Cloud Functions was more of a “quick and dirty” way to get simpler scripts, like ETL pipelines, into production. No matter what GCP calls this product, you’ll still be able to run scripts using a serverless configuration. As a bonus, you’ll now be able to use NVIDIA-based CPUs to boost runtime compute power. To leverage this though, you’ll need to upgrade to a gen 2 cloud function. With many new releases comes obsolescence. This case is no different. Effective October 14th, Google Cloud Functions (excuse me, Google Cloud Run functions), will no longer support Python 3.8, as Python itself is ending support for 3.8 in the same time frame.
If you need to go into more depth with updating runtimes or other aspects of deployment, you can learn to deploy a cloud function in 5 days. It’s 100% free and comes with access to a dedicated GitHub repository. Enroll here. I want to make sure I keep you sufficiently updated, so here are this week’s links:
Until next time—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.
Hi past, present or future data professional! If you’re in the U.S., Happy Thanksgiving! I’m prepping for my food coma, so I’ll make this week’s newsletter quick. Like millions of Americans, I’ll be watching NFL football (go Ravens!). The average NFL game is 3 hours. If you can skip just one of today’s games and carve out that time for professional development, here’s how I’d spend it. In the spirit of football, I’ll split the time designation into 4 quarters. Documentation pass - if you read...
Extract. Transform. Read. A newsletter from PipelineToDE Hi past, present or future data professional! In 2 weeks or so The Oxford English Dictionary will reveal its 2025 word of the year, a semi-democratic process that lends academic legitimacy to words like “rizz” (2023’s pick). If you’re currently employed or interact with white collar workers, you would think the word of the year is “headwinds.” Used in a sentence: “We’ve pivoted our AI strategy but still encountered headwinds that...
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...