> Start slow, build your foundation, learn your bits and bytes,
    > data structures and sorting algorithms first then venture out.

In my experience, the challenge for beginners is that they lose interest and make no progress at all, not that they take some suboptimal path.

It's like picking up a guitar. You can come up with the Perfect Five-Year Roadmap and preach about how someone should first learn music theory and proper form before taking a crack at it. But for most people, that's dull and they'd never learn guitar if they had to do that before jumping in and just trying.

I think beginners should optimize for doing anything at all, and nothing should be advised against as a suboptimal route. The optimal route is the one that compels them, even if it amounts to faking it til they make it with a game framework and devoting 75% of their time to things completely unrelated to programming.

Sorting algorithms? Bits and bytes? Seriously? I started dozing off during that sentence and I've been programming in some form for at least 10 years. That's not how you're going to woo most people into programming.

A visual feedback loop can be useful to those unfamiliar with computer concepts. Being able to think about complex algorithms with concrete examples (think graphics, physics, game state machines, dialogue scripting) can help reign in the abstract concepts.

Additionally, being exposed to multiple forms of art can be useful to find a creative outlet you may not have considered before e.g. music, art, writing, design.

That being said, I think making games is really hard. I think a lot of people want to make games and don't realize how difficult it really is. I think everyone should try it at least once.

I typically recommend Processing[0] to young hopefuls.

> Also engines like Unity provide a false sense of security when infact you have no idea what's going on behind the scene

And that's okay. Maybe that's a lesson that can only be taught the hard way. Maybe you care deeply about what is going on behind the scenes, maybe you couldn't care less.

Also, most successful games are not written from scratch. Unity and friends have had a staggering impact on the indie game industry. I wouldn't be surprised to learn that plenty of game developers have never used anything else.

I think the most important thing is that no matter what you do you should enjoy doing it. If you really want to make a game but you have no idea how to code, and you find it intimidating, maybe this is for you.

[0] https://processing.org/

Sure writing an entire game is a lot of work. But starting with the typical "print "Hello world"" then looping. Then text input. Then average 5 numbers = Students quit out of boredom.

Where as inside a game you get instant visual feedback. You start possibly with a simple exiting game and start modifying. Whether it's Pong or Breakout or a simple space shooter. All of those can teach the same core elements and yet the instant visual feedback means students are far less likely to be bored and far more likely to explore other ideas.

Similarly creative coding (processing, p5.js, etc.) often go the same way. The instant visual feedback leads to excitement and exploration for many more than the "learn these 100 foundational things before you can actually do anything interesting"

There are a lot of great learning opportunities for building a game without a graphics layer / engine. A new developer trying to build a Tic Tac Toe game in the terminal will be exposed to some challenging but not impossible challenges that will have a wide scale application.

Plus for many people, these types of games are already a familiar domain. For people new to coding I try to encourage them to build what they know. If that's a DOS-era blackjack game, it will be much more engaging to them than trudging page to page through an algorithms book.

Don't get me wrong the materials you listed in your last sentence have their application, but the sorting algorithm section of a learn programming book / video is (while useful!) less engaging for someone looking to get hooked on a new skill/hobby/career.

In fact, I would rate game programming as one of the most difficult software domains of all. I can't think of any other domain where you're immediately hit with the same level of algorithms, performance concerns, design questions, etc.

If you just want to do indie game dev, it's great, but it doesn't transfer and it teaches bad habits without the basis you mention in bits & bytes, data structures & algorithms.

While programming in general is highly abstract & often requires you to form a roughly analogous model of the situation in your head, game-dev programming usually involves you working directly on that model. It's very physical. Move this to that location, shrink those, animate the other, fade that out of existence. It's much easier to see the effect of your code in a game engine than through programming a sorting algorithm and logging the results to console.

For that reason, it's a great way to see if programming might be something you enjoy. It's not a great way to learn programming.

edit: apologies, I didn't see xyzzy_plugh's comment before making my own.

* Note that I'm a CodinGame employee, so my answer might be biased.

Thanks for the feedback :) It's really appreciated. Coding with friends is always more fun than learning to code alone, and if you want to onboard your friends onto programming, maybe you can also take a look at our "Clash of Code" category.

https://www.codingame.com/multiplayer/clashofcode

These are short coding "battles", from 5 to 10mins, where you can challenge your friends in small coding exercises (filter prime numbers, find how many ones there are in a binary representation, that sort of things). You can create private clashes and play together with your friends

    The best place to hire developers
    CodinGame for Work allows you to source, screen, and recruit bright and creative developers

Yes, especially doing things that are useful to you. This can be something very small. Many years ago, I needed to list filenames in a folder. (I had no idea of the command line). I knew some basic Python and I figured out how to do this.

Or I wrote a flashcard quiz test game to prepare for my history test in school (Javascript and HTML).

Or I wrote a small program to find rar or zip files on my computer that have also been extracted and now take up approx. double the space on the disk (the extracted version and the archive are both there).

Or some animations in Javascript to understand things we learned in physics class (harmonic oscillation and similar things). Small projects like that.

Or a program with GUI where I plotted some function we learned in math class about, with sliders to control some parameters of the function and see how the plot changes instantly.

I liked it so much that I enrolled in university to study computer science and I really liked the uni courses too, because I already understood how programming things is helpful in everyday life, it wasn't a dry abstract thing that you build for its own sake.