Learning Kotlin by “Mistake”

I recently wrote about how the Android engineering team at Udacity has embraced learning Kotlin through experimentation and making “mistakes”.

 

Check it out here:

Learning Kotlin by Mistake – Udacity Eng & Data

As our individual and collective team understanding of Kotlin develops, we inevitably review & revisit code thinking things like: “I’ve learned 3 new ways to write this” “I prefer a different syntax/convention now” “What was I thinking when I wrote this the first time?”

 

. . .

Thoughts, questions, tips on learning Kotlin? Comment below or share on social media.  I’d love to continue the conversation.

 

I love to meet/talk/discuss with others so if you have feedback or want to chat you can follow me on Twitter, YouTubeMedium, or subscribe here to stay up to date on the latest posts from my blog.

My year with Udacity’s Android Nanodegree

Motivations and Starting Out

A little over a year ago, I had never heard of Udacity and had zero experience with MOOCs. I was a relatively new developer, having only completed my graduate work a year prior. I was eager to improve my skills both with the Android platform and as a software engineer in general.

Then, while live-streaming the Google I/O 2015 keynote I saw an announcement about this thing called a Nanodegree program as a means of learning about Android development using a curriculum and courses developed in conjunction with Google. I was immediately intrigued. It seemed like the perfect opportunity to level-up my skill-set, and I registered for a free trial that same week.

Read More »