As a designer and developer, one of the easiest traps you can fall into is always learning new programming languages or tools, but never using them to build things.
There are over 700+ programming languages out there. What happens is you learn one, hear something exciting about a new language, and you start learning that one instead of using the first. And so we hop from one language to the next, without actually doing the thing they were each made for— to create stuff.
But it’s not just programming, anything we learn can get stuck in “learning mode”.
Learning is one important part of the equation — using what you learn is the other part. Both are required. And the order doesn’t necessarily matter. You can act first and learn from those actions, or you can learn and act on what you know.
Is a skill important if you never use it?
Perhaps. Anyone who knows how to defend themselves in a fight is grateful for their training and skills, and even more grateful if they never have to use them in a real toss-up.
But, in most cases, skills are only important if we use them. Otherwise, why did we spend so much time and energy learning them in the first place? To use them someday? Maybe. But someday is rusty.
Knowing how to do something isn’t enough. We must also do something.
Same same with knowing you need to do something. Knowing isn’t enough. We also need to do.
Join the Renaissance:
STAY BOLD, Keep Pursuing— Josh Waggoner | Daily Blog #1887
Newsletters: Considerations | Practices | Bookaholics
Subscribe: Renaissance Life on Apple Podcast| Renaissance Life on Spotify