text stringlengths 0 2.35k |
|---|
[40.76 --> 45.86] but the issues are not going to be related to, oh, I made a programming mistake and there |
[45.86 --> 46.70] is a bug in my program. |
[46.78 --> 47.46] It's going to be exploited. |
[47.60 --> 50.38] It's going to be more related to design issues. |
[50.38 --> 55.96] What's up, friends? |
[56.06 --> 58.40] This episode is brought to you by Sourcegraph. |
[58.84 --> 64.32] With the release of Sourcegraph 4.0 and the Starship event just a few weeks behind us, |
[64.52 --> 70.12] it is super clear that Sourcegraph is becoming not just CodeSearch, but a full-on code intelligence |
[70.12 --> 70.72] platform. |
[71.12 --> 74.10] And I'm here with Joel Kortler, product manager of Code Insights for Sourcegraph. |
[74.58 --> 79.20] Joel, this move from CodeSearch to Code Intelligence is a really big deal. |
[79.20 --> 83.92] How would you explain this feature, Code Insights, if you're just talking to folks in the hallway |
[83.92 --> 85.56] track of your favorite conference? |
[86.18 --> 89.74] I would really start with technical because before I was a product manager, I used to be |
[89.74 --> 90.40] an engineer as well. |
[90.68 --> 94.42] And it's really cool and exciting just to be able to say, we're going to turn your code |
[94.42 --> 95.56] base into a database. |
[96.06 --> 100.12] And the structured language that you need to interact is just the ability to write a code |
[100.12 --> 101.80] search, you know, literal search. |
[101.94 --> 102.66] That's totally fine. |
[102.80 --> 106.08] Regular expression, you know, that'll give you a few more advanced options, even a structural |
[106.08 --> 106.44] search. |
[106.90 --> 111.46] But the number of long tail possibilities that unlocks, truly the journey of building |
[111.46 --> 115.56] this product was just saying, well, we've just unlocked, you know, an infinite number |
[115.56 --> 116.18] of possibilities. |
[116.62 --> 120.24] We got to figure out some immediate use cases so we can start to, you know, invest in this |
[120.24 --> 121.28] product, build it and sell it. |
[121.74 --> 125.52] But we're only getting started in terms of the number of uses that we're uncovering for |
[125.52 --> 125.70] it. |
[126.04 --> 130.04] The story I told you about discovering like version tracking turned out to be a really important |
[130.04 --> 133.62] use case that wasn't even on our roadmap six months prior to discovering that as we |
[133.62 --> 136.44] are already planning to launch this product until we talked to enough folks, realized |
[136.44 --> 139.84] this was a problem and then found, well, oh, that's like a simple regular expression |
[139.84 --> 143.34] capture group that you can just plug right in because we really built this system to |
[143.34 --> 145.08] not limit the power of what we built. |
[145.18 --> 148.06] We don't want to give you like three out of the box templates and you can only change |
[148.06 --> 149.18] like one character or something. |
[149.28 --> 152.18] It's truly like the templates are there to hold your hand and get you started. |
[152.30 --> 155.76] But if you can come up with anything you want to track in your code base, you can do |
[155.76 --> 156.46] that with Code Insights. |
[156.70 --> 157.36] I love it. |
[157.40 --> 157.86] Thank you, Joel. |
[157.86 --> 163.68] So right now there is a treasure trove of insights just waiting for you living inside |
[163.68 --> 164.30] your code base. |
[164.46 --> 167.32] Your code base is now a queryable database. |
[167.38 --> 168.34] Thanks to Sourcegraph. |
[168.86 --> 172.68] This opens up a world of possibilities for your code and the intelligence you can gain from |
[172.68 --> 172.92] it. |
[173.18 --> 178.54] A good next step is to go to about.sourcegraph.com slash code dash insights. |
[178.72 --> 180.02] The link will be in the show notes. |
[180.36 --> 182.86] See how the teams are using this awesome feature. |
[182.86 --> 187.94] Again, about.sourcegraph.com slash code dash insights. |
[188.30 --> 190.58] Again, this link is in the show notes. |
[205.74 --> 206.58] Let's do it. |
[207.28 --> 208.22] It's go time. |
[208.92 --> 210.36] Welcome to go time. |
[210.36 --> 213.58] Your source for diverse discussions from all around the Go community. |
[214.06 --> 216.70] Check out our back catalog at go time.fm. |
[217.02 --> 221.66] There you'll find the most popular episodes, our favorites, and a request form so you can |
[221.66 --> 223.90] let us know what you want to hear about on the pod. |
[224.26 --> 228.80] Special thanks to our partners at Fastly for shipping our shows super fast to wherever you |
[228.80 --> 229.04] listen. |
[229.30 --> 230.78] Check them out at fastly.com. |
[231.22 --> 232.86] And to our friends at fly.io. |
[233.22 --> 235.20] Host your app servers close to your users. |
[235.48 --> 236.32] No ops required. |
[236.64 --> 238.44] Learn more at fly.io. |
[238.44 --> 239.46] Okay, here we go. |
[240.36 --> 245.02] Hello, everyone who is joining us today on a Wednesday of the recording. |
[245.36 --> 249.18] We normally record on a Tuesday, but we have a very special guest, so we need to make a |
[249.18 --> 250.76] very special event about that. |
[251.38 --> 252.40] Ian is my co-host today. |
[252.48 --> 252.82] Hi, Ian. |
[253.14 --> 253.88] Hey, how you doing, Natalie? |
[254.22 --> 254.60] Good. |
[254.76 --> 257.80] I'm very excited to have Ivan today join us. |
[257.92 --> 258.16] Yeah. |
[258.32 --> 259.48] Ivan Kwiatkowski. |
[260.02 --> 262.10] Also known on Twitter as Justice Rage. |
[262.24 --> 266.10] You are a senior security researcher at Kasparsky. |
[266.10 --> 266.58] Yes. |
[266.76 --> 267.00] Hello. |
[267.14 --> 268.16] Very happy to be here. |
[268.54 --> 268.80] Indeed. |
[268.96 --> 274.78] So I work in the threat intelligence field and my daily work involves looking at malware |
[274.78 --> 276.36] and writing reports about it. |
[276.48 --> 281.24] Basically, the activity that I'm involved in is trying to figure out what the attackers |
[281.24 --> 285.04] are up to, what kind of tools they're using, methodologies, what types of victims they are |
[285.04 --> 287.10] after, and then we write stuff about it. |
[287.66 --> 291.76] And our customers read our reports, and then it allows them to figure out whether or not |
[291.76 --> 296.58] this group or this group is likely to attack them or not, depending on what type of information |
[296.58 --> 297.24] that they are after. |
[297.46 --> 302.36] And if so, how they may defend from those attacks by knowing more about the type of malware |
[302.36 --> 306.98] that they use, the type of attack vectors that they typically favor, and so on. |
[306.98 --> 313.98] So really, I spend my day in AIDA Pro most of the time, and sometimes as well, I do give |
[313.98 --> 319.18] out trainings for reverse engineering, either in universities or for our customers as well. |
[319.48 --> 324.82] And there is a very cool video that has two parts of you reverse engineering and malware |
[324.82 --> 328.12] written about a year ago that was written in Go, actually. |
[328.40 --> 328.74] Absolutely. |
[329.10 --> 330.88] And that was from the SolarWinds attack. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.