text stringlengths 0 2.35k |
|---|
[3084.64 --> 3084.84] Yeah. |
[3085.20 --> 3086.50] You know, if you don't like the song, don't worry. |
[3086.58 --> 3087.78] A new one will be on in one minute. |
[3088.06 --> 3088.22] Yeah. |
[3088.68 --> 3090.14] Are monkeys still around, Ron? |
[3090.14 --> 3092.56] So I find that comment offensive. |
[3093.00 --> 3093.22] Oh. |
[3093.42 --> 3095.18] They are known as primate professionals. |
[3096.30 --> 3097.88] You know, they do my taxes. |
[3098.62 --> 3104.52] Primate professional is one of my mechanics that maintains my prosthetic limbs. |
[3105.32 --> 3107.12] So I really resent that comment. |
[3107.38 --> 3108.76] You know, I think you should take that back. |
[3108.82 --> 3109.42] They're primates. |
[3109.60 --> 3110.12] Fair enough. |
[3110.56 --> 3110.80] Yes. |
[3110.92 --> 3111.74] Primate professionals. |
[3112.14 --> 3112.54] Fair play. |
[3113.70 --> 3114.48] Well, okay. |
[3114.68 --> 3115.24] I'll tell you what. |
[3116.14 --> 3119.92] I mean, obviously, Ron, we want to pick your brains about the future all night. |
[3120.06 --> 3122.02] But unfortunately, we've run out of time. |
[3122.42 --> 3126.02] Well, that's good because I'm actually, my lasers are almost out of the batteries. |
[3126.26 --> 3127.54] I'm going to have to start pedaling. |
[3127.92 --> 3131.36] I'm going to have to be pedaling for at least six or seven months to recharge now. |
[3131.36 --> 3137.54] So I wish all of you gophers in the past a tremendous lifetime. |
[3138.10 --> 3144.24] I hope that you're able to listen to some of this and at least know what not to do with |
[3144.24 --> 3145.78] go in the future. |
[3146.22 --> 3147.40] Thank you, dead program. |
[3147.56 --> 3148.32] Ron Evans. |
[3148.32 --> 3150.76] As always, absolute pleasure. |
[3151.46 --> 3155.28] And I've been Matt Raya and, of course, my co-host, Natalie Pistinovich. |
[3155.50 --> 3156.54] See you next time. |
[3160.88 --> 3163.14] Your next step is to subscribe. |
[3163.44 --> 3167.56] If you haven't already, head to gotime.fm for all the ways. |
[3168.02 --> 3172.00] And don't forget to follow us on Twitter so you can join in on the Unpop polls. |
[3172.36 --> 3173.54] We are at Gotime FM. |
[3174.02 --> 3176.36] Did you catch our changelog episode with the Graphite team? |
[3176.36 --> 3178.86] If not, here's a taste of what you're missing. |
[3179.50 --> 3183.68] It's interesting how many stories are like this where it's not your main product that |
[3183.68 --> 3184.68] becomes your main product. |
[3184.82 --> 3185.38] I think Slack. |
[3185.46 --> 3187.40] Wasn't Slack like the internal chat app? |
[3187.48 --> 3190.86] They were trying to build games and they're like, wow, this Slack thing is pretty cool |
[3190.86 --> 3194.42] that we built and started selling that and obviously became a big deal. |
[3194.60 --> 3198.74] Same thing with Flickr, which is like no one knows about Flickr anymore, right? |
[3198.82 --> 3203.54] But Flickr began as like some sort of Flash video game and then it turned into image sharing. |
[3203.88 --> 3205.54] It was the Instagram before Instagram. |
[3205.54 --> 3206.36] There you go. |
[3206.72 --> 3208.94] I think it's one of the purest ways to discover something, right? |
[3208.98 --> 3212.90] If you solve the need for yourself without some grand idea of making it into a company, |
[3213.04 --> 3214.82] but it ends up being that useful. |
[3214.96 --> 3215.82] People really want it. |
[3216.10 --> 3216.70] It's quite pure. |
[3217.30 --> 3217.48] Yeah. |
[3217.88 --> 3220.42] It kind of leans to the iteration process too, right? |
[3220.44 --> 3222.80] Like even innovation requires iteration. |
[3222.98 --> 3223.38] Totally. |
[3223.66 --> 3223.88] Right. |
[3223.88 --> 3227.86] You can't get to a problem or even a solution without having a problem. |
[3227.98 --> 3231.88] And sometimes you have to sort of go on a journey, which might be the wrong tool or the wrong |
[3231.88 --> 3232.24] thing. |
[3232.30 --> 3238.44] And you sort of discover from your exhaust of iteration that you got this down in the rough |
[3238.44 --> 3240.74] if you just put things to work. |
[3240.84 --> 3242.12] And there you go. |
[3242.12 --> 3246.30] Stacked diffs are super cool for fast moving code review. |
[3246.62 --> 3250.56] Listen to the whole thing at changelog.fm slash 491. |
[3250.88 --> 3255.96] Thanks again to Fastly for CDNing for us, to Breakmaster Cylinder for keeping our beat |
[3255.96 --> 3258.02] supply secure, and to you for listening. |
[3258.40 --> 3259.18] We appreciate you. |
[3259.18 --> 3265.56] Next up, Matt, Natalie, and myself have a deep discussion on development velocity, estimations, |
[3265.78 --> 3267.08] and all that agile jazz. |
[3267.60 --> 3271.16] That's something to look forward to next time on GoTime. |
• Introduction to Alexey Palazhchenko and his background with Go |
• Discussion of the cancellation of the Golang Show podcast due to members moving on to new projects or changing roles |
• The rebranding of FerretDB from MangoDB due to trademark concerns with MongoDB |
• Alexey's personal history with Go, including starting to use it at Microsoft and later working on a multiplayer game in Go |
• Discussion of AI-driven development, including the potential for AI tools like GitHub Copilot to suggest code changes and improvements |
• AI-driven development as an augmentation to the IDE |
• Concerns about Copilot using unlicensed code and potential licensing issues in open-source projects |
• Difficulty determining if auto-generated code is good or not, due to lack of labeling on GitHub repositories |
• Questions about safety practices and security when using AI-proposed code |
• Possibility of future precedents and judges being AI tools |
• Discussion on the limitations of AI in coding, including potential biases and lack of understanding |
• Analysis of Go as a language that is particularly well-suited for AI-driven development due to its simplicity and standardization |
• Examination of other languages, such as C++ and Java, that may be more challenging for AI to understand |
• Sharing of personal experiences with using Codex (the underlying engine of Copilot) on different programming languages |
• Discussion on the concept of "uncanny valley" in code generation and how it can make generated code look like a mix between human-written and machine-generated |
• Exploration of languages that may not work well with AI, such as Malbolge and LaTeX |
• Speculation on potential future applications of AI in developer tools, including documentation creation, pull request reviews, and more. |
• AI-augmented database, FerretDB |
• Copilot features: smart configuration values, proper Go configuration file generation, code review linter |
• Potential AI tools: variable name suggestion, project name suggestion, license selection, security vulnerability detection |
• Benefits of using Copilot: improved productivity, reduced compilation time, better documentation |
• Cautions and considerations: verifying generated code, representation issues with suggestions, potential for over-reliance on AI |
• Fuzz testing and AI-generated test data |
• Discussion of existing libraries and tools that can be used in conjunction with Copilot |
• Discussion of using GitHub Copilot for coding assistance |
• Limitations of Copilot in understanding complex codebases |
• Potential uses for AI in Go development, including generating domain-specific languages |
• Ideas for future improvements to Copilot and its applications |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.