Look for weaknesses you have as "a developer" (or whatever you want to be). Focus on them. Work at them until you get better, or at least more comfortable. F

Look for weaknesses you have as "a developer" (or whatever you want to be). Focus on them. Work at them until you get better, or at least more comfortable. Find new "muscles", skills, what have you and push them. It's a lot like music. Specifically for me, it's been reading. I used to not like reading source code. I often wouldn't know what I was looking at. If I found the style strange, I wouldn't know if it was inherent to the language, the project, or just the developer. Just knowing library X can do T doesn't always answer the question; sometimes you have to know exactly how it does T, with what tradeoffs &c. Same goes for APIs. Reading has brought me more learning than anything.