Knowledge transfer applies learned knowledge or skills to a different task or context. For programmers, earlier language experience can either open a shortcut or create a misleading expectation. section 5.4.1
Transfer helps when concepts align: a Java developer learning Kotlin may recognize a verbose declaration, infer its type, and simplify it. It hinders when familiar assumptions clash with a language’s foundations, as with JavaScript’s prototypal inheritance or Scala and Elixir’s immutability. section 5.4.1 section 5.4.1
A useful shortcut—and a dangerous one
A Java learner might transform `val boundsBuilder: LatLngBounds.Builder = LatLngBounds.Builder()` into `val boundsBuilder = LatLngBounds.Builder()`. The shortcut is useful because prior knowledge transfers; applying Java expectations to JavaScript, however, may produce confusion rather than progress. section 5.4.1
Make transfer more reliable by:
- Connecting new ideas to prior knowledge while checking whether the underlying concepts really match. section 2.4.2
- Retrieving ideas across different times and contexts instead of relying only on rereading or presentation. section 2.4.2
- Pausing over incorrect assumptions; syntactic differences may be easy to repair, while foundational differences need deliberate examination. section 5.4.1
val boundsBuilder: LatLngBounds.Builder = LatLngBounds.Builder()
Compare the explicit and inferred Kotlin declarations to see how knowledge of Java can support transfer without guaranteeing identical language behavior. section 5.4.1
