Six hundred bucks, PLUS $70-$156/year??? For a shit camera? That’s insane…

Pretty!

No, the difference is just that spots on the hood don’t tend to grow much, especially if they’ve been covered with touch up paint. The most common parts of a car to rust is anything on the underbody, and I’d say the most common body panels to rust are right near the fenders usually because that’s where rocks get kicked up, break through the paint, and when water sits in there it rusts. Super common, just a fact of life.

As one commenter said, triangles are good. They’re very good at handling loads. Other than that, the best way to learn how to design and woodwork better is to just get out and do it! You’ll learn more as you go.

The paint should act as the sealer as long as you touch it up if it ever gets knocked off again. Little rust spots on what I assume to be the hood or front of your car are really a non-issue, corrosion-wise. But that said, are these just small spots on body panels, or are they spots near wheel wells or something where water tends to collect?

If the drive turns on, it’s fine. Any damage that’s enough to break a hard drive will make it very clear very quickly. The only thing you’d really risk would be misalignment of the platters, which again, would show itself pretty much instantaneously. Drives are shipped with their heads in a parked position and in specially-designed packaging specifically to avoid these types of instances.

So for padding, it sometimes depends on how your compiler works, but usually, it doesn’t pack bytes by default - that needs to manually be done. Otherwise, a uint32 followed by 2 uint16s, for example, will take up the space for 3 uint32s (in a 32-bit native compiler). If you manually specify packing (implemented differently depending on your compiler and such), then it will pack those all properly into just 2 uint32s.

I do imagine 24 bits followed by 16 more in a bit field for a 32-bit number would potentially cause problems. But it’s late here and I could certainly be wrong so take that with a grain of salt.

That also said, I typically don’t use bitfields directly in structures - it’s not usually good practice, at least where I work. I’d either do a uint8[3] or use a whole uint32 that is a union, and in the union would be your :24 followed by a reserved : 8, if that makes any sense. It’s sometimes worth it to leave a few extra bytes in there just from an organization standpoint.

Worked for me; I can see it fine

Just note that if you 3D print something, if you use the wrong material, there’s a chance it may melt.

Out of curiosity, what’s wrong with medium? (Serious question)

Must be part of Reddit’s new rebrand

Great explanation. Yes - I’ve done this before! Built up a system with a RAID array but then realized I wanted a different boot drive. Didn’t really want to wait for dual 15Tb arrays to rebuild - and luckily for me, I didn’t have to! Because the metadata is saved on the discs themselves. If I had to guess (I could be wrong though) - I believe ‘sudo mdadm —scan —examine’ should probably bring up some info about the discs, or something similar to that command.

It kinda looks like a marigold to me. If the leaves are crunchy, it’s underwatered. There’s a chance that some of it is still alive so you may see some small growth start to pop up - but usually, everything that’s crunchy is totally dead. If it’s mushy or limp, it’s underwatered - which unfortunately is probably worse.

Is it a hardware raid or a software raid? If it’s software (not sure abt hardware), the discs themselves should have the array’s metadata on it, and you can just use mdraid & restart the array.

Congrats! Looking wonderful :)

I do like that idea. I think Apollo (or one of the Reddit apps) had something that expanded the hit box on links to prevent that as well - that could potentially be useful, too.

I wouldn’t say to disable it - but if there was an option to toggle on/off somewhere, that would be awesome.

I’d personally be super surprised if they were outsourcing their firmware engineering - but I do suppose it’s technically possible.

Ahh, yeah. Neither would I. I would expect my USB sticks to last longer than that, lol.

That aside - here’s a fun fact. We sell the NAND from scrapped SSDs that we no longer need for development to a third-party vendor that actually desolders it and uses it for flash drives. So… you never really know what kinda flash storage you get on your flash drives! (Or… we did do this, until the program recently got shuttered because NAND is so damn cheap now)

I do agree with the plastic brick part - but there is actually reasoning behind that second part - the read-only mode. That happens when the flash is down to a very low amount of life left (usually predetermined by the manufacturer). It is by design because the flash will degrade further if you continue to write to it, so by forcing it to read-only mode, users can still recover their data in a failing/aging SSD. Not to say it isn’t a huge pain in the ass when that happens though, lol