@jaroslavholan @banterCZ

I have tried vibe coding too
These two gradle plugins are done by Claude code I was more less navigator

https://github.com/zvrablik/forbiddenPackages

and https://github.com/zvrablik/downloadMaven2Repository/tree/development

These two plugins would never exist without LLM. I would hack it somehow to Gradle code.

drawback in such code generation is that I don't remember much of it in details. Ok for support tools but talking about generated code when something happened in production may be not fun.

@jaroslavholan @banterCZ

I got task to convert old product from javaee to jakara last year.

First part I had to do manually as we did not use any LLM but in the second part I was able to use claude code. It was like switching to warp speed. Testing options was way quicker and throwing away all changes was much easier when I found better way.

@jaroslavholan @banterCZ

I try keep the context very narrow (e.g. specify files to use in context) to avoid generating heap of code or solving something else.

4. refactoring - usually in non-trivial refactoring - it helps me understanding the code, doing partial refactoring, but still I do write some code

8. rewriting from one language to another -e.g. Gradle Groovy DSL to Gradle Kotlin DSL I get quickly working code as starting point and now I could refactor bit by bit.

@jaroslavholan @banterCZ

I use claude code, Opus model with Intellij Idea MCP and Jira MCP

My task where LLM has good results (for me):
1. upgrade libraries in case the api changed
2. replacing deprecated function calls - usually in combination with open rewrite
3. code review - now I investigate using claude code skills (like the OWASP)
4. refactoring
5. web UI - usually scafolding before I ask somebody to help me :)
6. generating release notes
7. generating configuration files