Skip to content
0:00 / 0:00

#jetbrainsjunie#aiagent#tdd

First Look at JetBrains Junie Autonomous AI Agent

Pairing with Duncan

4.5K subscribers • 13 videos on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • May be out of date. The tools, versions or practices it shows have likely moved on.

Beginner. No background in the topic needed.

8.6K views1 year ago1 recommendation

AI and machine learningTools and practiceAI for codingAI agents and tool useTesting

Duncan tests JetBrains' autonomous AI coding agent Junie by having it implement code using test-driven development.

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. Join Duncan as he takes an in-depth first look at Juni, JetBrains' new AI tool, demonstrating how it autonomously follows the rules of test-driven development. Watch Duncan initiate tasks, review the tool's performance, and explore features like file creation, proactive task execution, and interaction via guidelines. Despite some technical hiccups, Duncan showcases the potential of integrating AI with coding workflows, emphasizing strict TDD for effective problem-solving. In this episode * Introspecting an existing project * Early Access weirdness * Brave Mode * Setting parameters * Tell Junie about Strict TDD - It makes a plan * Ask Junie to create a test * Goodness it's eager * I'll take control and write the test I want * Down boy * Now another test * We get out of sync somehow * Reboot the chat * Reboot IntelliJ * Now we are green we can reformat * Prompt a refactor * It's being proactive again! * More tests to add features * Junie is high on its own supply * Another test to refine behaviour * Println debugging is back! * Communicating through test names * If that fails just say what we want * More EAP editor state issues * Ask for another refactor * The Verdict There is a playlist of AI episodes - youtube.com/playlist?list=PL1ssMPpyqociSAO5NlyMEYPL6a9eP5xte If you like this video, you’ll probably like my book Java to Kotlin, A Refactoring Guidebook (java-to-kotlin.dev). It's about far more than just the syntax differences between the languages - it shows how to upgrade your thinking to a more functional style.

Why it's here

1 person recommends this

u/dmcgin r/Kotlin • Recommends

…0:17:54 Junie is high on its own supply * 00:21:01 Another test to refine behaviour * 00:21:43 Println debugging is back! * 00:22:23 Communicating through test names * 00:23:20 If that fails just say what we want * 00:24:24 More EAP editor state issues * 00:26:32 Ask for another refactor * 00:28:06 The Verdict There is a playlist of AI episodes - link to this video If you like this video, you’ll probably like my book Java to Kotlin, A Refactoring Guidebook (http://java-to-kotlin.dev). It's about far more than just the syntax differences between the languages - it shows how to upgrade your thinking to a more functional style.…