75. GitHub Copilot and ChatGPT: Game Changers for Developers?

04/06/23 • 50 min

In this special episode of AWS Bites, we drop all our opinions about the sudden growth of AI and how it is going to change the future as we know it! We begin by taking a trip down memory lane and discovering the types of AI tools that have been used in the past and how they have helped us. Then, we'll dive into ChatGPT, a language model that can assist us in writing and even creating code. We're especially excited to discuss how ChatGPT can be used to create slide decks or even write a book or a blog post. But wait, there's more! We'll also explore the utility of other AI tools such as Grammarly and OpenAI Whisper for improving our writing and transcribing spoken words into text. Moving forward, we'll examine how we tried to use AI to develop cloud applications on platforms like AWS. We'll also consider the impact of AI on the education system and how it can be used to modernize complex systems, or for learning, including programming languages that are new to developers. Now, we know there might be some concerns about using AI, such as whether it takes away the fun of software engineering or reduces creativity. But fear not! We'll address these concerns head-on and explore how AI can actually make us more productive and lead to exciting new discoveries. Finally, we'll discuss the exciting possibilities for AI and its potential to democratize access to the job market and society in general.

💰 SPONSORS 💰

AWS Bites is sponsored by ⁠⁠⁠fourTheorem⁠⁠⁠, an AWS Consulting Partner offering training, cloud migration, and modern application architecture.

In this episode, we mentioned the following resources:

Our episode about OpenAI Whisper for generating transcripts
David Boyne's AI-powered story generation tool (AWS Blog post)
The Fission project for simplifying monolith to microservices migrations

🎁 BONUS CONTENT A Limerick by ChatGPT On the Amazon Cloud far away, Where businesses went to play, The costs grew so vast, Their budgets were trashed, As their dollars all floated away!

You can listen to AWS Bites wherever you get your podcasts:

💰 SPONSORS 💰

AWS Bites is sponsored by ⁠⁠⁠fourTheorem⁠⁠⁠, an AWS Consulting Partner offering training, cloud migration, and modern application architecture.

In this episode, we mentioned the following resources:

Our episode about OpenAI Whisper for generating transcripts
David Boyne's AI-powered story generation tool (AWS Blog post)
The Fission project for simplifying monolith to microservices migrations

🎁 BONUS CONTENT A Limerick by ChatGPT On the Amazon Cloud far away, Where businesses went to play, The costs grew so vast, Their budgets were trashed, As their dollars all floated away!

You can listen to AWS Bites wherever you get your podcasts:

Previous Episode

74. Function URLs vs API Gateway

How can you use a Lambda to respond to an HTTP request? There are more ways than ever to do it. We have API Gateway REST APIs, Lambda support for Application Load Balancer, and now Function URLs. But which one should you use, and when? In this episode of AWS Bites podcast, we will give you a quick and simple guide to picking the best way to build APIs with Lambda. In this video, we're going to pitch Function URLs against API Gateway in a battle for the ages! Function URLs offer a simple and quick way to get a public URL to invoke a Lambda function, with fewer configuration options and cheaper pricing. They are suitable for private webhooks, simple backend functions, and machine learning inference backend. However, they lack authorization and DDoS protection, making them unsuitable for public webhooks. On the other hand, API Gateway offers more features and control, making it suitable for public APIs. API Gateway comes in two flavors: REST and HTTP with some subtle differences. Finally, we will also cover Application Load balancer and explore when and why it can be a convenient alternative to both Function URLs and API Gateway.

💰 SPONSORS 💰

AWS Bites is sponsored by ⁠⁠fourTheorem⁠⁠, an AWS Consulting Partner offering training, cloud migration, and modern application architecture.

In this episode, we mentioned the following resources:

Article by AJ Stuyvenberg reporting that Function URLs have a latency of 8.35ms
GitHub repository with all the material we used in our evaluation

You can listen to AWS Bites wherever you get your podcasts:

Next Episode

76. Unboxing AWS Copilot

In this episode, we're doing something different! Join us for a special screen-sharing edition of our podcast series, as we take a deep dive into AWS Copilot, a service designed to simplify container application deployment on AWS. During this video, we'll be sharing our screens as we walk through the AWS Copilot landing page and documentation, and demonstrate how to use the service to deploy a container application. We highly recommend watching the video version of this episode, as we'll be providing a lot of visual guidance and examples. Starting with the basics, we'll learn about the differences between copilot init and copilot app init, and how to prepare our environment using a custom domain. We'll then walk through the deployment process step-by-step, examining the generated configuration file, manifest.yml, and testing our deployed application. Next, we'll explore the networking resources created by AWS Copilot, including a VPC, subnets, and a load balancer, and review the automation capabilities of CodePipeline. We'll also discuss the options available for rolling out new changes, and demonstrate how to make changes and re-deploy through the pipeline. Throughout the video, we will share their thoughts and opinions on AWS Copilot, including a failed attempt with AppRunner and a review of the pipeline execution and timing.

💰 SPONSORS 💰

AWS Bites is sponsored by ⁠⁠⁠⁠fourTheorem⁠⁠⁠⁠, an AWS Consulting Partner offering training, cloud migration, and modern application architecture.

In this episode, we mentioned the following resources: