Do you ever take on a learning track and sooner or later realize just how big the mountain is? Maybe you spend 3 months with your nose to the grindstone only to look up and see that you are nowhere near where you thought you'd be after 3 months, despite all the effort you put in.
I think as programmers, we naturally look for the most efficient way to do something. Even when we've optimized our learning, there's still no replacement for the time and elbow grease required.
What are your metrics for success when pursuing a new learning track? How do you move the goal post if you realized you've bitten off more than you can chew?
Maybe you have no metric for success, and your metric is more akin to spending 30 minutes a day working on X, 5 days a week.
Top comments (0)