zib

When I have no choice but to interact with people, I do my best to treat them with respect. However, I would say I'm generally ambivalent toward people overall and do my best to avoid them. I'm just not a social person and I never will be. Being forced into social settings is exceptionally stressful to me.

Listen, give him a break. That one brain cell can do only so much.

We get to have a little dictatorship as a treat.

I hate riding my bike in the street for exactly this reason. I really shouldn't be of the mindset that every time I get on my bike could be my last.

Good point, that is a valid way to do it sometimes, but it's extremely situational and trying to do that for everything would be absolute nonsense.

That was my thinking. A friend of mine has had a Polestar 2 for about a year now and absolutely loves it. Hasn't had a single problem with it. Like with conventional vehicles, some brands are just shit for quality and others are great.

I can understand telling you not to use break and continue if the point is to teach you to think about different ways to solve problems, but saying it's because "it makes the code harder to read" is bullshit. Readable code flow is important, but if using those makes your code too hard to read, your problem is most likely that you've just written shitty code.

To get really into the technical weeds, what break and continue boil down to in the compiled machine code is a non-conditional branch instruction. This is just going to move the execution pointer to a different location in memory. Other keywords, such as if, elif, and else, will compile down to conditional branch instructions. Basically the same thing, but they have the added cost of having to evaluate some data to see if the branch should happen at all. You can achieve the same things with both, but the high level code might need to look different.

For instance, if you're in a loop, continue will let you skip the rest of the code in the loop to get to the next iteration. Not a huge deal to instead make the entire code block conditional to skip it. However, the break keyword will let you exit the loop at any point, which is more complicated to deal with. You would have to conditionalize your code block and force the looping condition to something that would stop it on the next iteration. If you ask me, that has the potential to be much more complicated than necessary.

Also, good luck using switch without any breaks, but I'm guessing that's not quite what your teacher had in mind.

In short, just go with it for now. Be creative and find a way to make it work to your teacher's liking, but always try to be aware of different ways you can accomplish a task. Also, I don't know what language you're using, but if you're in C/C++ or C# and you feel like getting really cheeky, it doesn't sound like she disallowed the use of goto. It's kinda like break with fewer safeguards, so it's super easy to write broken code with it.

That's it exactly. In addition to over-hiring during COVID, the massive spending spree from a ton of over-inflated, short-sighted acquisitions ever since the IPO absolutely demolished the company's budget. Cutting Weta Digital was only the tip of this latest iceberg.

Damn near everything in Nier Gestalt/Replicant. That game wrecks me every time I play it.

Me, an American, looking at 17: "You guys get to live 21 days per year?"

Listen, I built enough lego bridges back in the day to know I ain't trusting that.