Not just you. 'Magic' seems great until newer members of the team have no idea how it works and just use it - then things get painful.
It just magically understands your query based upon the name of the function.
There is far too much "magic" going on these days which has a massive learning curve for the newbies, and a headache for everyone else when something stops working because they've changed how the incantation works.
I haven't picked it in the past except for a toy project, to experiment with Lombok.
It has some interesting ideas which would be nice if they folded it into Java, but while it's fringe it ends up being a liability.
> val a: Int = 1
I wouldn't want to inflict that on anyone.
Don't get me wrong, I still pick Java over Kotlin, but I thought ktl had type inference. Even Java has "var a = 1" now. I just wish we had optional named parameters in Java, that's like, my biggest issue with the language.
[0] https://www.oreilly.com/library/view/kotlin-programming-the/...
Optional named parameters and also default values would be great.
The stuff that gets used by the most in this codebase is the `allParameterConstructor` for enums and the `slf4j` annotation. Without those two I could probably remove the Lombok dependency.
It is for this reason I don't use it (also I don't like too much magic, but that's me).