Why use AI pair programmers?

I have been using Github Copilot for a few months now and have been blown away at how helpful it is when writing tests. These tools get a lot of bad rap, but I suggest you try them before you knock it. Tests are a great place to start.

Writing Tests for GeoAsteroids

I have this [2D spaceship game] I wrote in Typescript. It didn't have any tests, so I thought it would be an excellent place to try Copilot. 

Test moveShip

The following function fires whenever the user presses the up arrow on their keyboard.

 * Move ship based on its x and y velocity
function moveShip(ship: Ship): void {

  ship.centroid = new Point(
    ship.centroid.x + ship.xv,
    ship.centroid.y + ship.yv,

Copilot cleverly suggests the following test without me typing anything! It's exactly what I was going to write anyway.

test.concurrent('Move Ship', () => {
  const testShip = new Ship();

  testShip.xv = 1;
  testShip.yv = 1;


AI pair programmers are not perfect. Sometimes the suggestions are flat-out wrong, and I am always weary of mindlessly accepting the autocomplete. But tools like Copilot already deliver great value for low-hanging fruit like writing tests. I am excited to continue using it and look forward to Copilot taking more and more off my plate. This way, I can focus on the most creative aspects of programming (writing new features!).

Back to Home
 Profile Picture
Profile Picture

About John Solly

I am a Senior Software Engineer with a focus on geospatial applications, based in the Columbus, OH metropolitan area. This blog is where I delve into the intricacies of GIS (Geographic Information Systems), offering deep dives into different components of the geospatial technology stack. For those who share a passion for GIS and its applications, you've found a spot to explore and learn.

Interested in collaborating or learning more about my work? Take a look at my portfolio for a showcase of my projects and expertise.


  • No comments yet.
Login to Comment