My experience of using Github Copilot

 It's been a while since I posted anything here. Let's change that! :)

The first topic I want to cover is my experience using GitHub Copilot. Let's get started.

What is Github Copilot?

GitHub Copilot is an AI-powered tool designed to assist developers by providing hints, recommendations, bug fixes, and code writing based on context and guidance. The first version, available to everyone, was released in October 2021.

GitHub markets Copilot not just as a "code completion tool" but as an "AI pair programmer." This is a smart move, as it sounds intriguing and generates interest.

Github Copilot logo image

How to use Github Copilot?

  • Use simple and clear language so that Copilot can better understand your comments and intentions. 
  • Context is crucial for effective interaction with Copilot. Well-structured and readable code, meaningful names for files, classes, methods, and comments all contribute to better results.
  • The more you use Copilot, the better it understands you and the more relevant its suggestions become. Copilot learns from your actions and the suggestions you select, so frequent use can enhance the quality of its recommendations. The more you work with it, the better it adapts to your coding style.
  • It's important to describe the task or problem you want to solve in a multi-line comment at the beginning of the file.
  • Copilot performs best with small, clearly defined tasks. Break down large tasks into smaller ones, describe them, and Copilot will provide suggestions for each step. 
Binary search generation

When not to use Github Copilot?

  • Working with cutting-edge frameworks and libraries that are unfamiliar to the AI model.
  • Tackling complex, non-trivial tasks that demand innovative solutions and a high degree of creativity.

Conclusions

  • Autocomplete worked well in most cases. However, explaining and simplifying code and adding tests were less effective, so I wouldn't recommend focusing on those features.
  • Fixing code is interesting, but often developers will spot errors in the logs or by simply reviewing the code.
  • I found writing new features useful, and in some cases, it provided better answers than ChatGPT. I also really liked the chat feature since it eliminates the need to keep another tab open with ChatGPT.
  • The advanced search was also hit or miss. Sometimes it offered completely unrelated results.

Comments

Post a Comment

Popular posts from this blog

How to design tiny url system

Image
This post is a personal cheatsheet on how to design tiny url system. Questions to ask: What’s the length of short url? How many urls will come? What duration to support? What chars in url are allowed? Basic calculation: Let’s assume that we are allowed to use chars  a-z, A-Z, 0-9 (62 chars in total). Url with length of 1 char means we are able to generate 62 unique short urls, 2 chars - \(62^2\) urls, 3 chars - \(62^3\), etc… Let’s assume that we get x requests per second and the business requirement is to store the short versions of urls for 10 years. We get following equation: \(x\) requests per second * 60 sec * 60 mins * 24 hours * 365 days * 10 years = \(y\) We get following formula from equation: \(62^n > y => n = log_{62}(y)\), where n is the length of short url. n = 7 looks like a decent amount of unique urls (\(62^7\) = 3.52 trillions) System capacity: Let’s assume that we have have read/write ratio 200:1, number of generated links per month - 100 million. Write load
Read more

System design tips on how to make capacity estimation

Image
Estimation is an important skill in system design interviews because it allows you to demonstrate your ability to reason about the complexity and feasibility of a given problem. It is worth noting that estimation is an inexact science and that it is normal for estimates to be off by some margin. It is more important to show that you have a clear understanding of the problem and can provide a thoughtful and well-reasoned estimate than to provide a perfectly accurate one. Here are a few examples of the types of estimation questions you might encounter in a system design interview: How many users can a system support? For example, you might be asked to estimate the number of users that a social media platform can support, based on the number of servers, storage, and bandwidth available. How much data can a system store or process? For example, you might be asked to estimate the amount of data that a data warehouse can store, based on the size of the data, the number of serv
Read more

IMAP protocol summary

Image
IMAP - internet message access protocol. Versions : IMAP1 (Interim Mail Access Protocol) - 1986. IMAP2 (Interactive Mail Access Protocol) - 1988. IMAP3 - 1991. IMAP4 - 1994, last updates - 2003. IMAP is used to read emails that came to the user's mailbox. Emails are stored on server :  Clients connect to the server and download emails only after a user request.  The server can perform complex operations with emails. Advantages : Several clients can work at the same time. All clients see the same mailbox status. Disadvantages :  Protocol is more complex in comparison to POP3. Server space for the mailbox is usually limited. IMAP is an application layer protocol and uses the TCP transport layer protocol. Port 143. IMAP allows you to use multiple mailboxes or folders: Folders are stored on server. Folders can form a hierarchy. Emails can be moved from one folder to another. Flag : It's an email "label". Emails can have one or multiple flags. System flags: \Seen \Answe
Read more