The Practical Nature of Coding Skills
Fundamentally, coding is a practical skill. It's not enough to be able to explain how to write code - you have to be able to do it. A lot of what you learn at university is theoretical: you learn to talk about software design, analyze code, evaluate architectural choices - which is not the same as being able to produce working software.
Professional programmers learn a huge amount of what they need to know on the job and at industry training courses. If you understand how practical skill acquisition actually happens, I think you can make better choices in your career.
"There is definitely a difference between a practical skill - being able to do something - and a thinking skill of being able to explain it."
The thing about software is it's all about practical skills. Skills like test-driven development, pair programming, continuous integration, and writing clean, maintainable code - these are things you don't learn at university, at least not in enough detail that you can really start using them on the job until you've had feedback and practice.
The Path to Proficiency
Skill acquisition follows a progression: from initial familiarity, to comprehension, to conscious effort, to conscious action, to proficiency, and ultimately to unconscious competence. You can't skip steps, but understanding this progression can help you learn more effectively.
One of the best ways to acquire practical coding skills is to learn in a group - whether with colleagues, at user groups, or coding dojos. Getting feedback and encouragement from others makes the learning process more effective and more enjoyable.
Want to improve your practical coding skills?
Explore Coaching Options
Comments
Post a Comment