,
5 tweets,
1 min read
Read on Twitter
This short screed is triggered by what I believe to be a rare stumble by my colleague and friend @chethendrickson, who tweeted that he prefers "knowledge" to "skills" in our recent musings on alternatives to "roles".
1/5
1/5
To me, knowledge is what we have when we leave the lecture hall, when we can parrot back what SOLID stands for (what /does/ it stand for, anyway?), when we can remember what all four of the Manifesto Values are, when we can define "refactoring".
2/5
2/5
Skill is what we have when we can apply the SOLID principles, when we live the values, when we can actually do refactoring.
We have skill when we can turn our knowledge into effective action.
3/5
We have skill when we can turn our knowledge into effective action.
3/5
We can't assess skill in a typical written exam that asks for facts, though we might manage it, for simple skills, in an exam where we solve problems.
To assess a builder's skills, I want to see what they have built, not just have them tell me what they know.
4/5
To assess a builder's skills, I want to see what they have built, not just have them tell me what they know.
4/5
Skill is the ability to apply knowledge. Skilled practice is what we want in our teams, and to get it, our people have to have all the necessary skills, not just the necessary knowledge.
Or so it seems to me.
5/5
Or so it seems to me.
5/5
