Um, at what point should I worry about using serialization or not? Is this a, an important topic in a small project? Is it only in big projects with a lot of traffic and a lot of data being handled? W-Is there thresholds where should I consider my options?

Well, I think, uh, it's, uh, not so much about, uh, per-performance because Jackson works extra, exceptionally well, es-especially with the Blackbird, uh, thing that optimizes, uh, code on the fly.

I think it's more about how you write your code and how clean your abstractions are because the cleaner the abstractions are, the easier it is to de-debug [laughs] and write tests.

Should I still use reflection serialization in my project, or try to avoid it completely?

Uh, well, I have mentioned before that we had to basically use Jackson because Kotlin, uh, didn't have the feature of handling, uh, unknown fields.

But, uh, [laughs] the thing is, there is an open mesh request in the repo that, with exactly that.

Yeah, and [laughs] I'm still checking from time to time, is it, is it merged or not.

But yeah.