Yeah, that is a good tip Franz! Thank you

Sometimes, I try to focus on a particular area in my articles/content and don’t spend too much time on things like that to avoid distracting.
About Jackson- I would go even one step further- we can configure that globally in our app. For example, for simple use cases we can make use of the application properties, e.g.: ‘spring.jackson.property-naming-strategy’ (source: https://docs.spring.io/spring-boot/appendix/application-properties/index.html)

For more fine-grained control, we could register our custom ObjectMapper, for example:

ObjectMapper()
.registerModule(KotlinModule())

(I do not recall the exact code, but basically we can configure plenty of things here)
And in general, with this approach we can have multiple mappers, we can set them for webclients, etc.

One nitpick:
For the usecase of conforming to snake case in JSON requests and responses, there is a better way than annotating each and every field. Better annotate the class:

@JsonNaming(PropertyNamingStrategies.SnakeCaseStrategy::class)