text
stringlengths
0
2.35k
• The idea that one doesn't need to know everything about computer science to be effective and can simply "get on with it" and try things.
• A humorous exchange about putting down red wine and eating sandwiches, possibly related to a previous episode or discussion.
• A wrap-up of the podcast episode, including a call for listeners to share their spooky stories and a mention of upcoming episodes.
[0.00 --> 2.52] I've got one which is something that's kind of triggering.
[2.74 --> 5.40] I don't know if anyone else has got sort of triggers from being horrified.
[5.78 --> 7.46] One of my old bosses used to come to me,
[7.64 --> 9.68] and if he started the sentence with,
[10.10 --> 11.04] what do you know about?
[11.54 --> 13.62] Then I knew immediately it was downhill.
[14.10 --> 16.32] It's like, what do you know about Perl?
[16.48 --> 18.20] It's like, uh-oh, where's this going?
[18.66 --> 21.66] Or, what do you know about directory services and exchange?
[21.80 --> 23.98] It's like, um, that they exist?
[24.14 --> 24.92] Great, you'll do.
[25.34 --> 27.32] And off you'll be shipped to a client's site.
[30.00 --> 32.98] What's up, friends?
[33.06 --> 35.40] This episode is brought to you by Sourcegraph.
[35.86 --> 38.66] With the release of Sourcegraph 4.0
[38.66 --> 41.32] and the Starship event just a few weeks behind us,
[41.54 --> 44.62] it is super clear that Sourcegraph is becoming not just CodeSearch,
[44.62 --> 47.76] but a full-on code intelligence platform.
[48.18 --> 48.96] And I'm here with Joel Cortler,
[49.06 --> 51.30] Product Manager of Code Insights for Sourcegraph.
[51.58 --> 54.78] Joel, this move from CodeSearch to Code Intelligence
[54.78 --> 56.22] is a really big deal.
[56.48 --> 59.04] How would you explain this feature, Code Insights,
[59.04 --> 61.38] if you're just talking to folks in the hallway track
[61.38 --> 62.58] of your favorite conference?
[63.16 --> 64.98] I would really start with the technical
[64.98 --> 66.40] because before I was a product manager,
[66.50 --> 67.42] I used to be an engineer as well.
[67.70 --> 70.38] And it's really cool and exciting just to be able to say,
[70.54 --> 72.58] we're going to turn your code base into a database.
[73.04 --> 75.38] And the structured language that you need to interact
[75.38 --> 77.44] is just the ability to write a code search.
[77.74 --> 79.66] You know, literal search, that's totally fine.
[79.82 --> 80.86] Regular expression, you know,
[80.88 --> 82.30] that'll give you a few more advanced options,
[82.56 --> 83.46] even a structural search.
[83.46 --> 86.60] But the number of long-tail possibilities it unlocks,
[86.76 --> 89.02] truly the journey of building this product
[89.02 --> 90.98] was just saying, well, we've just unlocked,
[91.20 --> 93.20] you know, an infinite number of possibilities.
[93.64 --> 95.54] We got to figure out some immediate use cases
[95.54 --> 97.48] so we can start to, you know, invest in this product,
[97.60 --> 98.30] build it and sell it.
[98.74 --> 100.12] But we're only getting started
[100.12 --> 101.42] in terms of the number of uses
[101.42 --> 102.72] that we're uncovering for it.
[103.06 --> 104.88] The story I told you about discovering,
[104.96 --> 106.32] like, version tracking turned out
[106.32 --> 107.40] to be a really important use case
[107.40 --> 108.96] that wasn't even on our roadmap six months
[108.96 --> 110.44] prior to discovering that
[110.44 --> 111.76] as we were already planning to launch this product
[111.76 --> 112.92] until we talked to enough folks,
[113.22 --> 114.12] realized this was a problem,
[114.12 --> 115.26] and then found, well, oh,
[115.26 --> 117.38] that's like a simple regular expression capture group
[117.38 --> 118.46] that you can just plug right in
[118.46 --> 119.94] because we really built this system
[119.94 --> 122.10] to not limit the power of what we built.
[122.18 --> 123.08] We don't want to give you, like,
[123.20 --> 124.08] three out-of-the-box templates
[124.08 --> 125.26] and you can only change, like,
[125.28 --> 126.18] one character or something.
[126.30 --> 128.10] It's truly, like, the templates are there
[128.10 --> 129.20] to hold your hand and get you started,
[129.32 --> 131.18] but if you can come up with anything
[131.18 --> 132.40] you want to track in your code base,
[132.46 --> 133.48] you can do that with Code Insights.
[133.74 --> 134.86] I love it. Thank you, Joel.
[134.98 --> 138.52] So right now there is a treasure trove of insights
[138.52 --> 139.60] just waiting for you.
[139.88 --> 141.32] Living inside your code base,
[141.32 --> 144.34] your code base is now a querible database
[144.34 --> 145.36] thanks to Sourcegraph.
[145.78 --> 148.32] This opens up a world of possibilities for your code
[148.32 --> 149.92] and the intelligence you can gain from it.
[150.20 --> 152.04] A good next step is to go to
[152.04 --> 155.46] about.sourcegraph.com slash code dash insights.
[155.76 --> 157.02] The link will be in the show notes.
[157.38 --> 159.86] See how the teams are using this awesome feature.
[160.06 --> 164.94] Again, about.sourcegraph.com slash code dash insights.
[165.30 --> 167.58] Again, this link is in the show notes.
[167.58 --> 183.34] Let's do it.
[183.92 --> 185.00] It's go time.
[185.00 --> 186.92] Welcome to Ghost Time.
[187.64 --> 189.56] Your source for spooky conversations
[189.56 --> 191.24] from around the digital campfire.
[191.70 --> 194.62] Special thanks to our partners Fastly and Fly.io
[194.62 --> 197.42] for helping us bring you Go Time each and every week.
[197.80 --> 198.08] Okay.
[198.52 --> 199.88] Here we go.
[199.88 --> 212.14] Hello.
[212.14 --> 212.44] Hello.
[213.40 --> 216.10] And welcome to Ghost Time.
[216.48 --> 217.28] I'm Matt Ryer.
[217.66 --> 220.68] Today we're talking about tech horror stories.
[220.96 --> 222.76] I'm joined, as ever,