• Shayeta@feddit.org
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    2
    ·
    9 days ago

    Clarifying requirements, designing architecture. Also, I dont understand how is someone supposed to be able to “parse code” without being able to write it? It’s like being able to read but unable to write.

      • Upgrayedd1776@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        ·
        9 days ago

        ditto, similar to the way Severence gets a sense of whats off, i cna do that with code, ask me to start from scratch i would not know where to start. Give me google, i will have a bunch of a copy pasta that works in the end, claude does the research, evaluation, best practices and review and testing and re-review and testing, when the Developers department will go to war with you if you put a Slack question through the wrong channel

      • ragas@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        8 days ago

        So really what you do is guess what the code you read is doing. Which is generally fine.

        But how can you be sure in a review that the code will actually work? How can you falsify it? A review is more than just reading code.

    • [deleted]@piefed.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      9 days ago

      I understand cooking concepts and can tell when something I am familiar with is made well. If I watch a cook, most of the time I can tell why they do certain things anand how it impacts the food.

      My cooking skills are very limited, especially when it comes to making new things. My sql skills are the same, I can read through the code and spot errors that match issues, but even creating something new is fairly limited despite being able to read and comprehend what has already been done.