7 Tips To Achieve A 99% Cloud Deployment Success Rate


Extract. Transform. Read.

A newsletter from Pipeline: Your Data Engineering Resource

Hi past, present or future data professional!

Few aspects of data engineering are as shame-inducing as saying, after a failed deployment, “But it ran in my environment!”

In my first year as a data engineer I was that guy who made excuses like this and grew frustrated that I would complete a build and then struggle to push it over the finish line.

Here’s what helped me:

  • Learning the subtle but important difference between a dependency-related error and a code-oriented issue
  • Taking time to actually read documentation rather than skimming it
  • Understanding my chosen cloud platform (Google Cloud Platform)
  • Distinguishing the important bits of an error string to properly Google a mistake (both in local and cloud dev contexts)
  • Not running to my seniors for answers; StackOverflow, Medium, Reddit and platform-specific communities (like Google Community) are hive minds for solving specific errors
  • Logging status codes and outputs; you can’t fix what you can’t see
  • Creating “clean” dev environments that contain only the dependencies I need

I don’t track my deployment success rate (probably for the best given my initial failures), but I estimate that following the above advice has reduced my failure rate from 20% to between 1-5%.

None of these bullets, however, is a substitute for hands-on experience.

To step through your own deployment, enroll in my free 5-day Deploy Your First Cloud Function course.

Enroll here: https://pipe_line.ck.page/33a3ad0f36

As always, please send me any questions: zach@pipelinetode.com.

Thanks for ingesting,

-Zach

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! 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...