Has anyone given formal workshops at work to train their team on Kotlin? Do most people just follow...

# android

[Andy Gibel]

Has anyone given formal workshops at work to train their team on Kotlin? Do most people just follow the Koans or does anyone know of some opensource lesson materials to use?

[dewildte]

I put together a collection of YouTube resources for the team to watch. I also made a sample project focused on teaching the differences between the scoping functions.

[dewildte]

Derek Bannas has a great video called Learn Kotlin In One Video.

[Andy Gibel]

👍 nice. Yes I definitely wanted to spend some practical sample time on stdlib and run/let/apply/with/etc

[dewildte]

The best way to learn though is to make stuff in Kotlin.

[dewildte]

I do have a lagger on my team that is scared of change and did what ever he could to avoid using it. Eventually he had to use it because our manager forced him to get with the program.

[Andy Gibel]

ha wow. This is the first I'm hearing of an Android dev who doesn't want to jump off the Java ship right away 🙂

[myotive]

Hey Andy - I work for Big Nerd Ranch and we teach Kotlin for both our corporate partners and anyone who can get to Atlanta for our Open Enrollment training.

It's a rigorous two day course (or seven day course combined with our Android Essentials class):

https://www.bignerdranch.com/training/bootcamps/

[electrolobzik]

@dewildte could you please share playlist of videos?

[rkeazor]

Android studio has a learn kotlin plugin that really good

[Matej Drobnič]

The best way to learn though is to make stuff in Kotlin.

This. Throwing people into the deep end (letting them start with writing Java in Kotlin) while showing them various Kotlin "tricks" gradually over time is how I got most of my team on board and they love the language.

[Andy Gibel]

Yeah I think my team is at the writing Java in Kotlin level for the most part. Most of them have already done the Big Nerd Ranch training @myotive

[Andy Gibel]

So I guess the training I need is a big more nuanced. I was thinking about basing it loosely on the new "Effective Kotlin" book for instance but also covering some details on collections, generics, stdlib