• JasonDJ@lemmy.zip
    link
    fedilink
    English
    arrow-up
    21
    ·
    edit-2
    1 day ago

    Probably performs a good burn-in for them too.

    Do people still do that? Used to be common practice to power on equipment and let it sit, either idle or full-tilt, for a couple days before even starting to configure it. Let the factory bugs scatter out.

      • Dozzi92@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        19 hours ago

        My parents bought a beach house (a bungalow on a postage stamp, before anyone gets an ideas that we’re some 1%ers) and it came with an old washer dryer. My old man put a single pair of jeans in the dryer and seemingly forgot about them. He says he did it for a timer. Leaves the house. Nobody there for a week. My mom comes in, dryer still running, jeans essentially translucent at this point. One of the things you can laugh at only because it wasn’t a tragedy.

    • AtariDump@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      19 hours ago

      I do; I use a four pass destructive run of badblocks on new drives before implementing them.

      • sugar_in_your_tea@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 hour ago

        Yeah, we did that at my last company to make sure our hardware was up to spec. We deployed an IOT device for long term outdoor installations, so it needed to survive very hot temps. We had a refrigerator we gutted and added heat to, and we’d run a simulation with heavier than expected load for a couple days and tossed/RMAd the bad units.

        That was a literal burn in, but the same concept ak applies to pretty much everything. If you build/buy a PC, test the hardware (prime95 CPU test, memtest for RAM, etc). Put it through its paces to work out the major bugs before relying on it so you don’t have to RMA a production system.