Thanks for sharing, it is especially helpful for me to get a perspective from someone who actually has ADHD! I definitely thought personally that Kotlin had so

Thanks for sharing, it is especially helpful for me to get a perspective from someone who actually has ADHD! I definitely thought personally that Kotlin had some big advantages. • The most common comment on a pull request was asking people to remember to “@NonNull all the things!” so Kotlin’s non-null by default aspects seemed wonderful. • Maybe the second most common comment on a pull request was to replace “==” with Objects.equals(x, y), Kotlin just has a sane ==. Note that Objects.equals() is the correct choice because y.equals(x) is “safe” but unfortunately written Yoda-style whereas x.equals(y) causes null pointer exceptions (the x usually comes from a getter which is null-tolerant). • Kotlin had immutable records by default which made tests automatically more readable. • The ability to mix declarations for functions and data structures etc in one file, allowed for much less jumping between files. Meanwhile, the lighter syntax meant that the code in those files took up a lot less visual space, so these files were not overwhelming... So to your point it definitely “felt better to use and gave me more of my time back”, I felt, otherwise I would not have pushed for it. And yes I agree the time to learn the language should all be accounted for in development hours, not some weekend homework project, and I would definitely validate your skepticism about the dangers about caring for the company more than it cares about you.