WEBVTT

1
00:00:01.700 --> 00:00:08.400
Now, when using this chat here, no matter if it's the chat in the sidebar or the inline

2
00:00:08.400 --> 00:00:12.820
chat, you also have some other useful shortcuts available.

3
00:00:13.820 --> 00:00:18.580
For one, in the inline chat, you can also refer to specific files or code bases.

4
00:00:19.060 --> 00:00:23.780
This could be useful if you want to generate some code here in this file based on some

5
00:00:23.780 --> 00:00:25.020
code in some other file.

6
00:00:25.380 --> 00:00:27.460
You could then refer to that other file here.

7
00:00:29.720 --> 00:00:36.120
But besides these hashtag shortcuts here, you can also use the at symbol to get access

8
00:00:36.120 --> 00:00:37.620
to some other shortcuts.

9
00:00:38.600 --> 00:00:42.460
Most importantly here in the main chat sidebar.

10
00:00:44.140 --> 00:00:48.180
Maybe at the point of time you're watching this also here in the inline chat.

11
00:00:48.500 --> 00:00:50.380
Right now it's a bit more limited here for me.

12
00:00:50.800 --> 00:00:58.860
But in that main chat sidebar, you see, if I type an at symbol, I get some other participants

13
00:00:59.300 --> 00:01:06.460
as GitHub calls them, I can bring into the chat to add even more or very specific context

14
00:01:06.460 --> 00:01:07.300
to the chat.

15
00:01:08.900 --> 00:01:14.040
For example, I can add at VS Code to ask a question about VS Code.

16
00:01:14.300 --> 00:01:20.580
So maybe a question that's not related to my project at all, but maybe a question regarding

17
00:01:20.560 --> 00:01:31.580
some VS Code settings, like where can I tweak the styling of the code in my editor?

18
00:01:34.060 --> 00:01:39.740
I can ask this question and hopefully I'll get back some helpful information regarding

19
00:01:39.740 --> 00:01:44.020
where in VS Code I can tweak that thing.

20
00:01:45.680 --> 00:01:50.280
And indeed, here it gives me some information regarding which settings I could change and

21
00:01:50.280 --> 00:01:55.200
it even gives me a button, you will sometimes get that here in that sidebar chat, which

22
00:01:55.200 --> 00:01:58.420
you can click to be taken to that place in the settings.

23
00:01:59.600 --> 00:02:01.220
So that's also very useful.

24
00:02:01.720 --> 00:02:07.100
And it's not just VS Code, you can also ask questions about the terminal, we'll get back

25
00:02:07.100 --> 00:02:07.660
to that soon.

26
00:02:08.699 --> 00:02:13.400
About the entire workspace, so again, your entire project here with all its code, all

27
00:02:13.400 --> 00:02:15.400
its configuration files and so on.

28
00:02:16.840 --> 00:02:22.040
About GitHub, if you're pushing your code to GitHub or if you're working with GitHub

29
00:02:22.040 --> 00:02:22.420
here.

30
00:02:23.300 --> 00:02:24.860
So that's also very useful.

31
00:02:25.320 --> 00:02:30.160
By the way, it's also at GitHub, at least at the point of time where I'm recording this,

32
00:02:30.460 --> 00:02:35.900
which you would have to select if you would want to incorporate web search into the response

33
00:02:35.900 --> 00:02:36.680
that's generated.

34
00:02:37.959 --> 00:02:44.060
So it's not obvious, but if you use GitHub, you will actually also get the AI behind this

35
00:02:44.000 --> 00:02:50.100
chat to search the web and incorporate the web search results into its response.

36
00:02:51.520 --> 00:02:58.620
So we can try this here, for example, with at GitHub to ask regarding does this code

37
00:02:58.620 --> 00:03:07.740
in this file follow all the common Python coding best practices, especially regarding

38
00:03:08.220 --> 00:03:09.500
code style.

39
00:03:11.620 --> 00:03:13.240
And it does not, by the way.

40
00:03:13.940 --> 00:03:19.180
And I can also bring in that file again to be really clear about which file I'm referring.

41
00:03:20.220 --> 00:03:22.520
So now here I got two pieces of context.

42
00:03:22.840 --> 00:03:26.760
I got GitHub to also take into account web search if needed.

43
00:03:27.180 --> 00:03:28.680
And I got this file.

44
00:03:29.360 --> 00:03:32.860
And now these references are being used.

45
00:03:34.500 --> 00:03:39.780
So here, actually, I, at least at the point of time where I'm recording this, would have

46
00:03:39.780 --> 00:03:43.160
to push this code to GitHub before being able to use at GitHub.

47
00:03:44.560 --> 00:03:49.600
So therefore, I'll actually try again in a new chat, but this time without at GitHub.

48
00:03:50.480 --> 00:03:54.880
So without the web search, but maybe it can still help me.

49
00:03:55.000 --> 00:04:00.620
Because the main point really is that you can bring different pieces of context into

50
00:04:01.420 --> 00:04:04.660
the chat to get the best possible reply.

51
00:04:05.820 --> 00:04:12.320
And now here I'm getting some suggestions regarding how I could tweak the code to make

52
00:04:12.320 --> 00:04:19.000
it a bit better and to be more in line with common best practices if I wanted to apply

53
00:04:19.000 --> 00:04:19.300
them.

54
00:04:20.380 --> 00:04:25.840
But the main takeaway is that with the hash symbol and the at symbol, you can bring different

55
00:04:25.880 --> 00:04:30.840
pieces of context and participants into the chat to get better results.