Implementing a config feature to Fuzzier using Junie
Junie implementing global exclusions
I let Junie implement a new feature to Fuzzier. Here are some thoughts about that.
You can checkout the full PR below. I only wrote the changelog, but all other changes were made by Junie.
It’s not that simple
Evaluating pros and cons of AI is hard (for me).
Prompting
Nothing special going on.
The whole process took 3 separate tasks
- Initial change - 3 prompts
- Code review and clean up - 3 prompts
- Bonus base test for a class that didn’t have any tests - 2 prompts
Time
I don’t think I saved any time by letting Junie handle the code changes. Reviewing code, planning and prompting felt to me like it took around the same time as it would have taken me to just write it.
Estimation: ~30 minutes (source: my butt)
Friction
This change wouldn’t have been made today, if I hadn’t decided to let Junie start implementing it while I was cleaning.
Just getting started was enough to sit down and finish the change properly. This included going through the changes that Junie made, testing that the feature works and looks correct, and checking and updating the documentation to match.
Quality
Yes, the quality was better than I would’ve made. Junie fixed not trimming the text from the exclusion text area that I had missed when implementing project exclusions.
It also added a field that I had missed to the test bench implementation and suggested adding notes that / and * exclusions would match all files.
Price
During this whole process I spent 1,28 JetBrains AI credits. I didn’t take any special measures regarding token usage.
With the Pro plan, this converts to 1,28 euros.
Conclusion
I think Junie did a good job with the feature. For context the feature was simple and had a good example present in the code.