Kotlin won’t save your skin if the code you wrote should be performant but you layered it into a heap of abstract classes, interfaces, factories, etc and, realistically, no one else would use or expand on that

Only once, tho

This is the scorched earth approach to error handling

No, he is on a pointer to a pointer to a point tonight

Technically correct is the best kind of correct