dmcg

Last month Jetbrains released an early access preview of their new AI tool Junie. Junie is an agent. This means that we can give it a goal, it will devise a plan, and then execute tasks autonomously. It can even change its behaviour based on how things are going.

In this first look at Junie I’m going to tell it the rules of Test Driven Development and see how well it can follow the process. As in the last episode, I will write the tests, and ask Junie to write the implementation code.

This one is really, really interesting.

This. Not the speculative builds thing, but the organising your codebase so that you don’t have this problem.

Our code structure needs to support both the functionality required by our customers, and our needs as developers.

This reminds me that because array access is just addition, in C you can also write 2[a] to access the third element of a.

In the same timescales I was thinking the same thing, but in particular recording the conversation between pair programmers.

OneNote had (has?) a mode where you could click on sections of a meeting note and hear the audio from the time the text was written.

Extend that to an IDE and every time you found yourself saying “what were they thinking when they wrote this?” you could listen in on the conversation and find out.

Does oneOf not cover it?

And thanks for the downvote, keep making sure no good deed goes unpunished.