We continue our dive into how to learn things while Michael’s voice sounds an awful lot like Joe’s, Joe says it’s a square, and Allen says it’s a triangle … oh, and Google Feud is back!
It’s time for more cowbell as we have a special guest in the studio, Will Madison (@IAmWillMadison), join us as Allen finally gets tripped up trying to pronounce a name, Joe teaches us the value of practice, and Michael evacuates in a rainbow colored straight line.
- Airbrake.io/CodingBlocks – Try Airbrake *free* for 30 days _and_ get 50% off the next 3 months!
I recently wrote about the differences between programming knowledge and skill in a previous post. In short: knowledge is what you understand, and skill is what you can do with it.
However, it is not enough to “know” a programming language, you need to be able to make cool stuff with it. Knowing is only half the battle!
So…what advice does the software engineering industry have for programmers who want to advance their skills?
What does it mean to be good at something?
Knowledge is understanding of a subject, skill is your proficiency in the application of that knowledge. By definition, you can’t be skilled at something you don’t understand. But knowledge on its own is only half the battle.