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?
(While I’m busy writing my book, here’s a guest post on a topic close to me. I grew up in Japan as an American citizen, so I know how tricky it can be to cross cultures. Elisa Abbott gives us an overview of how localization is more than translating strings. —Jon)
As the world’s population is entering a phase of unprecedented growth, it’s essential to recognize that more and more people will own a smartphone. Billions of people don’t speak English as their native tongue, and maybe don’t know it at the most elementary level. This brings us to the idea that a high-quality localization (abbreviated l10n) of your app isn’t just an advantage — it will eventually become an indispensable part of app development.
Localization is the process of integrally translating your app content, yet also taking into account the linguistic peculiarities of a particular region. While this appears to be a very lengthy and strenuous process, research suggests that it has astonishing returns on investment. In this article, we’d like to look into the technicalities of localizing your app. Let’s dive right in, shall we?
Happy new year! It seems like good time for a Quality Coding retrospective. I also want to share some goals for 2018.
…Did someone say, “Are you writing a book?”
Do you enjoy conferences and workshops? Here’s my conference schedule for this fall:
I want to ensure my platform does the best possible job of answering your needs and interests. And that means I need to know more about you. To do that, I’ve created my 2017 Reader Survey.
Would you please take a few minutes to fill out the survey? By doing so, you will ultimately be helping yourself. Why? Because you will be helping me create content even more interesting and relevant to you.
Your input is important to me. The survey is easy to fill out, and the results are completely anonymous. I can’t tell who said what. And you can finish in five minutes.Yes, I’m Happy to Help. Take Me to the Survey!
Thanks in advance for your help.
If you’re interested in Swift development, and want to visit Japan, start making plans to go to the next try! Swift conference in Tokyo. It was my privilege to be a speaker earlier this month.
Let me share my impressions of the conference, and why you might consider making the trip there.
(But first, a side-note about this blog: Sorry I’ve been so quiet lately! I was spending my time preparing for try! Swift Tokyo 2017. Next up is CocoaConf Chicago, where I’ll be leading a TDD workshop in addition to giving a talk. But I’ve also continued to TDD a JSON parsing example, in both Objective-C and Swift versions, so I have plenty to blog about. To make sure you don’t miss any new articles, you can sign up to get updates via email.)
Do you enjoy conferences and workshops? I’m looking forward to attending, teaching, and speaking at these events in the fall of 2016…
Wow. I could never have imagined how 2014 would play out for Quality Coding. Check out this collage.
There are many people I want to thank, and I’m excited about what lies ahead for this blog.
For my European readers: I have two speaking engagements coming up in January 2014. The first is with Mobile Central Europe in Warsaw on January 11. I’m honored to be part of this brand new developer’s conference! Check out the cool conference trailer above.
Then after an eBay iOS Developer Meeting in Berlin on January 13 (for eBay Inc. employees only), I’ll be speaking at eBay Tech Talk in Berlin on January 14 (open to the public).
I hope to meet some of you soon!
NSBrief is a fun and informative podcast about Cocoa “developer-y topics.” I’m honored that I had my moment of glory on Episode #97: Jon Reid.
Host extraordinaire Saul Mora and I had an hour-and-a-half conversation about iOS unit testing, test driven development, and such.
There are a quite a few other episodes, but I’d like to recommend two in particular relating to testing:
Do you have any questions about anything we said during the podcast? Leave a comment below.