How to use ChatGPT to write code — Blake Messer // Cratejoy
- Part 1 How to use ChatGPT to write code — Blake Messer // Cratejoy
- Part 2Struggles in buy-vs-build land — Blake Messer // Cratejoy
Show Notes
-
01:33Why Blake built a Slack integration for ChatGPTFrustrated by having to keep taking screenshots of conversations with ChatGPT to show them to the engineers on his team and product managers, Blake created a way so everyone can interact with it within Slack and experience its power.
-
03:05How are people using ChatGPT?People have turned it into a pocket assistant, a writer, and a coder for HTML and CSS. The sooner people realize it isnt going away and learn to use it, the more elaborate their work will be.
-
06:20Navigating the roadblocks with C suite when introducing ChatGPTJust ask them to spend 20 minutes with it and then tell you it won't change everything pretty soon.
-
10:20How to get the best out of the toolPrecise prompts, sniff tests, use cases, and follow-up questions. It works best when you can distinguish between a useful answer and when you need to call it out on its error.
-
12:39Strategies to use ChatGPT to learn in public without looking like you dont know what youre doing in front of your teammatesTest your prompts in private but share some of your wins, some of the prompts, or some of the learnings from the model in your public Slack channel.
-
14:02What is Copilot, how does it work, and why is it a game changer?Its a code predictor that predicts the code youre about to write and then just writes it for you so you can operate at a more executive level while you're doing the work that you're doing.
Quotes
-
"I see people using ChatGPT for almost everything. I've seen people use it to write job descriptions, write emails, and I've seen it used to write code, CSS, and HTML, which is quite good at. It allows the people using it to have their pocket assistant, and the output from that pocket assistant ends up being more often than not right the first time." - Blake Messer
-
"My feeling is that ChatGPT is going to be a part of daily life for everyone in our field if it's for whom it's not already in short order. And so, I thought for my engineering team, the earlier I could drive adoption and expertise with how to use and what the pitfalls are with this tool, the more elaborate the work we are doing." - Blake Messer
-
"Adopting ChatGPT depends on team culture and how much your IT org will trust you to install a third-party application. Yes, there are privacy concerns, security concerns, and copyright concerns. People are asking, is this going to be useful? Can I trust my junior engineers to use this responsibly? Are they going to commit code that they don't understand? It all comes down to the engineering culture problem that will block their adoption." - Blake Messer
-
"Most senior engineers are already taking large pieces of code and chucking them into small pieces and then trying to understand those smaller pieces and have those abstractions make sense. As long as that's your workflow, it's an optimal tool." - Blake Messer
-
"People are jamming the bot a lot. And it's not because they don't want to look like they don't know what they're doing in front of their teammates. In my case, they don't want to drown us in the tedium of trying to convince us not to use media queries while writing the CSS. They know they will try ten prompts before one works. And they don't want to flood us with all the garbage. But when they finally get it to work, if they don't post it someplace public, then there's a loss there." - Blake Messer
-
"GitHub created Copilot in collaboration with Microsoft and open AI. And essentially, what it's trying to do is sit in your code editor. It tries to predict what code you're going to write next based on what file you're looking at, what is the other contents of that file, what other files are in the same repository or directory or whatever." - Blake Messer
- Part 1 How to use ChatGPT to write code — Blake Messer // Cratejoy
- Part 2Struggles in buy-vs-build land — Blake Messer // Cratejoy
Up Next:
-
Part 1How to use ChatGPT to write code — Blake Messer // Cratejoy
Are you one of those CTOs scared of adopting ChatGPT because of privacy, security, and copyright concerns? Your team members are already using it. The earlier you drive adoption and expertise with how to use and what the pitfalls are, the more elaborate your work will be. Find out more in this episode of the CTO podcast as Blake Messer, VP of Engineering at Cratejoy, discusses how to use ChatGPT to write code and more.
-
Part 2Struggles in buy-vs-build land — Blake Messer // Cratejoy
The buy vs. build question is a recurring one engineering leaders have to deal with. You are often worried that by taking an off-the-shelf solution, they will only have 80% of the functionality you want. Do you still go ahead to buy or build internally? How does doing either help you compete in the market? Find out more in this episode of the CTO podcast as Blake Messer, VP of Engineering at Cratejoy, discusses answering the buy vs. build question and how to avoid struggles down the road.
Play Podcast
