Toasting to the new year?

I didn’t say I think it’s a good thing, just that the truck guy probably think it is.

It’s supposed to be a good thing. I don’t get the context of the stickers either unless it’s just supposed to be a useless explanation of the situation.

Imma leave this here since they put it quite nicely. https://lemmy.sdf.org/comment/6818226

Also, just read their username and you’ll see it’s clearly exactly what we all think it is.

This is a good tool for visualizing your raid needs from your capacity and total number of drives.

https://www.seagate.com/products/nas-drives/raid-calculator/

I’ll preface that I’m no raid expert, just a nerd that uses it occasionally.

The main benefit of most raid configurations is the redundancy they provide. If you lose one drive, you do not lose any data. It’s kinda obvious how you can have 1:1 redundancy, you just have an exact copy of the drive. But there are ways to split data into three chunks so that you can rebuild the data from any two chunks, and 5 chunks so that you can loose and two chunks. Truly understand how raid does this could easily be an entire college course.

Raid 0 is the exception. All it does is “join together” a bunch of drives into one disk. And if you lose an individual disk you likely will lose most of your data.

Another big difference is read/write speed. From my understanding, every raid configuration is slower to read and write than if you were using a single drive. Each raid configuration is varying levels of slower than the “base speed”

I typically use raid 5 or 6, since that gives some redundancy, but I can keep most of my total storage space.

The main thing in all of this is to keep an eye on drive health. If you lose more drives than your array can handle, all of your data is gone. From my understanding, there is no easy way to get the data off a broken raid array.

I’ve literally never heard GUI said as “gee ewe eye” before.

You could just say UI, avoids the gooey phobia and sounds less weird than g u i.

I think those make sense as deviations. I’ve heard “my sequel” but you’re absolutely right about postgresql.

The name is kinda irrelevant like hard vs soft g in gif. People know what you mean when you say either.

But in that same vein, the creator of the “graphics interchange format” says the pronunciation is soft g, but basically everyone says hard g… So “official” pronunciation is kinda irrelevant.

I don’t judge anyone who uses whichever term they want, but I’ve just noticed the general trend in my smallish interaction bubble.

The only people I know who actually call it ess queue ell are either too new to know the “sequel” pronunciation, or the type of person you generally smell before you see.

It was a bad pun on “parallel”

I’d guess it’s beside the others.

C# is .Net though. It’s only syntax without it.

I think it’s definitely a dig at windows, because that used to be the primary issue with c#, you could only really target windows and you could only write it using windows. You could run .net framework applications on Linux, but it was a lot of work and it really underperformed (which would fit the timeline of 2015, when this comic was first posted). Now with .net core you can make a self contained executable that can run on anything.

You absolutely can ask it for code you plan to use as long as you treat chatgpt like a beginner dev. Give it a small, very simple, self contained task and test it thoroughly.

Also, you can write unit tests while being quite unfamiliar with the syntax. For example, you could write a unit test for a function which utilizes a switch statement, without using a switch statement to test it. There’s a whole sect of “test driven development” where this kind of development would probably work pretty well.

I’ll agree that if you can’t test a piece of code, you have no business writing in the language in a professional capacity.

People who are annoyed by types have never had to spend weeks of their life hunting for a missing property on an object.

Compilation errors are so much more preferable than finding out the same error at runtime.

Bad/wrong documentation is worse than no documentation.

“Practice makes perfect” is only true if you’re practicing the right stuff. Otherwise you’re just reinforcing bad habits.

I love how you chose the middle ground. Clearly there is no other option between people deciding to not use fireworks in a city and another lockdown.