I’m interested in any discussions/guideliness/effo...

# announcements

[Tristan]

I’m interested in any discussions/guideliness/efforts around how to write clean and expressive Kotlin.

I realise that there’s https://kotlinlang.org/docs/reference/coding-conventions.html but I’m looking more at how we can use a language like Kotlin to make code more readable and make intentions clear in a concise way. Not just syntax and capitalization, but more about what shape your API should have and how you can make it hard to use incorrectly (using static types and using clear naming).

I realise that these things aren’t really language specific, but I think it’s fair to say that without putting explicit thought into this, it’s easy to bring over baggage from previous experience (ie. Kotlin that looks like Java). I don’t want to bring up the s-word here (Swift) but I do see that the Swift API Guidelines (https://swift.org/documentation/api-design-guidelines) have been at least partially responsible for that community’s efforts in how to make code clear at the point of use, and to take advantage of the features that language provides (algebraic data types, internal/external parameter names etc) as well as a structured approach to thinking about API design.

I’ve been reading a lot about Kotlin from various sources and our team is using it day to day. What I’m looking for is the place that discussions take place, so that my team and I can learn from and participate in them, and also whether there are any community resources/guidelines around how to best use Kotlin in this way.

[thana]

maybe this could be the first topic for #CGDU0D2AC 🤔

[Tristan]

…. joining… thanks