text stringlengths 0 2.46k |
|---|
[857.86 --> 860.54] I think it's a great win for kind of like human agency. |
[860.84 --> 863.70] Like we want to be programming the computer is not the other way around. |
[863.70 --> 864.02] Right. |
[864.08 --> 868.16] And I think a lot of the technology that has emerged over the past, you know, 10, 15 years |
[868.16 --> 872.78] has been kind of computers programming us as humans a little bit in terms of like all the |
[872.78 --> 873.66] stuff that we consume. |
[874.06 --> 877.88] And so, yeah, I'm super excited for textual based inputs. |
[877.88 --> 881.12] It's, I think chat is kind of like a subset of that. |
[881.48 --> 885.60] The way we think about Kodi evolving is really it's going to evolve in the direction of just |
[885.60 --> 887.12] like this rich REPL. |
[887.28 --> 892.94] So it's not, it's not necessarily going to be like, oh, it's a human-like thing that you |
[892.94 --> 894.34] talk with conversationally. |
[894.48 --> 897.10] It's more like if you want to do a search, you type something that looks like a search |
[897.10 --> 897.34] query. |
[897.48 --> 898.78] It knows that you want to do a search. |
[899.28 --> 900.32] Shows you search results. |
[900.32 --> 903.88] If you ask a high-level question, it knows you're asking a high-level question. |
[903.88 --> 907.24] It gives you an answer that integrates the context of your code base. |
[907.40 --> 912.46] If you want to ask a question about your production logs or maybe something about something someone |
[912.46 --> 917.88] said in chat or like an issue or a code review, you should pull context from those sources |
[917.88 --> 923.88] and integrate that and both synthesize an answer to your specific question, but also like refer |
[923.88 --> 927.96] you back to the primary sources so that you can go and like dig deeper and understand more |
[927.96 --> 929.08] fully how it got to its answer. |
[929.08 --> 931.64] So we think chat is just the starting point. |
[931.78 --> 935.12] It's really just like this rich REPL that's going to integrate like all sorts of context, |
[935.30 --> 940.52] like whatever, you know, piece of information is relevant to you creating software. |
[941.02 --> 943.88] This is kind of like the thing that focuses that and pulls it all in. |
[944.12 --> 948.46] It really seems like that, at least as an interface, you're seeing that as the future |
[948.46 --> 949.82] of what Sourcegraph is, isn't it? |
[949.86 --> 952.52] Or is there more to Sourcegraph than that in the future? |
[952.88 --> 957.18] So the way we think about it is like we spent the past 10 years building the world's most |
[957.18 --> 958.42] advanced code understanding tool. |
[958.42 --> 959.72] So we have the best code search. |
[959.84 --> 961.42] We have the best code graph. |
[961.58 --> 965.68] So the global reference graph across, you know, all the different languages in the world. |
[966.14 --> 972.34] We have a large scale code modification refactoring system and a system to track high level insights. |
[972.46 --> 976.06] So there's all these like backend capabilities that are really, really powerful. |
[976.74 --> 982.56] And what language models have done is given us a really, really nice beginner friendly interface |
[982.56 --> 983.86] to all that power. |
[984.10 --> 986.92] And I think you're going to see this across all kinds of software. |
[986.92 --> 991.22] It's like historically building power user tools has been difficult because the on-ramp |
[991.22 --> 997.16] to getting full, full, taking full advantage of those tools has been a little steep. |
[997.52 --> 998.04] Requires education. |
[998.22 --> 998.30] Yeah. |
[998.36 --> 998.52] Yeah. |
[998.62 --> 1002.72] And so like if you're worried about the on-ramp, maybe you end up constraining your product a |
[1002.72 --> 1006.78] little bit just to make it simpler, dumb it down for the beginning user. |
[1006.78 --> 1007.90] But you lose out on the power. |
[1007.90 --> 1012.64] I think that tradeoff is no longer going to be as severe now with language models. |
[1012.84 --> 1019.96] And so at Sourcegraph, we're basically thinking, rethinking the user interaction of the entire |
[1019.96 --> 1020.54] experience. |
[1020.74 --> 1024.64] Like the underlying capabilities and underlying tech is not changing. |
[1024.80 --> 1028.02] That's still, if anything, that's gotten more valuable now because you can feed it into |
[1028.02 --> 1029.84] the language model and instantly get value out of it. |
[1029.84 --> 1033.84] But the entire user interaction layer, I think, needs to be rethought. |
[1034.28 --> 1040.74] And Cody, as your AI editor assistant, is kind of like the first iteration of that thought |
[1040.74 --> 1041.14] process. |
[1041.44 --> 1043.86] How did you iterate to the interface you're at now? |
[1043.90 --> 1045.82] And is it a constant evolution? |
[1046.50 --> 1046.80] Yeah. |
[1046.90 --> 1049.74] I mean, it's pretty much like, hmm, I think that would be a good idea. |
[1049.80 --> 1051.64] Let me go hack it together and see how it plays. |
[1051.66 --> 1052.68] And you play around with it. |
[1052.74 --> 1054.32] And then you kind of experience it yourself. |
[1054.42 --> 1055.98] And you build conviction in your own mind. |
[1055.98 --> 1060.38] And then you maybe share it with one or two other teammates and see if they have the same |
[1060.38 --> 1060.92] wow moment. |
[1061.14 --> 1064.38] And if they do, that's usually a pretty good sign that you're onto something. |
[1064.84 --> 1068.98] And there might be more details to hammer out to make it more accessible to everyone. |
[1069.24 --> 1074.38] But if you can convince yourself and at least two or three other smart people out there that |
[1074.38 --> 1078.88] there's something worth investigating, I think that's typically a pretty good sign that you're |
[1078.88 --> 1079.34] onto something. |
[1079.50 --> 1080.80] How do you get access to Cody? |
[1080.84 --> 1084.16] Not so much get access, but how do you use it in the Sourcecraft world? |
[1084.16 --> 1085.60] Like, how does it appear? |
[1085.98 --> 1086.86] How do you conjure it? |
[1087.32 --> 1087.50] Yeah. |
[1087.56 --> 1088.80] So it's just an editor extension. |
[1089.16 --> 1091.08] You can download it from the VS Code marketplace. |
[1091.54 --> 1092.84] It's available now. |
[1093.02 --> 1094.12] And it's free to use. |
[1095.52 --> 1098.26] And we have other editors on the way. |
[1098.42 --> 1100.04] IntelliJ is a very high priority for us. |
[1100.08 --> 1100.84] Also NeoVim. |
[1101.04 --> 1102.68] And of course, my editor of choice, Emacs. |
[1103.34 --> 1103.70] Of course. |
[1106.60 --> 1110.08] And we're developing it completely in the open as well. |
[1110.08 --> 1113.26] So Cody itself is completely open source and Apache licensed. |
[1114.16 --> 1119.08] And to get access to it, to start using it, you just install the extension into your editor |
[1119.08 --> 1120.80] and start using it. |
[1120.86 --> 1122.04] It opens up in a sidebar. |
[1122.18 --> 1122.92] You can chat with it. |
[1122.98 --> 1124.58] We also do inline completions. |
[1124.90 --> 1127.26] So as you're typing, we can complete code. |
[1127.70 --> 1132.44] Again, taking advantage of the kind of like baked in knowledge of the language model plus |
[1132.44 --> 1135.00] the context of your specific code base. |
[1135.00 --> 1138.32] So generating like very high quality completions. |
[1139.38 --> 1145.38] And yeah, it's generally just as simple as installing the extension and then you're off |
[1145.38 --> 1145.82] to the races. |
[1146.18 --> 1147.44] Probably a Sourcegraph account first. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.