Look at the specific problem you’re having I’ll start with my long term goal and then my more immediate ones. It’s what I’m paid to do, it’s what any annual bonus is appraised on etc. You need to hit the ground running.Īs a senior developer getting to grips with a project, my motivation is to know enough Kotlin to be able to contribute to the quality of the codebase. Rarely do you have time and budget to learn a book inside out. However work life tends to be a bit more complex than that. Reading a book for the book’s sake is much easier – if you get the big concepts out of the book you’ve succeeded. Where this gets tricky is determining what ‘meaning you’re after’. There could well be foundational steps along the way, but I need to keep my eyes on the prize. To do that, I have to fit what I learn into the available hours I have at work, and the particular project I’m on. Otherwise we might risk focusing on trivia and minutiae and miss the big picture.Įven that isn’t enough though, if i want to Learn Kotlin more effectively. The idea here is that we find the overarching concepts as a kind of ‘primer’ for our learning. I’ve written about the excellent ‘ Make it Stick‘ and in that book, there was a concept of ‘searching for meaning’. We’ll start with the ‘search for meaning’. Review that periodically so that you can link the “I should do this” to the “this is how I did this” in your head. As you do each ‘ drill‘, question where it belongs in relation to your overall goals. Picture courtesy of TLDR – set some goals up to go alongside your training materials.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |