text stringlengths 0 2.35k |
|---|
[87.14 --> 88.44] especially, you know, engineering organizations |
[88.44 --> 89.50] that are pretty established, |
[89.94 --> 91.40] they have older versions of things |
[91.40 --> 93.32] or even older versions of, like, SaaS tools |
[93.32 --> 94.08] they don't use anymore |
[94.08 --> 95.58] that they haven't fully removed |
[95.58 --> 96.96] because they're, like, not sure if it's still in use |
[96.96 --> 98.46] or they, you know, lost focus on that. |
[98.76 --> 100.58] And they're spinning up old virtual machines |
[100.58 --> 101.58] that they're still paying for. |
[101.68 --> 103.26] They're using, you know, old SaaS subscriptions |
[103.26 --> 104.08] they're afraid to cancel |
[104.08 --> 105.70] because they're not sure if anyone's actually using it. |
[105.80 --> 107.16] And so getting off of those versions |
[107.16 --> 108.78] not just, like, saves you the headaches |
[108.78 --> 109.94] and the risks and the vulnerabilities |
[109.94 --> 111.22] of being on old versions, |
[111.22 --> 113.36] but also literally the money of, you know, |
[113.42 --> 115.06] older systems running more slowly |
[115.06 --> 115.90] or the build times |
[115.90 --> 117.36] or, you know, virtual machines |
[117.36 --> 119.08] and SaaS tools that you're no longer using. |
[119.40 --> 120.56] Before you had this ability, |
[120.66 --> 121.28] we talked to teams |
[121.28 --> 122.96] there were basically three ways you could do this. |
[123.24 --> 124.50] You could slack a million people |
[124.50 --> 126.68] and ask for just, like, an update point in time. |
[126.94 --> 128.46] You could have sort of one human |
[128.46 --> 129.12] and one spreadsheet |
[129.12 --> 130.68] where, like, it's somebody's job |
[130.68 --> 132.02] every Friday or every two weeks |
[132.02 --> 133.64] to just, like, search all the code |
[133.64 --> 134.56] and find all the versions |
[134.56 --> 135.94] and write it down in a Google sheet. |
[136.20 --> 137.66] Or there were a couple of companies |
[137.66 --> 139.58] I came across with in-house systems |
[139.58 --> 140.48] that were sort of complicated. |
[140.68 --> 142.44] You had to know, you know, maybe Kotlin, |
[142.62 --> 143.60] but you didn't know Kotlin. |
[143.66 --> 144.54] But if you wanted to use this system, |
[144.58 --> 145.30] you had to learn Kotlin |
[145.30 --> 146.64] and you'd have to sort of build |
[146.64 --> 147.66] the whole world from scratch |
[147.66 --> 149.52] and run basically a tool like this |
[149.52 --> 150.88] with a pretty steep learning curve. |
[151.18 --> 152.52] And now for all three of those, |
[152.56 --> 153.26] you could replace it |
[153.26 --> 155.00] with a single line, Sourcegraph Search, |
[155.12 --> 156.08] which is basically just |
[156.08 --> 156.82] the name of the thing |
[156.82 --> 157.34] you're trying to track |
[157.34 --> 158.04] and the version string |
[158.04 --> 158.80] in the right format. |
[159.08 --> 160.00] And then we have templates |
[160.00 --> 160.76] that'll help you get started |
[160.76 --> 161.60] if you're not sure |
[161.60 --> 162.32] what that format is. |
[162.48 --> 163.54] And then it'll automatically track |
[163.54 --> 164.68] all the different versions for you, |
[164.86 --> 165.58] both historically. |
[165.76 --> 166.74] So even if you start using it today, |
[166.82 --> 167.90] you can see your historical patterns. |
[167.90 --> 169.38] And then, of course, going forward. |
[169.96 --> 170.64] Very cool. Thank you, Joel. |
[170.72 --> 172.12] So right now there is |
[172.12 --> 174.42] a treasure trove of insights |
[174.42 --> 175.18] just waiting for you. |
[175.42 --> 178.04] Living inside your code base right now, |
[178.32 --> 180.10] teams are tracking migrations, |
[180.44 --> 182.02] adoption, deprecations. |
[182.36 --> 183.50] They're detecting and tracking |
[183.50 --> 185.20] versions of languages and packages. |
[185.20 --> 187.18] They're removing or ensuring |
[187.18 --> 189.18] the removal of security vulnerabilities. |
[189.56 --> 191.14] They understand their code by team. |
[191.22 --> 192.90] They can track their code smells and health |
[192.90 --> 193.90] and they can visualize configurations |
[194.52 --> 196.60] and services and so much more |
[196.60 --> 197.50] with code insights. |
[197.90 --> 200.18] A good next step is to go to |
[200.18 --> 202.18] about.sourcegraph.com |
[202.18 --> 204.10] slash code dash insights. |
[204.38 --> 205.88] See how other teams are using |
[205.88 --> 206.90] this awesome feature. |
[207.22 --> 209.84] Again, about.sourcegraph.com |
[209.84 --> 211.98] slash code dash insights. |
[212.24 --> 213.98] This link is in the show notes. |
[213.98 --> 230.04] Let's do it. |
[230.26 --> 231.70] It's go time. |
[232.26 --> 233.94] Welcome to go time, |
[234.10 --> 235.78] your source for diverse discussions |
[235.78 --> 237.26] from around the go community. |
[237.26 --> 240.20] We record live on Tuesdays at 3 p.m. |
[240.20 --> 240.62] U.S. |
[240.68 --> 241.08] Eastern. |
[241.46 --> 243.36] Subscribe at youtube.com |
[243.36 --> 245.24] slash changelog to be notified |
[245.24 --> 247.14] so you can be part of the action. |
[247.48 --> 249.30] And don't forget to follow the show on Twitter. |
[249.46 --> 250.72] We're at go time FM. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.