There Has Never Been a Better Time to Learn a New Programming Language

I’m learning Kotlin. After a decade of Swift, Android was always the thing I’d get to “eventually” - and eventually arrived this year, mostly out of curiosity about how the other half ships. It has been the easiest language pickup of my life.

Not because I got smarter. Because the economics of learning a language just changed completely.

Syntax was never the expensive part

You can learn any language’s syntax from a book in a weekend. That was true in 2005 and it’s true now. The expensive parts were always somewhere else:

Idiom. Knowing what the language can write versus what its community does write. Every language has a dialect that marks you as local, and books are always five years behind it.

The toolchain. Nobody warns you that learning Android is 20% Kotlin and 80% Gradle.

The under-the-hood questions. The gap between using a language and knowing it is a thousand small questions - what does this actually compile to? where does this allocate? why is this fast and that slow? - that used to take years of scattered blog posts and Stack Overflow archaeology to answer.

AI didn’t make syntax easier. It made those three things cheap. That’s the whole story.

Learn by translation, not from scratch

Here’s the trick that’s made Kotlin feel easy: I never ask “how does Kotlin work?” I ask “in Swift I’d write this - what’s the idiomatic Kotlin, and why is it shaped differently?”

An AI that knows both languages fluently is a personal translator between mental models. And a second language learned by translation goes fast, because you’re not learning programming - you’re learning a mapping. let becomes val. Protocols plus extensions become interfaces plus extension functions. async/await becomes coroutines. Swift and Kotlin grew up watching each other, and it shows; some days the delta feels closer to an accent than a language.

Where the mapping breaks is exactly where it gets interesting - and that’s where an endless, patient explainer changes everything. Nobody at work rolls their eyes when I ask my fourth “but why is it like that?” of the morning.

Go under the hood - it finally costs nothing

This is the part I care most about. Knowing a language means knowing what’s beneath it, and those questions used to be the hardest ones to get answered:

What does a suspend function compile to? (A state machine with a continuation parameter - the same broad strategy Swift uses for async, expressed through Kotlin’s coroutine machinery.) What actually runs my Kotlin on Android - the JVM? (No: ART, with its own mix of ahead-of-time and JIT compilation. The JVM performance rules you may know do not transfer cleanly.) What does data class generate? Where do captured variables in a lambda live?

Ten years ago, chasing one of those to the bottom was an evening. Now it’s a conversation - and each answer survives cross-examination: show me the bytecode, compare it to what swiftc does, when would this bite me? Learning a language while understanding its machinery used to be a luxury for people with unusual patience. Now it’s the default way in.

The one rule: AI explains, you type

The discipline that makes any of this work: the AI writes none of the learning code. Every line, I type. The moment an agent writes my Kotlin, I’m no longer learning to write Kotlin - I’m learning to review it, which is a different and shallower skill. It’s the same logic as keeping the agent in a sandbox and integrating by hand: the friction isn’t waste, the friction is where the learning lives.

Use it as the tireless senior colleague instead - the one who explains, never judges the question, and has read every compiler source dump ever posted.

So pick the one you’ve been postponing

Learning a language is thousands of small questions, and the price per question just dropped to roughly zero. The language you’ve been putting off for years costs a fraction of what it did when you first postponed it.

Mine was Kotlin. It took a few evenings to feel at home, and the surprise wasn’t that it was possible. It’s that it was pleasant.