Skip to main content

I didn't notice this VS Code feature until it made me question how I code

I was working on a refactoring using VS Code the other day when I noticed something I hadn't seen before: a tiny bar chart quietly living in the status bar, tracking my AI vs. manual typing usage over the last 24 hours.

It's called AI Statistics, and it shipped in VS Code 1.103. To enable it, open settings and search for "AI stats" — flip the checkbox, and a small gauge appears in the bottom-right of your status bar. Hover over it and you get a breakdown: how much of your recent code came from AI completions versus your own keystrokes.


On the surface it sounds like a novelty. But I found myself actually pausing when I saw the numbers.

It reframed something I hadn't really thought about consciously: not whether AI coding tools are good or bad, but just how much I'm actually leaning on them day to day.

That visibility is weirdly valuable. It's the kind of data point that makes you more intentional — maybe you lean in harder on AI for boilerplate and pull back when you want to think through the design yourself. Either way, you're making a choice instead of just drifting.

It's a small feature, but it's one of those additions that changes how you relate to your own workflow. Worth enabling if you haven't yet.

Popular posts from this blog

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.

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...