Copilot Best Practices (What Not To Do)

Рет қаралды 38,989

Күн бұрын

This video covers best practices of using copilot by flipping the script and covering WHAT NOT TO DO.
00:00 - Intro
00:25 - Don't let copilot fly the plane
01:18 - Don't misuse copilot tools
03:50 - Don't recreate existing prompts
05:50 - Don't forget about context
06:30 - Don't ignore feedback features
08:00 - Outro
#vscode #githubcopilot #ai #bestpractices

Пікірлер: 45

@aar021 3 ай бұрын

Love it. Thank you for the video. Love your delivery style. Also love Copilot, it is a smart time saver.

@tlskillman 3 ай бұрын

Very helpful. I had no idea some of these features existed. Thanks.

@kate-pt2ny 3 ай бұрын

This video is very meaningful. I learned a lot. Thank you for sharing.

@ae-gc7ck 3 ай бұрын

This was helpful for me. Thank you

@alexandergarzon8052 2 ай бұрын

I would love to have an /improve command. Essentially, I envision writing my own code first and then seeking feedback from Copilot for suggestions on better approaches, improved syntax, and more.

@Ayan-sn2vb 4 күн бұрын

Great video.

@guilhermemm-dev Ай бұрын

what vscode theme is used in this video please? I liked it

@stevenzhang8620 3 ай бұрын

My takeaway from the video: use inline chat(command + i), use / command.

@tekskilldev8310 3 ай бұрын

@workshop looks all the files in the folder right? Even if you are working in js file workshop will keep html and css files in context as well right? Please explain. The suggestions via @workshop are thus wholistic and more relevant. Is my understanding correct?

@tekskilldev8310 3 ай бұрын

@@squishy-tomato thank you for quick feedback. I have been using copilot for just over 3 months and it has greatly improved by ability in javascript sphere. I am glad I got this clarified. thanks

@claus4tw 3 ай бұрын

I have set my vscode to only use a single tab at all times. Does that mean I cannot use workspace?

@AhmadElhedek Ай бұрын

So why comments for prompting is bad though? maybe not very effective I get it but I feel like the video didn't tell me why it is bad.

@DavidSandoval-dd5eq 23 күн бұрын

What's not to love. Microsoft knows how to make it easy for beginners.

@Mempler 3 ай бұрын

before ctrl+i was a thing, I constantly used the comment method.

@ovidiuc4 3 ай бұрын

For me, both inline chat and the chat panel have been useless. Suggestions are always much lower quality than ghost text, whether I highlight the context or not. And I have to do extra work to get them (i.e. explain what I want). When context is needed, I go to Chat GPT in the browser, where I can have control over the context and have a conversation with it.

@xxXm0RpH3usXxx 3 ай бұрын

opening two files in split view does not create a context for both, does it? i feel like it is only looking through the active document. Is there anything I am missing or is it not possible?

@alanhg 3 ай бұрын

use #filename can reference the file. At the moment I also think that the split screen doesn't have multiple files as references, so you can manually associate the files yourself

@zachfotis 3 ай бұрын

The chat icon has disappeared from my VS Code. Does anyone know why?

@nanakwame1122 3 ай бұрын

opening multiple files does nothing even witht he #file command because the context is extremely small and can barely cover half a file

@rootulp 3 ай бұрын

Why should comments not be used for prompts?

@krishnabisen2666 3 ай бұрын

Because that's not how we usually write the code, and it doesn't look clean

@ofoyeAbraham 3 ай бұрын

Actually its awesome but I will need some slightly explanation of something you said

@osman3404 3 ай бұрын

Does that also works on Visual studio 2022

@mfsbo 3 ай бұрын

Yes it works with copilot installed as extension

@josueando 3 ай бұрын

0:46 this was exactly the first prompt I wrote when I used copilot for the first time 🤣🤣🤣🤣🤣🤣

@stevenzhang8620 3 ай бұрын

hahahaha! Too greedy man.

@rs3800 3 ай бұрын

I disagree a bit with using comments in code for copilot: how to persist instructions for copilot in context otherwise? copilot has a very bad memory from chats.

@crackwitz 3 ай бұрын

The "what" is already encoded in the code. Comments are for "why".

@rs3800 3 ай бұрын

@@crackwitz it's not always already in the code if Copilot does not perform as expected. Then it's IMHO helpful to have the comments as supporting "context". I think it also make sense to omit the verbs: "table of customers" instead of "create table of...."

@mfsbo 3 ай бұрын

I am going to say chat is more useful if your dont want to add some more context. For me comments have been more relevant and helped in smaller functions and hinting was a lot better with keeping code readable without losing the comments.

@AndyPayne42 14 күн бұрын

Tried doing it this way and the code comments is much faster/more natural. using special commands and then clicking with the mouse (or finding the right number of tabs) is not convenient. Why not adapt to how users like to use it instead of adding gui components and pushing that and saying the other way is wrong when user experience says otherwise. AI should integrate naturally.

@yomajo 3 ай бұрын

1:50 pffft. mouse.

@yogitech33 3 ай бұрын

Comments aren't always efficient

@crackwitz 3 ай бұрын

Also, code just looks bad when all your prompts are strewn across it. It smells. Comments are for "why", not for "what". You should make a video on that coding practice. It looks like a lot of beginners use copilot and have terrible coding habits.

@ionutale1950 3 ай бұрын

4:03 fixing that missing =, yeahh totaly worth 38$ per month

@FindecanorNotGmail 3 ай бұрын

What not to do: Be complicit in mass copyright infringement

@merridius2006 3 ай бұрын

Amen

@justdavebz 3 ай бұрын

Why not use comments? It is because we cant help make co-pilot better by accepting correct answers and helping it learn? If that is the case, be transparent about it.

@theBidon 3 ай бұрын

Lol

@ItsComcastic 3 ай бұрын

In my experience copilot just isn't as good when prompting with comments. Instead of suggesting code it often suggests more comments. What's cool about in line chat is you can ask it to do something, it'll create a diff for you to review and before accepting you can change the prompt to get copilot to tweak the suggestion it gave you. It's a pretty nice way to iterate on code suggestions and not possible to do with comments. If a comment generates a bad reply you have to make your comment even more verbose and copilot loses the context of the generated code you're trying to get it to make changes to. Yes github probably benefits from you using inline chat and feedback. But you also benefit from a better experience.

@ChrisNoringchrisnoring 3 ай бұрын

If copilot suggest a comment for a comment then start typing the code, that will help. Copilot is trained on docs and code, help it by narrowing it down. In editor and chat are two great experiences if you know how to use it

@user-xx9oe3mj7s 3 ай бұрын

For me it's just inconvenient to use comments as you need to delete the comments again after copilot generated your answer (unless you want to leave them there and have a code full of copilot prompts)

@bass-tones 2 ай бұрын

Did you not see his example? He added a comment in the middle of an HTML block purely to instruct the AI. You would never in real life want this “comment” embedded in your HTML like this. In real life you’d add the comment to instruct the AI and then be forced to delete the comment afterwards. Keep in mind this is just an example. You shouldn’t create temporary code or comments for the mere purpose of asking the AI to generate something. That’s why the CTRL+I menu exists, that’s what problem it solves.