text stringlengths 0 2.35k |
|---|
• Communication difficulties and nuances of verbal vs written communication |
• Importance of tone and context in communication |
• Challenges of expressing nuance through words alone |
• Use of emojis to convey emotion and intention |
• Role of emoji use in pull requests and code review norms |
• Potential benefits of incorporating voice notes or audio feedback into PRs |
• Discussing the difficulty of interpreting tone from written feedback |
• Using emojis to categorize comments as blocking or non-blocking |
• Pros and cons of using emojis versus GitHub's supported blocking feature |
• Importance of clear communication in code reviews to prevent misunderstandings |
• Benefits of streamlining communication through clear labeling and checklists |
• The importance of communicating clearly in code reviews |
• Fear of making mistakes in pull requests is common among engineers |
• Honeycomb's fast analysis tool is discussed as a solution to application issues |
• Teams who use Honeycomb avoid context switching and tool sprawl, improving effectiveness and business outcomes |
• Cloud native observability with Chronosphere helps teams manage complexity and increase confidence |
• The increasing amount of data being produced is causing issues in the observability space. |
• Many companies are focused on producing more metrics, traces, and logs to monitor complex environments. |
• This approach may be a mistake, as the increased volume of data does not necessarily lead to better outcomes. |
• Incident rates and mean time to detect (MTTD) and resolve (MTTR) are still rising despite the increase in data. |
• The added cost of managing this increased volume of data can make the problem harder to solve. |
• Importance of balancing critical and non-critical tasks |
• Difficulty of juggling multiple priorities in software development |
• Role of experience in making decisions on code changes |
• Skill of authoring a PR and asking for review |
• Art of making concise arguments for code changes |
• Need to improve skills in reviewing and walking reviewers through pull requests |
• The host, Jeff, shares his unpopular opinion that dogs are better pets than cats |
• Sarah's unpopular opinion is that aspiring software engineers should focus on writing and philosophy courses over computer science theory |
• Discussion ensues about why having strong communication and argumentation skills is essential for success in software engineering. |
• Discussing the value of a computer science degree versus dedicated software engineering |
• Importance of clear communication and concise argumentation in software engineering |
• Relationship between humanities classes and practical skills for software engineers |
• Debate on whether software engineers should have a broad range of knowledge or specialize in one area |
• Mention of past episodes discussing related topics, including the value of literature to software engineering |
• Discussion about the end of an episode and potential future episodes |
• Idea for a new plugin using GPT3 that can create empathetic responses |
• Collaboration on creating the plugin, with encouragement to make it happen |
• Farewell and closing remarks from the host, including promotion of membership program and sponsors |
[0.00 --> 7.00] If I'm blocking Angelica's pull request and I leave a bunch of comments and some of them are like, great job, this is really cool. |
[7.00 --> 10.22] And some of them are style and some of them are actually questions. |
[10.22 --> 13.82] And then some of them are actual blocking like requests for changes. |
[13.82 --> 24.48] It helps kind of narrow to those and like create more of a clear checklist in a way of what you're expecting to be changed before being asked to re-review the code. |
[24.48 --> 35.54] So I just think it's helpful, even if you are formally like blocking the pull request to communicate like what things you expect to be changed before you think that it could be merged. |
[35.92 --> 44.88] Gotcha. I don't know if I was just projecting my own fear, like seeing the email where it says this has been like changes have been requested and oh no, what did I do wrong? |
[45.22 --> 46.18] I need to do that. |
[46.80 --> 49.76] Don't worry, we all do stuff wrong in our pull requests all the time. |
[50.14 --> 51.46] That's part of being an engineer. |
[54.48 --> 60.84] This episode is brought to you by Sourcegraph with the launch of their Code Insights product. |
[60.84 --> 63.84] Teams can now track what really matters in their code base. |
[64.16 --> 70.46] Code Insights instantly transforms our code base into a queryable database to create visual dashboards in seconds. |
[70.94 --> 73.90] And I'm here with Joel Cortler, the product manager of Code Insights for Sourcegraph. |
[74.36 --> 84.06] Joel, the way teams can use Code Insights seems to pretty much be limitless, but a particular problem every engineering team has is tracking versions of languages or packages. |
[84.58 --> 87.26] How big of a deal is it actually to track versions for teams? |
[87.72 --> 89.46] Yeah, it's a big deal for a couple of reasons. |
[89.64 --> 91.46] The first is, of course, just compatibility. |
[91.46 --> 95.58] You don't want things to break when you're testing locally or to break on your CI systems or test systems. |
[96.06 --> 102.24] You need to have some sort of level of like version unification, minimum version support, and all of that needs to be compatible forward. |
[102.24 --> 116.38] But the other thing we learned was that for a lot of customers, especially, you know, engineering organizations that are pretty established, they have older versions of things or even older versions of like SaaS tools they don't use anymore that they haven't fully removed because they're like not s... |
[116.38 --> 119.50] And they're spinning up old virtual machines that they're still paying for. |
[119.62 --> 123.62] They're using, you know, old SaaS subscriptions they're afraid to cancel because they're not sure if anyone's actually using it. |
[123.74 --> 137.00] And so getting off of those versions not just like saves you the headaches and the risks and the vulnerabilities of being on old versions, but also literally the money of, you know, older systems running more slowly or the build times or, you know, virtual machines and SaaS tools that you're no lon... |
[137.00 --> 139.22] Before you had this ability, we talked to teams. |
[139.52 --> 140.90] There are basically three ways you could do this. |
[141.18 --> 144.62] You could slack a million people and ask for just like an update point in time. |
[144.88 --> 153.88] You could have sort of one human in one spreadsheet where like it's somebody's job every Friday or every two weeks to just like search all the code and find all the versions and write it down in a Google sheet. |
[154.12 --> 158.40] Or there were a couple of companies I came across with in-house systems that were sort of complicated. |
[158.60 --> 161.52] You had to know, you know, maybe Kotlin, but you didn't know Kotlin. |
[161.52 --> 168.80] But if you want to use this system, you had to learn Kotlin and you'd have to sort of build the whole world from scratch and run basically a tool like this with a pretty steep learning curve. |
[169.18 --> 176.72] And now for all three of those, you could replace it with a single line source graph search, which is basically just the name of the thing you're trying to track and the version string in the right format. |
[176.98 --> 180.24] And then we have templates that will help you get started if you're not sure what that format is. |
[180.36 --> 183.50] And then it'll automatically track all the different versions for you, both historically. |
[183.68 --> 185.84] So even if you start using it today, you can see your historical patterns. |
[185.96 --> 187.30] And then, of course, going forward. |
[187.90 --> 188.10] Very cool. |
[188.16 --> 188.56] Thank you, Joel. |
[188.56 --> 193.10] So right now there is a treasure trove of insights just waiting for you. |
[193.44 --> 199.96] Living inside your code base right now, teams are tracking migrations, adoption, deprecations. |
[200.28 --> 203.14] They're detecting and tracking versions of languages and packages. |
[203.14 --> 207.10] They're removing or ensuring the removal of security vulnerabilities. |
[207.48 --> 209.06] They understand their code by team. |
[209.14 --> 210.84] They can track their code smells and health. |
[210.84 --> 215.40] And they can visualize configurations and services and so much more with code insights. |
[215.40 --> 222.02] A good next step is to go to about.sourcegraph.com slash code dash insights. |
[222.30 --> 224.84] See how other teams are using this awesome feature. |
[225.08 --> 229.90] Again, about.sourcegraph.com slash code dash insights. |
[230.16 --> 231.92] This link is in the show notes. |
[231.92 --> 248.04] Let's do it. |
[248.80 --> 249.70] It's go time. |
[250.44 --> 255.52] Welcome to Go Time, your source for diverse discussions from all around the Go community. |
[256.04 --> 257.14] Subscribe to the pod. |
[257.14 --> 260.82] If you haven't yet, head to go time.fm for all the ways. |
[261.16 --> 263.54] And if you dig the show, please do tell your friends. |
[263.70 --> 264.48] That'd be pretty cool. |
[264.92 --> 269.40] Special thanks to our partners at Fastly for shipping all of our pods super fast to wherever |
[269.40 --> 270.00] you listen. |
[270.22 --> 271.94] Check them out at fastly.com. |
[272.04 --> 273.90] And to our friends at fly.io. |
[274.40 --> 276.50] Post your app servers close to your users. |
[276.72 --> 277.66] No offs required. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.