tutorial purgatory - freeCodeCamp.org

How I Escaped Tutorial Purgatory – and How You Can, Too

freeCodeCamp — Mon, 23 Nov 2020 17:50:41 +0000

By Daniel Chae

Tutorial purgatory. We've all been there. The mindless scrolling, pausing, and playing. All the copying, and pasting of the coding snippets. It's a lukewarm place to be.

You're "learning" because you're making your way through structured content. But when you leave the tutorial, you can't code any of what you "learned".

The great thing is that you don't have to stay stuck in tutorial purgatory. I'm going to share with you my own experience about how I broke out of tutorial purgatory and how you can too.

Whatever method you decide to use, I'll share the key metrics for breaking out of the tutorial rut.

_Photo by [Unsplash](https://unsplash.com/@dchuck?utm_source=ghost&utm_medium=referral&utm_campaign=api-credit">Daniel Chekalov / Painful Realizations About My Learning Approach

When I first started learning how to code I looked forward to learning anything and everything.

I'd Google "easy programming projects" and browse the first few search results. I kept my eyes peeled for tutorials because I thought I could avoid failure with the tutorial's help. I also believed that the more tutorials I completed, the more I would learn.

I couldn't have been more incorrect in my learning approach.

The unfortunate aspect was that I wasn't retaining the knowledge of what I was coding. After several months of "completing" tutorials, I soon came to grips with my lack of progress. I couldn't understand the code I was writing.

An example of this was when I completed a Flask tutorial. I thought I knew and understand Python from completing a tutorial. I decided to take w3 school's Python quiz and was confident I would pass. Unfortunately, I failed.

After I discovered I wasn't learning what I thought I was, I felt pretty hopeless. I thought tutorials were the key to learning. I thought about trying projects without tutorial help, but I was too scared to fail. I was burning with desire to become a great programmer, but I was out of ideas for how to do that.

How I Broke Free from Tutorial Purgatory

_Photo by [Unsplash](https://unsplash.com/@pabloheimplatz?utm_source=ghost&utm_medium=referral&utm_campaign=api-credit">Pablo Heimplatz /

I sat and pondered answers to those two questions. I started researching different types of programming and various career paths. It was illuminating.

I found articles and forums on data science and analysis. I found helpful graphics that explained the difference between the front-end and back-end. I discovered how the front-end and back-end interact. I also found videos that explained what APIs were and how to view, receive, and write data from an API.

I would encourage you to ask the same questions:

What is it that you want to work on?

What type of programming is out there?

As you reflect on what it is you want to work on and explore, you'll begin to narrow down your learning path.

You'll feel less inclined to learn everything there is to know and more of what you are most interested in. You'll also feel less overwhelmed as you focus in on what type of programming interests you the most.

Meetups Changed My Life

_Photo by [Unsplash](https://unsplash.com/@windows?utm_source=ghost&utm_medium=referral&utm_campaign=api-credit">Windows /

This is What Freedom Feels Like

_Photo by [Unsplash](https://unsplash.com/@micahtindell?utm_source=ghost&utm_medium=referral&utm_campaign=api-credit">Micah Tindell / Meetup.com.

I would also encourage you to check out the r/learnprogramming subreddit. There are some snarky individuals on Reddit who may give you a hard time for asking questions. But there are also plenty of people who are more than willing to guide, inspire, and help you. If you allow them to, they'll help you become a better programmer.

Your Keys to Success When Learning to Code

_Photo by [Unsplash](https://unsplash.com/@mlightbody?utm_source=ghost&utm_medium=referral&utm_campaign=api-credit">Malcolm Lightbody /

Tutorial purgatory is a miserable place to be. You don't know if you're heading in the right direction and learning to program can feel hopeless.

But take heart, you don't have to stay stuck in tutorial purgatory. Keep asking questions! Distill your vision so that you're not overwhelmed with having to learn everything. You're heading in the right direction if you're producing results and feeling confident. Time to break out of tutorial purgatory and you'll thank yourself later.

How to Move from Coding Tutorials to Building Projects as a Developer

freeCodeCamp — Thu, 19 Dec 2019 17:00:00 +0000

By M. S. Farzan

Learning to code by following tutorials works for many people. And yet there tends to be a separate learning curve when you're trying to move out of the tutorial ecosystem and into creating your own projects.

I've written elsewhere about how to escape tutorial purgatory and make progress as a programmer. But to summarize here, it's a necessary step in your growth as a developer to venture out into the wild west of programming and build something. This will expose you to the ins and outs of your chosen coding ecosystem.

Here are five tips to help you move out of those tutorials and into making real progress as a developer by building projects.

1. Choose a Project

Whether you're coding from a book or working through online tutorials, your first step upon leaving the safety of your nest is to choose a project that is specific to your field of interest.

If you're an aspiring front end developer, that might mean creating a basic website. If you're learning Python, that could look like a simple web scraper. Find something that interests you, and research examples to get an idea of what your project might look like when it's complete.

2. Set Up an IDE

If you've been learning from online tutorials which provide a console that handles all of the back end work for you, take some time to set up an integrated development environment (IDE) that is specific to your intended project and ecosystem.

The actual form of your IDE will vary greatly depending on your project. You could be cobbling together a workflow that includes a code editor, command line interface, version control system, and package manager. Or, on the other hand, you might install a game engine that has all of the stuff that you need built-in for you.

The important component of this step is to become comfortable coding in an environment that is standard for the type of work you want to do. This helps you move away from only coding in a browser or following a book.

3. Get Comfortable with Documentation

Here's a glimpse of a familiar workflow when you're beginning a new project:

Set up your IDE
Code
Get stuck or forget the syntax for something
Google some half-formed question about the issue
Find the official documentation and a handful of Stack Overflow posts
Check social media for no reason
Return to the documentation and Stack Overflow to find your answer
Return to step 2

Unless you're a super expert in your field, chances are that you'll get stuck trying to figure out a solution to some aspect of your project. The official documentation for the library or framework that you're using will likely have some sort of answer - even if it's an obscure one - for whatever's puzzling you. But if it doesn't, someone has probably asked a similar question on Stack Overflow or elsewhere.

Even if there are no answers out there for your specific question, there will be a breadcrumb somewhere that'll lead you to an approach for how to solve your problem.

If you're trying to use ES6 classes in some obscure JavaScript framework, for example, you might not find the exact answer you're looking for. But there will be plenty of similar resources out there that can help you come up with a solution yourself.

4. Ask for Help

One of the best things you can do for yourself as an aspiring developer is to make friends with other developers in your field. They can look at your code and provide feedback about how to make it better.

For some people, the idea of sharing their work and having it critiqued is an anxiety-inducing experience. I recommend working as diligently as you can to overcome this emotion as it will stagnate your growth as a programmer.

When you're starting out with your own projects, it can be extremely helpful to have someone who's already walked the path to look at your work and offer constructive criticism. Even if doing so requires you to rewrite whole sections of code. In many cases, you might be trying to recreate the wheel while other options already exist. There, you'll benefit greatly from learning best practices from experts that have experience in the field.

5. Identify Other Areas for Growth

One project usually leads to another, and you'll quickly identify areas in which you're able to grow as a developer. This might mean that you'll move from front end development to back end, or vice versa, or hop from 2D game programming into 3D.

It might also mean that you need to keep building your skill set just to complete the initial project that you've chosen. There's no shame in learning C#, for example, then deciding to build the back end of a web app, and having to learn all about ASP.NET and Razor Pages before actually making any progress!

Happy coding!

If you enjoyed this article, please consider checking out my games and books, subscribing to my YouTube channel, or joining the Entromancy Discord.

M. S. Farzan, Ph.D. has written and worked for high-profile video game companies and editorial websites such as Electronic Arts, Perfect World Entertainment, Modus Games, and MMORPG.com, and has served as the Community Manager for games like Dungeons & Dragons Neverwinter and Mass Effect: Andromeda. He is the Creative Director and Lead Game Designer of Entromancy: A Cyberpunk Fantasy RPG and author of The Nightpath Trilogy. Find M. S. Farzan on Twitter @sominator.

How to Use GitHub and ES6 Features to Create and Structure Your Code

freeCodeCamp — Thu, 19 Dec 2019 17:00:00 +0000

By M. S. Farzan

If you're moving from coding tutorials into creating your own JavaScript projects, you'll want to become familiar with using a version control system like GitHub and benefiting from ES6 features to clean up your code and streamline your development process.

In this new video, we'll walk through cloning an existing repository from GitHub, creating your own local and remote repositories, utilizing node package manager (NPM) to install dependencies, creating a streamlined code base using ES6 classes, import/export modules, and arrow functions, and adding, committing, and pushing changes to GitHub.

Plus, we'll talk through the basic file structure for a Phaser 3 project!

Check it out (50 minute watch):

Happy coding!

If you enjoyed this article, please consider checking out my games and books, subscribing to my YouTube channel, or joining the Entromancy Discord.

How to Set Up an Integrated Development Environment (IDE)

freeCodeCamp — Sun, 17 Nov 2019 21:25:59 +0000

By M. S. Farzan

If you're moving from online tutorials to building your own projects, you might be overwhelmed by the idea of setting up your own integrated development environment (IDE), or wonder why you even need one to get your work done.

In this article, I'll discuss what an IDE is and give you some ideas about what yours might look like, particularly if you're working in JavaScript, although the information will be applicable irrespective of language or project type.

Here's a video version of this post if you'd prefer (28 minute watch):

What is an Integrated Development Environment?

An integrated development environment, put simply, is everything a programmer needs to get their work done. The actual makeup of an IDE will vary between programming languages, types of projects, and even between programmers, but there are some things that are common among a lot of IDEs, which I'll cover below.

The simplest way to understand an IDE is to consider an "all-in-one" solution like Unity. As a fully-featured game engine, Unity has everything you'll need to create a 2D or 3D game: a GUI that allows you to build your game world, a code editor (Visual Studio) where you can write scripts, a way to download dependencies and assets, and even GitHub integration so that you can keep track of build versions and collaborate on projects. For smaller projects, Unity can be thought of as a fully functional integrated development environment, where everything is already set up for you after downloading the game engine.

Other IDEs can vary greatly in complexity, particularly if you're coming from an online tutorial that allows you to code right in the browser. One of my gripes with common answers to the question, "what programming language should I learn?" is the notion that learning JavaScript is easier because "it just runs in your browser."

Tell that to anyone who's attempted to set up an IDE for Create React App, which requires several components to get up and running - none of which are apparent when you're working through online tutorials. To actually do work as a developer, you'll need four main things to set up your integrated development environment: a code editor, command line interface (CLI), version control system, and package manager.

Major caveat: your IDE may vary greatly depending on programming language or type of project, but you'll likely need one or more of the following in any case!

IDE Tool #1: Code Editor (and Compiler)

A whole bunch of online tutorials allow you to just code in the browser, which is great for understanding basic programming concepts, but in the long run, you'll need an editor that allows you to save your code (and compile it, if you're using a language like C# or C++).

There are a lot of code editors out there, such as Atom (lightweight, free, and open source), Sublime (super popular with tons of integrations), and Visual Studio / Visual Studio Code (supported by Microsoft and wonderful to work with). It would be reductive to say that they're "all the same thing," as each one provides a different approach to supporting your coding workflow, so you might try one or two before deciding which one you like best.

IDE Tool #2: Command Line Interface (CLI)

If you have a computer, you've undoubtedly used your file explorer or some other navigational GUI to access the file system, create folders, delete files, and so on.

The command line interface (CLI) allows you to do the same thing...in plain text. Which might seem super archaic or annoying at first, but once you wrap your head around chaining commands together and integrating them into your workflow, you'll begin to see the power of the CLI and how essential it is to most development environments.

On Mac, you might be using the Terminal. Because I've installed GitHub for Windows (more on GitHub below) on my machine, I use Git Bash for my work. There are several options here for you, and it might do to check out a few command line tutorials to understand some of the basic principles so that you feel comfortable using it in your IDE.

IDE Tool #3: Version Control System

There are several resources out there that provide overviews of what is version control and why you should use it. Suffice it to say that when you're building anything other than a simple project, you'll need a way to back up your work, share your code with collaborators, and keep track of the different build versions so that you can muck with parts of the code base and not others.

GitHub isn't the only version control system out there, but it is the gold standard at the moment, and it would be worth your while to look up a few tutorials to learn how to take advantage of its features, even if you just wind up using it as a remote backup method.

Additionally, while there are several addons to integrate GitHub right into your code editor (or game engine), the standard practice for doing Git-related tasks is by using the command line interface, which provides another reason for becoming proficient with your CLI of choice.

IDE Tool #4: Package Manager

For some IDEs, like with our Unity example above, all you need to do is download and install software to get started with building your projects. Most of the dependencies that you'll need will be included with your initial download, and if not, there will be a way to access them from within the game engine (e.g. Unity's Asset Store).

For other, more choose-your-own-adventure IDEs, you'll need to piece things together yourself, and one of the essential components will be a package manager like NPM or Conda.

Package managers do a lot of things, and at their most basic functionality, they'll help you to install all the dependencies you'll need to get your work done. If you want to get started on a React project, for example, you'll navigate to a folder through your CLI, and, after installing NPM (which is bundled with Node.js) type:

npx create-react-app my-app 
cd my-app 
npm start

The first line basically says: "Hey, NPM! Download all the dependencies for Create React App, and put them in a folder called 'my-app.'"

The second line then tells your CLI: "Navigate to the new directory called 'my-app.'"

The third line gets the action going: "NPM, it's me again. Start a development server that displays my project in a browser and updates it whenever I make changes to the code."

Once you've installed all of the necessary dependencies using your package manager, you'll begin working in your code editor and using the command line interface to make pull requests or push code to a remote repository using your version control system.

In summary, an integrated development environment comprises all of the things you need to get your work done, and varies based on language, project type, and your personal preference. Ordinarily, IDEs include a code editor (and compiler), command line interface, version control system, and package manager, but your integrated development environment might have different requirements or a combination thereof.

You can do it!

If you enjoyed this article, please consider checking out my games and books, subscribing to my YouTube channel, or joining the Entromancy Discord.

M. S. Farzan, Ph.D. has written and worked for high-profile video game companies and editorial websites such as Electronic Arts, Perfect World Entertainment, Modus Games, and MMORPG.com, and has served as the Community Manager for games like Dungeons & Dragons Neverwinter and Mass Effect: Andromeda. He is the Creative Director and Lead Game Designer of Entromancy: A Cyberpunk Fantasy RPG and author of The Nightpath Trilogy. Find M. S. Farzan on Twitter @sominator.

How to Choose a Programming Language and Escape Tutorial Purgatory

freeCodeCamp — Mon, 04 Nov 2019 20:45:53 +0000

By M. S. Farzan

A few weeks ago, I posted about my experience attempting to learn JavaScript, C#, Python, and more from Codecademy, Udemy, and freeCodeCamp, along with escaping from tutorial purgatory and actually making progress as a developer.

Deciding on a programming language can be extremely challenging and time-consuming as there are dozens of options out there, with a lot of conflicting information. In this article, I'll share some options based on my own experience learning to code, with suggestions for how to choose a programming language, escape tutorial purgatory, and make progress as a developer.

Here's a video version of this post if you'd prefer (11 minute watch):

Scenario #1: You Know What You Want to Build

Often, in articles such as these (or in the "What Coding Language Should I Learn?" infographics with which you're probably intimately familiar), you're asked to think critically about what you want to build after you've learned to code.

This approach is useful if you have some idea about what it is that you want to do with a programming language after learning it, but not so much if you just want to learn to code, as was my experience. I'll cover both scenarios in this article.

If you do know what direction you want to take your coding career after learning a programming language, you'll most likely have an easier time figuring out which language to learn first. Here are some suggestions in that case.

Front End Development: JavaScript (and HTML/CSS)

If you already know that you want to work on the "front end" of websites - meaning, anything the user sees when they come to a website - you should begin your coding journey with learning JavaScript. You'll probably start out by learning HTML and CSS, which form the backbone of just about every website, and then begin adding JavaScript to enhance functionality and interactivity to your sites.

JavaScript is fairly ubiquitous as a programming language, and has an easier on-ramp than other, lower level languages like C++. It's a great jumping-off point if you don't know what you want to learn...but more on that later.

Back End Development: Python, C#, or JavaScript (and SQL)

Let's say you're more interested in learning about the guts of websites, managing the "back end" and trying your hand at database administration. You've got a lot of options here, and the most straightforward path is Python, which is a beginner-friendly language that has mature frameworks (e.g. Django and Flask) for back end development.

You also can't go wrong with C#, which will expose you to Microsoft's .NET ecosystem and a programming language that, once you get into the weeds with it, is a pleasure with which to work. And if you're thinking of going "full stack" - meaning, you want to do front end and back end development - you might consider learning JavaScript, which has younger but highly prized back end frameworks like Express and Koa. Doing so will also ease your learning process as you'll be using the same language to code both stacks.

Whichever language you choose for back end development, you'll most likely also wind up adding SQL to your toolbox for database management, so put that on your radar.

2D Game Development: JavaScript or C

I've written elsewhere about what engine you should use to make 2D games, but here's the skinny.

There are a lot of 2D game engines, many of which may or may not suit your fancy as a game developer, and each with their own benefits, idiosyncrasies, and learning curve. Some of them, like Game Maker Studio 2, for example, utilize their own proprietary languages to run scripts, but I'd actually recommend you first learn JavaScript or C#, even if you're considering using a different game engine in the long run.

With JavaScript, you can use frameworks like Phaser to make 2D games, or fully-featured engines like Construct 3 (which actually uses drag-and-drop development with room for custom scripts). If you choose to learn C# instead, you'll work with Unity 2D, or perhaps MonoGame - but I'd actually recommend starting with non-engine tutorials (e.g. .NET)to get a good handle on the language first.

Learning JavaScript or C# will give you the foundational coding knowledge you'll need to tackle another game engine, like Game Maker, while also providing you with things like programming best practices and clean code organization.

3D Game Development: C# or C++

There are a lot of options for learning to code for 3D game development, and I'd suggest you start with C# or C++. In fact, unless you're super tech savvy or already have a background in programming, I'd recommend for you to start with C# and work your way down to C++. You'll have an easier learning curve and will learn fundamental programming concepts without having to deal with things like memory management and lower-level code.

You'll probably wind up learning both in any case, but if you start with C#, you can tinker around with Unity 3D, and then make your way to C++ with Unreal Engine 4.

Data Science/Machine Learning: Python

Although there are options in other languages for learning data science/analysis and machine learning, Python is currently the gold standard for this realm of coding. It's a fairly straightforward language to learn and will expose you to good programming habits and widely-used frameworks, so you can't go wrong here.

Scenario #2: You Don't Know What You Want to Build

There's the distinct possibility that you've spent days, weeks, or even months searching through articles, videos, reddit posts, and Stack Overflow questions reading about programming languages, and still have no idea where to invest your time because you don't know what you want to build.

I've been there. It's annoying.

My recommendation to you, trite as it may seem, is to just pick one. Literally any one of them, even if they're not listed here. Go learn JavaScript. Or Python. Or Rust. Or Haskell.

OK, maybe not Haskell. But pick something, and stick with it long enough to learn the basics and see if there's a possibility that you might like using that language to build with it. And keep in mind two things as you do so:

Set a time limit for yourself. Like, "I'm going to take the next three months to learn JavaScript using freeCodeCamp tutorials." If, at the end of that period, you feel like you're making progress and it's interesting to you, keep going! If not, it may be time to reconsider your choice of language and see if there's something out there that might be a better fit for you.
Build something that's not in your tutorials. This is a crucial step in your growth as a developer. I'll cover it in the next section.

Scenario #3: You're Stuck in Tutorial Purgatory

If you've found yourself doing tutorial after tutorial, on the same or different websites, without ever actually feeling like you're making progress, you may be really frustrated with the experience of learning to code. I've been there, and can help.

The first step is to consider what programming tutorials are good for, and what they are not. Most online tutorials - particularly ones that allow you to code right in the browser - are excellent for teaching you how to program.

They are not, on the other hand, good for teaching you how to be a programmer.

The best tutorials will expose you to fundamental coding concepts and require you to apply that knowledge to solve puzzles and projects. They're wonderful learning tools that can, if used beyond their scope, become crutches that will stifle your learning.

A programmer, for example, doesn't sit around all day doing tutorials. A programmer programs, and that's precisely what you need to do to make progress after you've mastered the basics.

The best way to make progress as a developer is to pick a project in your language of choice and set out to do it. If you're learning JavaScript, for example, you might choose to build a simple website with HTML/CSS and add some interactivity with jQuery. You'll probably start out by setting up an integrated development environment, immediately forgetting how to do something that you learned in your tutorials, get frustrated, head to Google, find the answer, and keep going. Then you'll make progress, get stuck, search Stack Overflow, scratch your head at the official documentation, maybe share your code with someone, and repeat the whole process.

And you'll be doing exactly what programmers do when building a new project.

Finally, you really can't go wrong with what programming language you choose, even if it's not on this list. If you wind up picking one, learning the basics, making a project, and deciding it's not for you, that experience will actually still help you in the long run. The information you'll learn in the process will be useful, irrespective of whatever language you end up using for your projects.

You can do it!

If you enjoyed this article, please consider checking out my games and books, subscribing to my YouTube channel, or joining the Entromancy Discord.

How I escaped from tutorial purgatory and learned to code - and how you can, too.

freeCodeCamp — Mon, 14 Oct 2019 18:00:00 +0000

By M. S. Farzan

Context: I'm a tabletop game developer and digital marketer, and, having spent a long time around games and computers, decided I wanted to learn to code about 3 years ago.

I set off as many do by searching, at great length, for what language I should learn, and where from, returning to this topic several times over the course of my journey. I came across several threads suggesting one language or learning platform over another, and thought to share my particular experience in case it's helpful for someone else in the same discernment process.

Disclaimer: I'm not a professional programmer, and although I am using my skills to benefit my work (you can read about my search for a prototype framework here), coding continues to be additive to my main work rather than a source of income, whatever that tells you.

Also disclaimer: I'm not attempting to position one language or learning platform over another, and I quite obviously haven't tried to learn every language out there, on every platform. The following is just my experience trying to figure out the most sensible way forward in an admittedly confusing environment.

You can also skip to the bottom for the TL;DR.

Prologue: C++

I'm not quite sure if I already knew that C++ was and continues to be a cornerstone in video game development. Maybe I saw it in one of those "What Programming Language Should I Learn" infographics that are around. But I wanted to know more about how games are made and how to talk to the computer. I'm pretty tech-friendly and have built or tinkered with my own PCs, thinking that might lend itself to the experience of learning how to code.

Holy smokes, was I way out of my depth. I did a few tutorials online (I think through learncpp or similar) and soon realized that I would need more guidance to understand basic object oriented programming principles, in perhaps a more readily accessible language, than I was finding in learning C++.

HTML, CSS, JavaScript, and Python

Before embarking on this adventure, I already had a little HTML experience, and came across Codecademy. I very much liked the ability to do tutorials from within the browser and without having to set up an IDE (doing so for C++ had been a trying experience). I quickly consumed all of Codecademy's lessons on HTML and CSS. The natural path from that point was to do the JavaScript course, which I enjoyed. But I soon found myself in "tutorial purgatory" (not my reference), working through the Python course and others.

I should also mention that I completed Codecademy's courses as a free user, not wanting to pay a subscription fee for what they were offering at the time, which included projects and mentor support.

I learned a lot of basics from Codecademy and general OOP principles, but didn't wind up applying much of it without a clear path forward. I returned to my search (who am I kidding, I've spent a LOT of time concurrently researching other languages, learning platforms, and bootcamps throughout the whole process) and decided I wanted to learn more about game development through courses on Unity.

C

I found Ben Tristem's Unity course on one of Udemy's perennial 10000% off sales, and worked diligently through the tutorials to build clones of 2D brick breaking and other games. I learned just enough C# to get by but not enough to feel confident in making anything myself.

Unity itself was probably more of a roadblock here than Tristrem and co.'s instruction, which was actually quite good. The Unity editor is a beast of an engine, with a lot of good tools that are impenetrable to a novice user (again, you can read more about my experience with Unity here).

I still feel like I learned a lot from the courses and the simple act of being exposed to C# and Unity's desired work flow, but wasn't getting enough out of the experience to continue. A friend of mine tipped me to take a look at freeCodeCamp, which is where I went next.

Back to JavaScript

On first blush, freeCodeCamp has the look of a less flashy Codecademy or Treehouse. But I liked how straightforward the tutorials were and didn't need to get past a paywall to make progress. I picked up where I left off with learning HTML and CSS, making good progress until I got to the Responsive Web Design projects that are required to finish the first section and receive a certification.

I can say with certainty that this was the moment (or series of moments) of my ejection from tutorial purgatory. For a novice with no real professional web design experience, and a willingness to figure out my own solutions without Googling the answer, the projects were hard. I eventually won out and made a couple of silly sites that satisfied the requirements, but the experience spurred me to work through several more freeCodeCamp tutorials on JavaScript front end libraries and back end frameworks.

More importantly, I started to work on my own web-related projects on CodePen and game projects using a bunch of different engines. I also started using Python to do some basic social analytics in my day job, and found it helpful.

Post-Tutorial Purgatory

Fast forward much time later, and I'm now working on several game-related projects in Phaser and Unity (most notably, a digital prototype for a tabletop card game I'm developing). I've spent a whole heck of a lot of time in framework documentation and Stack Overflow looking for answers and best practices for stuff (linking this post one more time for good measure). I also have developed friendships with a few colleagues who are themselves programmers, and it's been helpful to run code by them for advice and feedback.

One thing that's been helpful about working on my own projects is just the basic experience of setting up a workflow. Learning to use the command line and Git in concert with setting up NPM and a code editor, for example, was eye opening (particularly coming from CodePen, which just does everything for you). For better or worse, most tutorials don't expose you to the nit and grit of the tools that you'll need to get your work done, and there's a lot to be learned.

If you're reading this and looking for the "and I just got my first job as a programmer!" statement, I'm sorry to disappoint! That hasn't been my objective (at least thus far), but I do have some basic TL;DR learnings to share that may be helpful for anyone who's also on the search for a programming language or how to escape from tutorial purgatory.

TL;DR

JavaScript:

Pro: A very good entry point into learning object oriented programming, particularly if you're interested in any kind of web development (front or back end). You can learn this through most platforms, but my experience was best served by freeCodeCamp.
Con: Many sites will tell you that it "just runs in your browser" so you "don't have to set up an IDE" and is thus easier to learn, but this mindset will only take you so far. If you're going to do any meaningful development with popular JavaScript frameworks (React, Vue, Express, etc.), you'll wind up setting up something IDE-adjacent with a code editor, package manager, dependencies, etc., without the kind of support you'd get from, say, setting up .NET or similar.

Python:

Pro: Super friendly for newcomers if the curly braces in other languages are intimidating at first, and a good point of entry if you're interest in getting into back end programming or data science. I had a good initial onboarding experience through Codecademy.
Con: Your options are a little limited if you're looking to get into front end or game development. There are frameworks, for example, that allow you to make games (PyGame, for instance), but if you're specifically looking into game development, you'd be better served elsewhere.

C#:

Pro: A very pleasant language that's well-supported by Microsoft and the open source community. With it, you can do back end development, make desktop apps, create games (mostly with Unity but there are other engines like Monogame out there). It may be an unpopular opinion, but I'd recommend first learning C# through Microsoft tutorials or elsewhere and then learning Unity to ease some of the cognitive load imposed by the editor's complexity.
Con: Not much to speak of here, unless you really don't like Microsoft or really do want to work on front end web development (I suppose you could look into Blazor, but I wouldn't recommend starting here). I could speak volumes about how Unity can improve its user experience, for example, but C# itself is great.

General Thoughts on Learning and Escaping Tutorial Purgatory:

One of my frustrations in my process of asking the question "what programming language should I learn?" was what I felt was the insufficient answer of "well, what do you want to build?" I encountered this answer a lot, and don't think it's the right way of approaching learning how to program if you don't already know what you want to do with it. A beginner doesn't have enough context to know what they can build, let alone the route to get there (unless they're the type of person that just wants to make games or just wants to land a job as a web developer).
A better answer would be to say, "try a few tutorials on different sites and in different languages, and see if something strikes you as interesting. If it does, stick with it; if it doesn't, pick one at random and see where it takes you. The stuff you'll learn will help irrespective of what you actually wind up doing."
Additionally, if you can force yourself to get out of the tutorial ecosystem and just make anything outside of the protected environment that's been set up for you, it'll help teach you things you'll need to eventually know, such as setting up an IDE, searching for answers to questions, and sharing your work.

I hope this post is helpful for others out there who are searching for a programming language or a way to escape tutorial purgatory and build cool stuff. And I'd love to hear about your experiences, too!

If you enjoyed this article, please consider checking out my games and books, subscribing to my YouTube channel, or joining the Entromancy Discord.