Category / learning

by Nathan Coumbe

I don’t like the word “talent”

“Talent” is something you’re born with… It’s innate, unchanging, and implies that if you don’t already have it, you never will.

“Skill” is a more accurate term. Skills can be learned, and most everything we consider to be talents are actually skills.

  • Musical abilities
  • Public speaking
  • Leadership
  • Writing
  • Painting
  • Inventing
  • Salesmanship
  • Teaching

People aren’t born to do these things. They try them out and persevere through the poor quality and failed early efforts until they get better.

Calling a musician “talented” might actually be an insult. Why?

Because it dismisses all the hard work they put in to develop the skill of musicianship.

by Nathan Coumbe

What could you do with 30 minutes a day?

Here are just a few things…

  • Read 20 books a year
  • Build a strong, resilient, powerful body
  • Cook a delicious and nutritious meal with your partner
  • Write three pages of something… or finish a book in less than a year
  • Learn a new language
  • Develop a new skill like drawing, dancing, or public speaking

Where does this time come from?

By saying no to a few minutes of social media each day. Or watching one less episode of your favorite show. 

That small sacrifice can pay enormous dividends in your future, and your life satisfaction in general.

by Nathan Coumbe

Improvement is ugly

One of my favorite quotes from Julia Cameron’s The Artist’s Way is this:

“It is impossible to get better and look good a the same time.”

Often, how we think others view us stands in the way of making progress. 

If we’re worried about what others think, we’ll pretend to have expertise we don’t—and often make ourselves the fool we were so worried of being. 

Or we’ll fall to braggadocio instead of humility when faced with someone who can actually help us improve.

She continues:

“Give yourself permission to be a beginner. By being willing to be a bad artist, you have a chance to be an artist, and perhaps, over time, a very good one.”

Keep a beginner’s mind as much as possible. You’ll go much farther and faster if you do.

by Nathan Coumbe

“Being” requires “doing”

You become a writer by writing.

You become a leader by leading.

You become a doctor by doctoring.

You can learn the principles and the ideas behind these fields from books and courses. But the skill to do them is only developed through practice.

Zig Ziglar said: “If it’s worth doing, it’s worth doing poorly.” That’s where you must start.

Anything worth being only comes about as a result of doing.

by Nathan Coumbe

Artists & fly fishing

Seth Godin has a short chapter in his book The Practice on his experience learning to fly fish. 

At the retreat, he specifically requested that he not have a hook attached to his rod so he could focus instead on the practice of casting perfectly. 

Without the hook (and therefore without any chance of catching anything), there was no way he could obsess over the outcome. He was focused on the process when everybody else was focused on catching a fish.

The result—he learned how to cast perfectly and mastered fly fishing. His friends obsessed over making a catch and failed to develop the necessary skills.

This is how artists must work. They must focus on the process, not the outcome. They must create and ship work on a regular basis without worrying about whether or not this project will be “the one.”

Process, not outcome. That’s where we need to redirect our focus.

If we don’t set out to create a masterpiece, it’s much more likely we’ll make one in the end.

(A personal aside: I realized after reading this passage that my dad was an artist in the same way. He loved fishing and genuinely did not care if he caught a fish or not in the process. He was totally at peace on a boat or pier casting and reeling, over and over. He had the mindset and demeanor of a true artist.)

by Nathan Coumbe

“Googling” is an underrated skill

If you spend any time coding, you’ll quickly discover that you don’t know, can’t remember, or never learned something you need to make your project work. 

Enter Google (or whatever search engine you prefer*). 

All you have to do is type in a few words related to the problem you’re trying to solve and voila! You’ve got your solution. 

Seth Godin says in his great talk, “Stop Stealing Dreams,” that there’s no longer any need to memorize stuff. And this is exactly why—if you need something, you can just look it up.

I would agree with him, but I’d also take that idea a step farther.

As you look things up and implement them in your projects (and not just coding projects either), they will eventually become muscle memory.

The important thing is implementation—put what you look up to use immediately so that it slowly becomes a part of your vocabulary. 

I think there are two points to this post:

  1. Learn how to get good at looking up the answers to your problems rather than staying stuck
  2. Memorizing things for the sake of memorizing is pointless—but memorization will come naturally as you IMPLEMENT what you look up

*Instead of using Google, I’d highly recommend you check out Ecosia as your new search engine. Here’s why:

  • Your search results are THE SAME as what you’d get on Google
  • Your information isn’t constantly sold to the highest bidder
  • You aren’t inundated with useless ads from the highest bidder instead of quality search results
  • Using Ecosia makes your searches CARBON NEGATIVE
  • For every 45 searches you make, Ecosia plants a new tree in a place where it’s needed (that’s every 11 days for the average person)

While you’re developing your “Googling” skills, consider switching to Ecosia today.

by Nathan Coumbe

Codecademy gets education right

I’ve been spending an hour (sometimes more) each day learning to code for the last couple of weeks using Codecademy. 

And from the beginning, I noticed something different about this learning experience…

It works.

Codecademy gets it right because it’s project-based, self-directed learning. 

I don’t sit through lectures and get quizzed on my ability to recall information. I don’t memorize a bunch of facts only to forget them half an hour later. 

Instead, I work out specific coding problems; I build projects using the coding languages I’m learning. 

In short, I’m building and practicing skills. 

We don’t learn by accumulating and regurgitating information. We learn by developing skills through constant, sometimes mundane practice.

That’s how da Vinci did it. It’s how Mozart did it. It’s how Steve Jobs did it. 

How can you work projects and problem solving into your education?

by Nathan Coumbe

Remember your founder’s roots

It amazes me how many companies still require their prospective employees to hold college degrees before they’ll even CONSIDER talking to them about work…

Especially because so many companies are founded by college dropouts, straight-D students, and vocal critics of modern education.

With so much information and easily accessible methods to build the skills necessary to do competitive work, college is quickly becoming a handicap more than anything else.

It’s four years spent in a classroom accumulating information rather than developing skills, building projects, and doing actual work. (And yes, I’m a college graduate who’s criticizing EXACTLY what I went through).

Never will you be required to sit through hours of lecture and regurgitate information on tests in your working career. But that’s what I’d estimate 90% of college is.

How does that help a company looking to hire for a role? Obviously it doesn’t.

I’d like to see more companies embrace what Apple, Google, Amazon, and other big tech companies are doing:

Value competence and proven skills over accreditation and papers.

Show you can do the work and forget what your “education” was all about.

Hopefully more companies will remember their founders’ roots and get out of this antiquated industrial mindset.

by Nathan Coumbe

Build your way forward

Imagine a web designer sitting at her desk.

There’s this nasty problem plaguing her current project. For the life of her, she can’t figure it out…

What does she do? She sits and thinks and thinks and thinks until she comes up with a solution.

Right?

Wrong!

She’s a designer—she builds her way forward. 

She writes a line of code and runs it. Does that fix the problem? No. Did she fail? NO! She just learned something about her code. 

So she writes another line and tries again. She builds her way past the problem one line of code at a time. 

Maybe we should approach more of our problems like designers. 

Instead of trying to think our way forward, we build.

by Nathan Coumbe

There is no such thing as failure

There is only feedback. 

People who develop a growth mindset view every failure as a learning opportunity, not an end result. 

Either you succeed or you learn. But you never fail. 

Of course, something might not work out like you planned. But as long as you learn from the incident and improve, did you really fail?