I’d have to subtly disagree with this. It is really good advice, especially when the scope of your game is larger than what one could reasonably finish in a game jam; If you can’t get to a fun game in a couple of days or less, you need documentation as to what your plan is to get there.

The problem is that this is the best advice for someone who has the technical “hard” skills to make a game (compsci, digital art, etc.), but lacks the "soft"er skills (software eng., scheduling, etc). To be fair that is super common, but the OP implies to me they’re not confident that they have the technical skills either yet.

Without either of those skills you can’t know what’ll take a couple of days or what’s actually weeks of work, and the value you get out of design docs becomes effectively random.

The common advice that I’d have to agree with is that your first few games should be as small of a scope as you can make them. Other comments to this post already go into detail, but the jist is that when you’re starting the amount you learn is more per-project than per-hour, so get out as many small things as possible to get your bearings.

Once you’ve done that, this is really good advice for your first sizeable project.

But then I’ll never sleep

Ok this may sound insane but trangle cut sandwiches definitely taste different than square cut. 3 holed donuts obviously won’t but at least with sandwitches it changes how much of the crust vs everything else you taste.

My understanding is that leaves contain some compound(s) that, when wet and under the extremely high pressures that train wheels provide, becomes one of the most effective lubricants we know about. In other words, the brakes literally won’t do anything because you’ll slip-n-slide your way at the same speed you were going before.

As someone who’s used both, I’d have a strong preference for Odin over Rust if it were at a stable 1.0 release. As it stands now (or, at least, when I used it), Odin is very much in flux. Spend enough time with the language, and you’ll either find a bug with the compiler or the semantics will change after you update.

That said, it would be my favorite without those problems. It is a really simple language in a good way. There’s no fancy language features that are just syntax sugar (well except maybe context, but I find that to be actually convenient). You can understand everything in an afternoon if you are already familiar with programming in other languages. Rust is pretty much the opposite in all of these reguards.

Rust also has the benefit of being pretty recognizable at this point, so if you say your project is in Rust then people will know what that means, unlike Odin. More “resume-able” in a way.

So, in short:

• Odin if you’re doing it as a hobby
• Rust if you want something “real”

While I do agree that math gets much easier with interest, and that it gets more interesting the further you get into it, and that math is inherently beautiful, etc. I feel this argument has to fall flat to people who don’t already agree. It’s the education equivalent of when someone says they couldn’t get into an anime and then the fans tell them ‘oh it gets really good around season 9’. You could be completely correct, as you are here, but it’s utterly unconvincing if you don’t already “know.”

To be fair, I think this is mostly a problem with math curricula. Math classes up through high school and early college seem to focus on well trodden solutions to boring problems, and at some (far too late) point it flips around to being creative solutions to interesting problems. I think this could be fixed eventually, but such is the system we have now.

The thing that finally got businesses to finally get off IE wasn’t from the browser being worse than every other option. Heck, it wasn’t even because it was a decrepit piece of software that lost it’s former market dominance (and if anything businesses see that as a positive, not a negative).

What finally did that was microsoft saying there won’t be any security updates. That’s what finally got them off their ass; subtly threatening them with data breaches, exploits, etc. if they continue to use it. I don’t see google doing this anytime soon, at least not without a “sequel” like microsoft had with edge.