Kotlin at Adobe - What Does It Look Like Today?

The biggest reason for us to be asynchronous programming with coroutines is maintainability. The code and the things that people have written during this 80% is not wasted when you need to go to that, I don't know, 20% and fine-tune things. We've figured that part out, I think, pretty well, at least for your team. What does Kotlin at Adobe look like tomorrow? And especially also in regards to, are you trying to push the things that you've learned here to other teams and advocate a little bit more? How's that looking?