• 0 Posts
  • 142 Comments
Joined 2 years ago
cake
Cake day: November 23rd, 2023

help-circle
  • Auditing the code it produces is basically the only effective way to use coding LLMs at this point.

    You’re basically playing the role of senior dev code reviewing and editing a junior dev’s code, except in this case the junior dev randomly writes an amalgamation of mostly valid, extremely wonky, and/or complete bullshit code. It has no concept of best practices, or fitness for purpose, or anything you’d expect a junior dev to learn as they gain experience.

    Now given the above, you might ask yourself: “Self, what if I myself don’t have the skills or experience of a senior dev?” This is where vibe coding gets sketchy or downright dangerous: if you don’t notice the problems in generated code, you’re doomed to fail sooner or later. If you’re lucky, you end up having to do a big refactoring when you realize the code is brittle. If you’re unlucky, your backend is compromised and your CTO is having to decide whether to pay off the ransomware demands or just take a chance on restoring the latest backup.

    If you’re just trying to slap together a quick and dirty proof of concept or bang out a one-shot script to accomplish a task, it’s fairly useful. If you’re trying to implement anything moderately complex or that you intend to support for months/years, you’re better off just writing it yourself as you’ll end up with something stylistically cohesive and more easily maintainable.


  • As someone who has been shoved in the direction of using AI for coding by my superiors, that’s been my experience as well. It’s fine at cranking out stackoverflow-level code regurgitation and mostly connecting things in a sane way if the concept is simple enough. The real breakthrough would be if the corrections you make would persist longer than a turn or two. As soon as your “fix-it prompt” is out of the context window, you’re effectively back to square one. If you’re expecting it to “learn” you’re gonna have a bad time. If you’re not constantly double checking its output, you’re gonna have a bad time.


  • Yes, if you’re going to run TrueNAS (or another solution based on ZFS) you should really get rid of the PERC and get an LSI SAS card in IT mode so that the system can see the raw disks.

    When you start your SATA swap, either use the onboard SATA ports (if there are enough) or get a SATA card (more ports, probably slightly better performance than sharing the onboard controller) and start the process I described before.


  • Yes, you’re going to want to get SATA drives that are the same size or bigger than your SAS drives. The mini-sas will break out into 4x sas connectors but you don’t have to swap 4 at a time; disconnect one SAS drive from the SAS breakout cable and then connect one replacement SATA drive to the SATA backplane (either the one on your motherboard or to a SATA card if you don’t have enough mobo ports). Do a zfs scrub. Once it’s finished with no errors, repeat all three steps. Once all drives are off the SAS card and your final scrub is done you can remove the SAS card entirely.


  • felbane@lemmy.worldtoSelfhosted@lemmy.worldAm i cooked? SAS or SATA
    link
    fedilink
    English
    arrow-up
    11
    ·
    edit-2
    2 days ago

    For this use case there’s not really an advantage using SAS over SATA. I’d suggest buying SATA drives in the future just because you don’t need a SAS card for them, and SATA drives are usually cheaper.

    If you use the H700 for hardware RAID and switch to SATA later, your best bet is probably to copy the data over (or better, use the opportunity to test your backup/restore process).

    If you could run the SAS disks in JBOD mode (which is possible if you sell the H700 and use another SAS card), you could set up your drives in a RAIDZ1 mode and later switch to SATA drives by replacing one drive at a time and doing a scrub between each swap.