zib

Thanks, friend, you too. And remember, best ideas win… unless you happen to know what you’re doing.

As a fellow Unity employee, I feel that right down to my bones. If the job market for software devs didn’t suck so hard, I would have left a while ago. Compartmentalization is the only coping mechanism I have to keep myself going.

Don’t forget the perk of forcing others to license the technology if they want to use it themselves.

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.

You misunderstand, we’re in the mirror universe.

I’m sure the Nintendo lawyers are furiously working on the C&D as we speak.

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.

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.

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.

Late 30s here and I beat that level for the first time very recently. My mind was blown when I learned that was not the final level of the game.

If anyone demands I implement some feature into one of my open source projects that I either don’t have time for or don’t want to do, my response is one of the following:

1. I’ll get to it when I can (if I actually care to do it)
2. You are welcome to implement it yourself and submit a PR
3. You are welcome to fork the project and do it yourself or convince someone else to do it

But thankfully, my projects don’t have a very wide audience, so requests/demands are rare.

Bobby Kotick keeps a close eye on all the girls at Blizzard.

Personally, I found Arch to be difficult to get installed. I’m ok with command line stuff once everything is all setup, but having to use it for the installation process is something I found to be too easy to screw up and too time consuming overall. Also, I haven’t seen any drop of vanilla Arch with a GUI installer. For the Arch experience, I generally go with EndeavourOS since it’s easy to install, gives you lots of options for the window manager, and is easy to use once you get it up and running.

If you’d prefer the Debian environment, I think anything from Debian or any of its derivatives (Ubuntu et al) would be a decent choice. My favorite is Linux Mint. I’ve seen a lot of people describe it like “entry-level” Linux, but it’s very capable and user friendly. It’s where I tend to spend most of my time when running Linux and I would say usually requires the least setup since it typically just works out of the box.

There’s also OpenSUSE Tumbleweed if you feel like going a somewhat different direction. I get more “traditional Linux” vibes from OpenSUSE, but packaged up in a user friendly manner. I play around with it from time to time in a VM, mostly when I want to test out some new server package locally. But, that said, it’s still capable of handling anything else I throw at it, so it’s fun to use all the same.

Indeed, and a lot of those low level peons think this new pricing structure is awful, but are being ignored by upper management.

I’m saying they didn’t think about it at all because it’s easier to blame users for misunderstanding than take responsibility for anything themselves.

Don’t get me wrong, the timing was fucking abysmal. They really should have thought about that ahead of time, but these executives rarely think about anything other than how to line their own pockets.

As much as I can’t stand John Riccitiello, anyone with RSUs will have vested stocks sold on a fixed schedule to cover taxes. They don’t get to choose when or how much is sold as long as they have their RSUs configured as sell to cover. The executives are no different in this regard, except they have a great deal more stocks than the average employee. However, this doesn’t absolve them of the awful new pricing structure. That shit should have been walked back before it ever left the planning stages.

I started out with blue switches years ago and they were obnoxiously loud, so I switched to reds and used those for a long time. Though, I kinda got tired of them and decided to give the Keychron banana switches a try several months ago and I’m absolutely loving them. They have a light tactile feeling, but they’re much quieter than Cherry browns. And a huge bonus is that Keychron keys are hotswappable, so if I get any bad keys or feel like switching to a new type, no having to deal with soldering to replace them.

This is really nice. I’ve been using Mint for years and didn’t know about it.