4 ms·
The post isn't really well structured, but the key points here are: * Expertise isn't an achievement, it's how we define a certain number or quality of achieve
by JayNeely 18y ago
The post isn't really well structured, but the key points here are:
* Expertise isn't an achievement, it's how we define a certain number or quality of achievements.
* Becoming an expert on a skill is about learning that skill's vocabulary so well that you can express yourself in it as you wish.
* Your metrics for expertise in a skill should be put in terms a non-expert can understand, if you want to be recognized as an expert.
- sh1mmer 18y agoI wouldn't agree with this summary. I think he was saying 1) Expertise is relative. His example included the temporal nature of the "cutting-edge" in computing. What was consider best practice 10 years ago is no longer considered even ok. 2) Achieve things by setting an actionable next step instead of a goal of becoming an "expert" A next step e.g. getting a patch into Rails Core will move you forward, trying to be an "expert" cause you to do things which make you an expert in the eyes of others. I.e. you'll work to fulfill the definition in 1)