Talking the Future of Tech
In this episode, we do some live vibe coding– using AI to write code. We share tips and tricks on having the best vibe coding experience and avoiding some common pitfalls. You’ll get to hear what we do, how we discover what the steps are, just how easy it is to interact with the system, to set up a basic environment. We also start to explore the limitations of vibe coding. We encourage you to listen along and try on your own!
Transcript: otter.ai/u/CqKdtWZWYb3AdPtcb-…?utm_source=copy_url
What is technical debt, and how does it apply to large language models? We dive into a really interesting conversation that goes from technical debt into system and code maintenance, which is probably a much better way to think about the challenges we have in maintaining the infrastructure systems, code, data and data lakes that we have to deal with on an everyday basis.
How do we maintain, store, track and update the LLMs themselves? How do we know and manage which model is being used when we retire a model?
References:
www.linkedin.com/pulse/how-google…h-debt-abi-noda/
devops.com/are-llms-leading-de…o-a-tech-debt-trap/
Transcript: otter.ai/u/ngUClgtMmLLKXCFalD…?utm_source=copy_url
Image: www.pexels.com/photo/anonymous-w…y-gloves-3846440/
Cloud2030LLMsChatGPTTechnical DebtMaintenanceCoding
Rob’s Hot Take:
In the Cloud 2030 podcast episode on August 17th, Rob Hirschfeld discusses the distinction between technical debt and system maintenance costs, emphasizing the importance of understanding the ongoing effort needed to maintain and improve systems. He points out that overlooking the maintenance costs while building a system leads to technical debt. Hirschfeld raises the question of whether large language models and AI can change the equation of system maintenance, a topic yet to be explored fully in the podcast.
What can we expect generative AI to generate and is it going to produce good code? Today we talk about Gluecon and generative DevOps and the different concepts and capabilities around it. What impact is it going to have on developers? How do we control that?
Today’s discussion was in preparation for our session on June 13, where we’re going to group program GPT to see what type of DevOps coding skills we can prompt. We talked about the necessity of prompting in this session and covered some tips to help you think about how to be a better prompt engineer, a skill set that everybody’s going to need to have in the next months if not years.
Transcript: otter.ai/u/lsye_htH0-wksAOrqg…?utm_source=copy_url
Image: www.pexels.com/photo/man-welding…ow-frame-2965260/