Sure, so the two are not exactly connected: I do use a bullet journal which helps to the simple fact I always have my notebook with me. When I read practical Vim, I used to memorize tips from the book and write them in my own words. Obviously it was the ones I wasn't aware of and felt were crucial. When the book talked about fundamental concepts like "movement" or "always the least amount of strokes" I wrote it down and the following tips (e.g. switching 2 characters or using / to move faster on a document or using vim marks to find your way in a repository of code). I didn't have a specific system, but the book is built in a way you can read single parts and just add them to your skillset. If you follow along and make sure you get everything, you get the small tips and the big ones in the order that makes sense and helps you grow your knowledge.
I hope this makes sense
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Sure, so the two are not exactly connected: I do use a bullet journal which helps to the simple fact I always have my notebook with me. When I read practical Vim, I used to memorize tips from the book and write them in my own words. Obviously it was the ones I wasn't aware of and felt were crucial. When the book talked about fundamental concepts like "movement" or "always the least amount of strokes" I wrote it down and the following tips (e.g. switching 2 characters or using
/to move faster on a document or using vim marks to find your way in a repository of code). I didn't have a specific system, but the book is built in a way you can read single parts and just add them to your skillset. If you follow along and make sure you get everything, you get the small tips and the big ones in the order that makes sense and helps you grow your knowledge.I hope this makes sense