Skip to main content

Github Copilot– Some experimentation

I was reading the following blog post when I thought: "How good (or bad) would Github Copilot handle the scenario's mentioned in the post?" This post is the answer on this question. 

But before we dive in, I would suggest to first read the original post on the JetBrains blog: Critical Thinking in an AI-Powered World | The .NET Tools Blog (jetbrains.com).

Back?

Let’s get started!

I already created an XUnit Test project targeting .NET 8 and pasted the first snippet used in the post in a test class:

Now let’s ask the same question but not to the JetBrains AI assistant but to Github Copilot in Visual Studio:

Suggest a way to refactor the variable `now` so that I can control the value without depending on `DateTime.UtcNow`

Here is the response I got:

Similar to the JetBrains AI Assistant it suggests me to create my own abstraction and create an IDateTimeProvider interface. Too bad! Let us also mention the TimeProvider class and see if we get a better result:

Please use the ‘System.TimeProvider’ class found in .NET 8 and C# 12 instead

But again, the results turn out quite similar:

So far, we cannot make a different conclusion as in the original post.

Take 2!

Ok, let’s refocus our attention on the second part of the post and let us see how Copilot helps wht the implementation of the CalculateFallTimeAndVelocity method:

Let’s see what the suggestion is that the system comes up with:

Not bad either! 

But let us improve our understanding of the magic values by using the following prompt:

Move all constants to descriptive variables.

I just apply the suggestion and the result looks like this: 

She(he?) didn’t isolate the Factor value but with the comment in place I can understand the role of the 2 in the code above. 

We continue with the next prompt:

Set the value of Gravity to Earth’s gravity up to four decimal places of precision

This gives us the following result:

Too bad! Although the value itself is correct, it gives me a suggestion with 5 decimal places of precision:

We end with the last prompt:

Comment each line with valuable information that explains what’s happening

And this is our final result:

Conclusion

Based on this I could only agree with the conclusion of the original post but applied to Github Copilot:

Github Copilot can help you solve a new fascinating set of problems but does not claim to be infallible. Since it uses models trained on human data, it can sometimes be wrong. That’s why you should think critically about responses and always take steps to understand and verify the results of any LLM-based product.

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...