<ul><li>So when you learn to code, your core skill is going to be constantly learning and constantly relearning. </li><li>That’s true in the short term and the long term. </li><li>Over the years, new languages and frameworks always emerge, and old ones evolve. </li><li>“Being a programmer basically means you’ll be an eternal student” </li></ul>

#9) Learn how to learn.

<ul><li>This is a big one. You should try to do some coding every day—at least, say, a half hour.</li><li>Why? Because this is just like learning Spanish or French: Fluency comes from constant use. To code is to speak to a computer, so you should be speaking often. </li><li>Bootcamps are good if time is tight .</li></ul>

#3) Code every day.

<ul><li>You can very quickly learn to automate boring things in you life.</li><li>That’s because computers are amazing at doing dull, repetitive tasks. They’re also great at being precise. Since we humans are terrible at doing dull tasks and quite bad at being precise, this makes us a match made in heaven.</li></ul>

#4) Automate your life.

<ul><li>“If you can learn one programming language, you can learn the other ones, and where you start doesn’t matter nearly as much as you might think,” as Quincy Larson, the founder of <a href="https://www.freecodecamp.org/">freeCodeCamp</a></li><li>“Stop looking for the perfect coding course,” advises Madison Kanna, “Just pick a curriculum and stick with it.”</li><li>“Find the jobs that you want, and then reverse engineer your curriculum” - Saron Yitbarek</li></ul>

#2) Don’t stress over what language to pick. 

“It’s better to do one hour a day then ten hours on Saturday”

<ul><li>Learning to code can be pretty isolating—it’s hours of just wrestling with the computer. </li><li>And while it’s good to try to figure things out, yourself, sometimes the fastest way to get unstuck is to ask someone else, How the heck does this work? </li><li>Frankly, I wish I’d done more of this socializing. </li><li>I too often spent time grinding away at a problem, myself, instead of asking for help. </li><li>When I did talk to other coders about problems I was having, inevitably they’d suggest an approach that helped.</li></ul>

#10) Reach out to other coders.

<ul><li>When you’re building stuff, you don’t need to start from scratch.</li><li>You can grab things that already exist, rip them apart, and see how they work. It’s a superb way to learn.</li></ul>

#7) “View Source”: Take other people’s code, pick it apart, and reuse it.

<ul><li>Sure, you obviously need to be able to think logically, to break big tasks down into tiny steps. That’s a prerequisite.</li><li>But if you asked me what’s the one psychological nuance that unifies all the coders I’ve interviewed?</li><li>They’re all able to handle total, crushing, incessant failure and roadblocks (at least, at the keyboard.)</li></ul>

Tough times don't last, Tough people do!

When you finally figure out the problem—when you fix the bug, and things start working—there’s a sudden, narcotic rush of pleasure that’s almost unlike anything you’ve ever experienced.

#5) Prepare for constant, grinding frustration. 

It’s never been easier to get started learning to code because there are dozens of free-or-cheap courses online.

#1) The online world is your friend. Start there.

<ul><li>If you’re coding in an abstract way, doing tutorials, it’s easy—when you get stuck—to think, ah, screw it, and stop.</li><li>But if you’re actually building a tool you’re going to use? It pushes you to go further, to work past the frustration and the blockages.</li></ul>

#8) Build things for you—code you need and want.

These were all small and silly, but they had to at least function, and when you have to make something function, that’s when you learn.

#6) Build things. Build lots of things.

I am a self-taught programmer, its true about the grind, its incessant and when you accomplish something that helps people at scale, it redeems itself. Learn coding to look differently at life.

Note from the editor: The following is a guest post by Clive Thompson (@pomeranian99), a journalist who's written about technology and science for two decades. Clive is a longtime contributing writer for the New York Times Magazine and a columnist for Wired. 

#8) Build things for you—code you need and want.

Similar ideas to #8) Build things for you—code you need and want.

7 Things You Need To Understand About Anxiety And Depression