Copilot Best Practices (What Not To Do)

preview_player
Показать описание
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
Рекомендации по теме
Комментарии
Автор

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

aar
Автор

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

tlskillman
Автор

"it is constantly learning from your.... feedback" :D

sandervandemoortel
Автор

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.

AhmadElhedek
Автор

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.

alexandergarzon
Автор

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.

rs
Автор

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

stevenzhang
Автор

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

kate-ptny
Автор

Why should comments not be used for prompts?

rootulp
Автор

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.

ovidiuc
Автор

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

Mempler
Автор

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

gmartins-dev
Автор

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.

AndyPayne
Автор

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

DavidSandoval-ddeq
Автор

@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?

tekskilldev
Автор

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

claustw
Автор

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.

mfsbo
Автор

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?

xxXmRpHusXxx
Автор

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

nanakwame
Автор

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

zachfotis