Kotlin in contrast just sounded so alien to me. Threads? Types? Nullability? Coroutines? How old is this language anyway? Even the name sounded caustic and uninviting. How would I get through the first few weeks of slogging through and feeling unproductive? I love feeling productive. But most importantly, would this be a step forward or a step backward for my career?
Then the quote from the Pragmatic Programmer surfaced in the back of my mind:
Learn at least one new language every year. Different languages solve the same problems in different ways. By learning several different approaches, you can help broaden your thinking and avoid getting stuck in a rut.
It helped me realize that I was framing the choice incorrectly. Learning Android would actually deepen my expertise as a client-side engineer because I would be solving the same problems but in a different way using different tools. In fact, I would be gaining broader knowledge within my specialization. I also knew that I needed to get out of my comfort zone. Shortly after, I let my manager know that I was ready and excited to make the change to Android, and I’ll be starting next week!
Stay tuned over the next few weeks to hear how it goes! Follow me on Twitter: @BiancaGando or sign up for Thumbtack Engineering Blog at the top-right of this post for updates!
P.S. Interested in having an existential crisis of your own? Or how about working at a company that encourages career growth and has lots of challenging problems on iOS or Android? We’re hiring!