• 0 Posts
  • 474 Comments
Joined 3 years ago
cake
Cake day: June 30th, 2023

help-circle















  • To each their own but ours didn’t really require more than an hour a month at most. It’s not running on cutting Edge hardware but chugs along pretty dependably. The back ups probably take the most time but even then ansible does most of the work and we bump the omnibus version once a month in off hours without issue.


  • It’s reliability was already not super great before the vibe coding hit.

    It’s mostly caused by them trying to migrate complicated legacy systems to azure. This type of work is already fraught with danger.

    The vibe code just supercharges an already risky endeavor. The LLM code could be perfectly correct but the more dynamic a complicated system the more difficult it becomes to judge side effects of any one change.

    The speed of change also means that experts in particular areas of the code base may find their mental model of the system to be out of date and incorrect faster than ever before. This is course also leads to the increased chance of mistakes or unintended side effects.


  • tempest@lemmy.catoProgrammer Humor@programming.devgithubDownDaily
    link
    fedilink
    arrow-up
    34
    arrow-down
    1
    ·
    13 days ago

    I mean there are tons of options in that space so if it’s an issue that is sorta on your business to have evaluated their dependency.

    We work on an internal gitlab instance that has had 100 percent up time for like 2 years. It doesn’t even have to be gitlab, there’s gitea and like 10 other options.

    I personally think that the industry has moved so far in the direction of cloud and saas that it’s lost a lot of valuable skills and made them dependent on too much externally.