Congratulation on finishing this GitHub Copilot worshop! Hopefully, this workshop session was useful to understand how GitHub Copilot works in practice when you work with a full stack project.
Here is a summary of what you have learned.
- You used GitHub Copilot Chat in conjunction with GitHub Copilot's file functionalities to intelligently build a full end-to-end Python Django, PostgreSQL, and ReactJS stacks application.
- You know when to take GitHub Copilot's suggestions and how to use prompt engineering to get right answers first time.
Although GitHub Copilot keeps getting improved, here some general suggestions when you with GitHub Copilot, and many of these practices involve art of mastering prompt engineering.
- When you ask GitHub Copilot within file as comments or function names, try to be detailed as much as possible if you want GitHub Copilot to get it right first time. You can always override the suggestions given by GitHub Copilot.
- When you ask GitHub Copilot Chat, start with something simple and have a conversation with GitHub Copilot to provide more contexts as you keep checking if suggestions are correct. For example, don't start with something like
Can you help me to create a ReactJS application that works with my Python Django application and retrieves data in a table format?Most likely, you will get some irrelevant result from GitHub Copilot Chat. Instead, try to start withCan you help me to create a ReactJS applicationand give more contexts to build your work toward building projects that you have in mind. - Don't always 100% trust what GitHub Copilot make a suggestion to you, and always use your judgement to see what is right or wrong. Again, you are the main developer while your GitHub Copilot is just your assistance pilot.
I can add more stuffs, but this is just your start of journey. Congratulation on finishing your GitHub Copilot workshop course!
