This week, I’m learning Kotlin. And what better way to learn a new language than by writing unit tests against the code?
What’s going on, you ask? Is the world coming to an end?
By day, I currently work for American Express, on the Amex iOS app. (Views expressed here are my own and do not necessarily reflect the views of my employer.)
And one of the benefits of working at Amex is, I get a full week to learn something new. (Work-related, of course! It can’t be “Best Beaches of Hawaii”.)
So, I’m going to learn Kotlin, the language of my Android cousins. (Just Kotlin at this point, no Android.)
But me being me, I want to use a test-centric approach. Unit tests can’t tell me if I’m writing “Kotliny” code. But they can tell me if the code works.
Update: You can watch a recording of me live-coding this.
Do any of you have Kotlin experience? If so, I’d like to hear from you. What are your tips & tricks? Are there any unit test gotchas? Is there anything like SwiftLint that can give me guidance about idioms? What’s the tooling like?
Help a brother out, leave a comment below.
Programming was fun when I was a kid. But working in Silicon Valley, I saw poor code lead to fear, with real human costs. Looking for ways to make my life better, I learned about Design Patterns, Refactoring, and Test-Driven Development (TDD). Programming became fun again! I've now been doing TDD in Apple environments for 18 years. I'm committed to software crafting as a discipline, hoping we can all reach greater effectiveness and joy.
Please log in again. The login page will open in a new tab. After logging in you can close it and return to this page.