Skip to main content

AI and developer productivity

With the introduction of AI-powered code completion tools like Github Copilot, there is a lot of focus on developer productivity and how these kind of tools could/should/will improve it.

Of course we are doing our own experiments,  and although hard to proof it scientifically, our developers claim to feel more productive.

However when I ask more details, they mostly talk about it helps them write code faster. Although their statement is certainly correct, I think we still have to tap in on the real productivity win that these kind of tools can offer.

What do I mean? Let me explain!

A few years ago Microsoft conveyed a study where they investigated what developers do most of their time.




If you look at the results, developers spend most of their time on reading and understanding code, not on writing new code.

Remark: this is in line with my own experience.

So if these tools really want to improve developer productivity, these scenario’s are the one to focus on. Github Copilot is already investigating this area through Copilot Labs. You have for example the option to ask to explain your code:

 

Interesting times for a developer…

Popular posts from this blog

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         ...

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.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...