|
|
|
|
|
|
by TheMongoose
456 days ago
|
|
|
Your manager is not your friend. Your company is not your friend. The internet is not your friend. Good news is that you're here asking for advice on how to drive your career instead of letting them do it. Bad news is I don't know how to help you if you don't actually want to write code outside of work. In general I've experienced a lot more valuable growth out of personal projects than LeetCode bullshit. I like to MAKE things, not solve pointless CS puzzles. My eyes also glaze over when I try to read a book or watch a video on some silly CS trivia. So if I had to rank effective strategies for me from least to most effective it's books -> videos -> stupid puzzles -> making things (using videos or other materials to get over sticky points) You'll notice some things here if you look closely. I have explained what works for me, and why. You'll have to do some experimentation to figure out what works for you, then lean in to that. Lastly for anyone that has trouble consistently doing a thing I always suggest the "just one hour" method. You promise yourself one hour of your best effort per day of working on that thing. If you're feeling good and get sucked in and work on it for multiple hours that's fine, if you struggling to give any fucks that day you complete the hour and move on to whatever other things you wanted to do. |
|
|
To clarify, when you rank effective strategies you're saying that, for you, books are the least effective and making thing is the most effective?