Depending on whom it is coming from, the phrase “I’d like to learn how to code” can mean wildly different things. To help shed light on the subject, I will attempt to put never-before coders into two distinct categories.
I. The Pragmatic
As a pragmatic, you’re not interested in theory. You just want to build a website. Or maybe you have a more pressing concern, like writing a script to automate certain tasks. In these situations, I recommend languages that are easy to learn to work with.
II. The Visionary
As a visionary, you’re not interested in simply building a website. You’d like to go deeper, digging into matters like: how to structure applications, organize complicated data models, interact with third party programs and databases, not to mention learning the differences between type systems, algorithm analysis and efficiency, etc. These are the things that get your blood pumping.
For big-idea thinkers, there are entire courses dedicated to these higher-level concepts. Languages like C, Java, C#, Swift can be helpful in enforcing inflexible or opinionated theoretical concepts in a classroom setting. Once you’ve got a solid conceptual grasp, the language you use is just another detail to keep in mind.
So Which One Are You?
In my experience with helping people learn how to code, there’s almost always a clear distinction between those looking to solve a problem with code and those searching for deeper understanding of it. With the first group, it’s incredibly difficult to impart meaningful scientific and engineering concepts when all they really need is a website or a quick script.
There’s a reason why Computer Science or Engineering tend to be four-year programs. A two-week boot camp or a weekend coffee shop session is geared more toward solving a specific problem. Which raises the question: Are you attempting to solve a problem or accomplish something greater?
If You Err On The Practical Side…
I recommend getting the scrappiest, simplest, most barebones development environment together — one that solves the problem directly and in a language that will help you build a solid foundation.
While you’re at it, pare down your goals to the basics, cutting out anything unnecessary. Learning how to write code can be a challenge. I recommend making progress in baby steps with simple code features that build on top of your previous successes. When you’re solving today’s problem the last thing you need to worry about is tomorrow’s solution.
If You’re Looking To Become An Architect Of Tomorrow…
You’ll want to seriously consider attending college. If higher education isn’t possible at this point, spend some time reading. Books like the Pragmatic Programmer and Code Complete: A Practical Handbook of Software Construction can be excellent starting points depending on your career goals.
It’s also a good idea to walk through programming tutorials at places like Tutorialspoint, Codeacademy, or Khan Academy. Tackling small programming challenges and discovering the “minimum viable product” will help you build up your understanding.
With this important distinction out of the way, it’s time to get started. Good luck!