It took me hours to realize why this game is so much more frustrating than it seemed like it should be. I've written assembly programs before. I didn't realize at first why I was writing duplicate code so much more often than I do when actually programming. But I've figured it out about 4/5ths into the game.
There's no jump return. This is an absolute killer when it comes to what programmers like doing - cutting problems into parts and isolating each part in it's own method.
In this game, if you section off code for a specific purpose, there's no way to return to where you called the method. So you can't call a method from multiple places outside specific circumstances. Which means you're forced to write duplicate code over and over, which is both tedious and feels wrong because normally that's a warning sign that you're writing bad code.
This is all frustrating because actually solving the puzzles is fun, and turtle programming, assembly, and multithreading is a combination you'll probably never encounter outside this game, which means these are all puzzles you've never seen before, but that missing jump return means actually implementing your solution is a chore nearly every single time.

Plot wise, I didn't finish it, but this is obviously weaker than, for example, world of goo in that aspect, for one major reason. In world of goo, you are very involved in the story during gameplay. Lots of the levels feature plot taking place as you solve the level (most of the chapter finales, for example). In 7 billion humans, the story of the game and the levels are completely isolated.

It took me hours to realize why this game is so much more frustrating than it seemed like it should be. I've written assembly programs before. I didn't realize at first why I was writing duplicate code so much more often than I do when actually programming. But I've figured it out about 4/5ths into the game. There's no jump return. This is an absolute killer when it comes to what programmers like doing - cutting problems into parts and isolating each part in it's own method. In this game, if you section off code for a specific purpose, there's no way to return to where you called the method. So you can't call a method from multiple places outside specific circumstances. Which means you're forced to write duplicate code over and over, which is both tedious and feels wrong because normally that's a warning sign that you're writing bad code. This is all frustrating because actually solving the puzzles is fun, and turtle programming, assembly, and multithreading is a combination you'll probably never encounter outside this game, which means these are all puzzles you've never seen before, but that missing jump return means actually implementing your solution is a chore nearly every single time. Plot wise, I didn't finish it, but this is obviously weaker than, for example, world of goo in that aspect, for one major reason. In world of goo, you are very involved in the story during gameplay. Lots of the levels feature plot taking place as you solve the level (most of the chapter finales, for example). In 7 billion humans, the story of the game and the levels are completely isolated.