zib

No idea, but it wouldn't surprise me. The corporations are basically the modern gods of Japan.

In my case, I use a PCI card with an m.2 slot for my OS drive. I lose a PCI slot, but I already had a few to spare.

I use a 1tb ssd for the os/apps with my raid5 strictly for storage. Kinda nice if the os needs to be reinstalled or I want to migrate the raid cluster.

As mentioned by others, he "retired" a few months ago, but he's not the only one at fault. Many of the other executives contributed to the terrible decision making that landed the company in its current situation and they need to be cut loose as well.

“There is not a lot of history of laziness being rewarded with success. Hard work is an essential ingredient in any recipe for success.”

Says the corporate executive whose success is measured entirely by the hard work of others.

Millennial here and I've had a similar experience. I ate a ton of red meat growing up, but once I got to my early-to-mid 30s, I noticed beef would give me a lot of stomach issues. I switched to eating chicken and sometimes (depending on the dish) substituting the meat entirely for black beans and found my stomach issues got a lot better. And it's still just as tasty to me, so I don't feel like I'm missing out on anything.

Maybe you should think a little more about the shareholders and little less about yourself. /s

We get to have a little dictatorship as a treat.

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.

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