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.
I’m taking a break from my normal content this week because JetBrains have just released an early access preview of their AI Assistant, and I wanted to be the first to make a video on it!
As luck would have it, I needed to make a diagram of the package structure of the Gilded Rose codebase, and I couldn’t find anything in the IntelliJ menus, so I thought that I’d see if AI assistant could help.
By the way, to access the tool, you need to download IDEA 2023.2 EAP, and log in to the AI service - details are here https://blog.jetbrains.com/idea/2023/06/ai-assistant-in-jetb... There seems to be a bit of a waiting list, so I hope that this isn’t too much of a tease if you don’t get access straight away.
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.
I'm confused. I don't think this is a JVM - it doesn't load and exectute byte-code at runtime. So is it a cross-compiler to C with a runtime that manages GC?
I've been pair-programming for over 15 years now, and was introduced to mobbing by Woody and Llewellyn a couple of years ago. I've tried it in a couple of teams for specific tasks. I don't think that in a team of experienced devs I would mob all the time (although if the team wanted to I wouldn't veto it), but it definitely has its place. In particular for learning new techniques, large refactorings and exploring solutions with customers.
I really didn't see any issues other than day-rate-compression through my 40s. Now I'm nearing 50 my memory definitely isn't what it used to be, but my expression in code is improving to compensate.
I feel that my influence and ability to drive good outcomes gets better as I learn more about myself, but the nurses here are telling me to go back to bed, so I'll have to turn off this computer thing now.
I was thinking that his point here would be that we always have to consider the noop case, the empty list etc. But no, so this item ironically added nothing to the piece.
I wonder how many of those data points are mine? Disappointingly I can't find any route that I alone have run or ridden - that's something to fix this summer I think.
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.