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

    All of the worst programmers I have worked with do that exact thing and refuse to acknowledge that they might have misunderstood what was said.

    The good ones ask for clarification when something sounds weird.

    • Siethron@lemmy.world
      link
      fedilink
      English
      arrow-up
      47
      ·
      2 days ago

      As a programmer working support. I often ask users for clarification on how they expect things to work, and they often make me imagine a dog going “no take only throw” by saying ‘i don’t know just fix it.’

    • idunnololz@lemmy.world
      link
      fedilink
      English
      arrow-up
      15
      ·
      edit-2
      2 days ago

      Early on in my career I’ve wasted time on projects implementing the wrong thing a few times so ever since I clarify to a fault even if it doesn’t sound weird. If something can be interpreted multiple ways I always ask for clarification even if one interpretation is “more popular”. I’d rather spend 5 minutes asking for clarification than waste a week of everyone’s time.

      Since then I don’t think I’ve ever implemented something “wrong”. There might be miscommunications in other parts of the communication chain but never with me.