Strategies for learning a new programming language.

Hello World, welcome to Dev Terminology, where we talk about dev concepts.

Today’s topic — Strategies for learning a new programming language.

Note: some of these techniques may work for you, and some may not. If you get stuck or notice that these strategies aren’t working, then pivot. Try other strategies to find what works best for you.

Learning a new language is like learning a new way of thinking.

Strategies for learning a new programming language — The Gist … Practice

Choose your programming language.
Read the Docs and go through the doc tutorial page.
Practice with coding interview problems.
Get started on a small project.
Engage with the community for support.
Dive deeper.

Remember that everybody learns differently, and regardless of your background, you are not alone. Learning to program is a never-ending struggle.

Learning anything requires time, patience, and practice.

Strategies for learning a new programming language — Overview

Choose your programming language.

At this point, I’m going to assume you understand the fundamentals of programming; if not, take a moment to learn them. It’s important to have that foundation.

Programming Fundamentals

Once you’ve got your foundation — choose a language that you want to learn.

Read the Docs and go through the doc tutorial page.

Reading docs can be a real snoozer, so remember that reference docs are generally written to be searched through rather than memorized — so don’t read it like a novel.

Skim through the table of context
Jot down some notes on:

Things that look familiar, and look the way you expected them to.

Things that look familiar, but do something unexpected.

Things that look totally new.

Read about the language and find the differences. Ask yourself questions like, is this language statically typed or dynamically typed? Is it compiled or interpreted? Jot down the paradigm you’ve never seen before.

Now go through the getting started tutorial to get set up.

Print Hello World!

Practice with coding interview problems.

You might be wondering — Why coding interview problems?

Gist — To help you build pattern recognition.

Coding interview problems are preset problems that allow you to focus on a specific idea at a time. Unlike small projects, coding interview problems are a bit more straight forward — you get a question, you give an answer. Solve a problem, then move on.

So how many problems should you do?

50, 100 + maybe? Honestly, it’s really up to you. Do enough to cover the foundational blocks — a set variety of different kinds of problems (i.e., Variables, Loops, Conditional statements, Functions, Data structures, Classes, etc…)

As you go through these problems and encounter something you don’t know how to do — look it up. Call your friend Google to help you out.

While you are solving these problems, consider coding by hand. — Build that muscle memory.

Don’t forget — The Goal of this is to gain a foundational understanding, and it may expose the gaps in your knowledge. Make sure to keep track of what you don’t know so that you can revisit it later.

Where to find coding interview problems

Get started on a small project.

Maybe consider having a toy project that you can implement repeatedly in whatever language you are learning so that you can see the differences between how each language you’ve learned goes about doing the same thing.

Focus on getting your code as clean and idiomatic as possible.

Template projects:

Project Euler
Rosetta Code puzzle
With template projects, you can often compare your solution to those written by others in the same language. Take note of the differences and ask yourself what can you improve on.

Engage with the community for support.

Get your projects code reviewed.

If you need more help, find tutorials, crash courses, articles, books, and/or a mentor.

Dive deeper.

Write production-ready code in the language. Use the language in a more realistic setting to help you explore its real-life advantages and challenges.

Read and test out lots of code — example code and production code.

Practice, Practice, Practice.

Maintain your enthusiasm.

Final note — Once you’ve learned it, teach it in simple terms (see it, write it, speak it, repeat).

This was Dev Terminology. Thanks for reading.

Credits and acknowledgment to the dev community.

Written by Jessica Dosseh

Find Jessica on: [GitHub, LinkedIn, Twitter, Patreon, and Portfolio]

Find theDevnotes on: [GitHub, Twitter, Blog, Medium, Dev.to]

P.S: [Dear reader — visit again sometime :)]