• CaptDust@sh.itjust.works
    link
    fedilink
    arrow-up
    1
    ·
    3 months ago

    Returning and finding everything done is equally suspicious. That’s when you have to take a closer look and discover what spaghetti made it through peer review.

  • LavenderDay3544@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    3 months ago

    This is the result of so called tribal knowledge in software development. It’s even worse when the senior citizen who understands everything retires, goes senile, or dies.

  • molave@reddthat.com
    link
    fedilink
    arrow-up
    1
    ·
    3 months ago

    Maybe, part of your job is to not touch anything in a random day and observe what happens when something breaks. That way, you can document what’s not being fixed so that your team is more prepared when you’re actually not there.

  • count_dongulus@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    3 months ago

    Sometimes I am happy about the increase in AI assisted coding specifically so junior devs won’t get as stuck without outside help. Very frustrating when they don’t reach out when they struggle, but at least they can privately copypaste into ChatGPT and get ideas. But, still requires a fine toothed comb when you’re doing the review to know if any toilet tier material sprayed out.