I know a guy who is seeking enlightenment writing web frameworks. He is streaming new frameworks at ever increasing pace. Unfortunately, he never gets around to supporting what he has created, thus, he never learns how to make something that actually makes life easier in the long run. His frameworks are pure zen, but only to him. The rest of the team while their days trying to convince management that their high regard for the guys capabilities is completely misplaced.
I know a bunch of people that spend their entire time learning new technologies. New frameworks, languages, patterns. The learning is typically shallow as it ends the moment the person knows how to do anything with it or when he/she finds some kind of huge disadvantage. Then there is a switch to another language/framework/library/tool/paradigm and the eternal cycle repeats.
Stick with a project/problem until completion. Don't be satisfied with first 80% and neither with second 80% of the task. You need to go all the way. Try to learn everything there is to learn about it. Try to figure out all different ways to improve it and then try to figure out why those might not be the best ideas. Go discuss with your team, your architect. Listen to their problems, then figure out how your ideas do/do not help solve them. Understand why.
Try to make things so simple everybody can understand them. Try to be able to explain every decision and how those decisions interact with each other.