Sign up to save your podcasts
Or
Share Episode 2 - Avoiding Being Dumb
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Episode 2 - Avoiding Being Dumb
Send us a text
Avoiding Being Dumb
Episode 2: Show Notes
(Recorded November 4, 2021)
Welcome to episode two of the Cloud Out Loud Podcast! Today, Jon and Logan discuss a couple of blog posts; one from Corey Quinn, Chief Cloud Economist at The Duckbill Group and creator of the Last Week in AWS newsletter, which shares some very valuable insights into where cloud providers should be going in terms of introducing people to the cloud and training people about the cloud. The second is titled ‘Avoiding GCF Anti-Patterns Part 3: How to establish outbound connections correctly’, the third in a GCP Blog series on Google Cloud Function (GCF) anti-patterns, which tackles two common issues you might encounter in your monitoring and logging when making outbound HTTP requests with a GCF and how to solve them. We tease out the common thread between both these blog posts, which echoes the overall theme of this podcast: what are the cultural changes that need to occur to take advantage of the cloud and be more effective? The cloud can bring enormous benefit to your applications, to your programming workflow, but it does require mindset change!
Key Points From This Episode:
- Diving into ‘The Dumbest Dollars a Cloud Provider Can Make’ by Corey Quinn.
- How charging for training disincentivizes people from learning about cloud platforms.
- Why Jon believes that cloud providers should provide free training and pay trainers.
- Calling for training and certification to be loss leaders for cloud platforms.
- The benefits of introducing limited time offers without diminishing the value of training.
- Next: ‘Avoiding GCF Anti-Patterns Part 3: How to establish outbound connections correctly’.
- Two common problems that arise: increased error messages and expired execution times.
- How to solve for a lower error rate or lower latency, depending on your use case.
- Using Cloud Tasks or PubSub to offload your requests to another cloud service.
- Jon on the highly technical aspects of this post versus appealing to Cloud Function newbies.
- How to break up the monolithic approach that traditional developers tend to take.
- What Corey Quinn’s post and the GCP Blog post have in common: adopt not only new skills and knowledge, but new mindsets and culture too!
- The ability and responsibility developers have to leverage the power of managed services.
- Final thoughts: the cloud is powerful and, like all powerful things, treat it like a chainsaw!
- Updates from the world of Web 3.0, the Metaverse, and NFTs.
Tweetables:
“Charging people for training and not paying trainers would be chasing after pennies and ignoring dollars.” — @JonGal [0:03:27]
“The revenue that you may be gaining by charging for the [training] as a cloud provider is pretty small compared to the benefits that training can bring to driving future revenue for the cloud with organizations that are receiving the training.” — @LoganAct2 [0:04:57]
“Between increased error rates and increased latency, a common pattern for improving the performance of your Cloud Functions is to offload your requests to another cloud service.” — @LoganAct2 [0:09:33]
“The world is different in the cloud. Not only do you have to acquire new skills and knowledge, you have to acquire new [mindsets], possibly new [cultures] within your company.” — @JonGal [0:13:27]
Links Mentioned in Today’s Episode:
View all episodes
By Jon and Logan GallagherSend us a text
Avoiding Being Dumb
Episode 2: Show Notes
(Recorded November 4, 2021)
Welcome to episode two of the Cloud Out Loud Podcast! Today, Jon and Logan discuss a couple of blog posts; one from Corey Quinn, Chief Cloud Economist at The Duckbill Group and creator of the Last Week in AWS newsletter, which shares some very valuable insights into where cloud providers should be going in terms of introducing people to the cloud and training people about the cloud. The second is titled ‘Avoiding GCF Anti-Patterns Part 3: How to establish outbound connections correctly’, the third in a GCP Blog series on Google Cloud Function (GCF) anti-patterns, which tackles two common issues you might encounter in your monitoring and logging when making outbound HTTP requests with a GCF and how to solve them. We tease out the common thread between both these blog posts, which echoes the overall theme of this podcast: what are the cultural changes that need to occur to take advantage of the cloud and be more effective? The cloud can bring enormous benefit to your applications, to your programming workflow, but it does require mindset change!
Key Points From This Episode:
- Diving into ‘The Dumbest Dollars a Cloud Provider Can Make’ by Corey Quinn.
- How charging for training disincentivizes people from learning about cloud platforms.
- Why Jon believes that cloud providers should provide free training and pay trainers.
- Calling for training and certification to be loss leaders for cloud platforms.
- The benefits of introducing limited time offers without diminishing the value of training.
- Next: ‘Avoiding GCF Anti-Patterns Part 3: How to establish outbound connections correctly’.
- Two common problems that arise: increased error messages and expired execution times.
- How to solve for a lower error rate or lower latency, depending on your use case.
- Using Cloud Tasks or PubSub to offload your requests to another cloud service.
- Jon on the highly technical aspects of this post versus appealing to Cloud Function newbies.
- How to break up the monolithic approach that traditional developers tend to take.
- What Corey Quinn’s post and the GCP Blog post have in common: adopt not only new skills and knowledge, but new mindsets and culture too!
- The ability and responsibility developers have to leverage the power of managed services.
- Final thoughts: the cloud is powerful and, like all powerful things, treat it like a chainsaw!
- Updates from the world of Web 3.0, the Metaverse, and NFTs.
Tweetables:
“Charging people for training and not paying trainers would be chasing after pennies and ignoring dollars.” — @JonGal [0:03:27]
“The revenue that you may be gaining by charging for the [training] as a cloud provider is pretty small compared to the benefits that training can bring to driving future revenue for the cloud with organizations that are receiving the training.” — @LoganAct2 [0:04:57]
“Between increased error rates and increased latency, a common pattern for improving the performance of your Cloud Functions is to offload your requests to another cloud service.” — @LoganAct2 [0:09:33]
“The world is different in the cloud. Not only do you have to acquire new skills and knowledge, you have to acquire new [mindsets], possibly new [cultures] within your company.” — @JonGal [0:13:27]
Links Mentioned in Today’s Episode: