• GiorgioBoymoder [none/use name]@hexbear.net
    link
    fedilink
    English
    arrow-up
    39
    ·
    edit-2
    1 month ago

    it’s really fucking with me that neither axis follows a progressive ordering so I’m going to post a fixed (debugged) version. EDIT: lmao this is the most fucked up, inconsistent alignment chart I’ve seen. here it is fixed:

    everything -> sometimes -> nothing

    know -> not sure -> don’t know

  • autoexec@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    13
    ·
    1 month ago

    Where does “it used to work, but now it doesn’t, and I don’t understand how it could ever have worked” fit in?

  • TheDoctor [they/them]@hexbear.net
    link
    fedilink
    English
    arrow-up
    10
    ·
    1 month ago

    I helped a friend debug a script last week that was working inconsistently in really weird ways. I looked at the script and it was all event hooks littered with sleep calls. I told him he was basically fuzz testing his own script and then getting surprised when he found race conditions. Shit was wild. Also, sometimes getters in Python are a mistake.

    • ☆ Yσɠƚԋσʂ ☆OP
      link
      fedilink
      arrow-up
      7
      ·
      1 month ago

      I find setters/getters are generally an antipattern because they obfuscate behavior. When you access a field you know what it looks like, but if you pass it through some implicit transformation in a getter then you have to know what that was.

      • TheDoctor [they/them]@hexbear.net
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 month ago

        Yeah. I can understand the use case when it’s something relating to keeping simple state in sync by replacing it with derived state. But this particular case was flushing a cache after each get, which made each get of the property non-deterministic based on the class’s state.

    • jollyrogue
      link
      fedilink
      arrow-up
      4
      ·
      1 month ago

      Aren’t setters and getters discouraged in Python?

      I remember reading something like, “This isn’t C++ , and Python doesn’t have private vars. Just set the var directly.”

      • TheDoctor [they/them]@hexbear.net
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 month ago

        In the way that’s common in languages like Java where you’re making a property read-only, yes. But there’s a whole protocol in Python called descriptors where you can override the . on a field. The most common form of these is class methods annotated with the @property annotation, which makes it so the method can be accessed as if it were a property.

  • BlueMagaChud [any]@hexbear.net
    link
    fedilink
    English
    arrow-up
    7
    ·
    1 month ago

    the “sometimes works, don’t know why” is the most maddening, I love tearing my hair out just trying to get it to fail reliabily so I’ve got a single hint

    • ☆ Yσɠƚԋσʂ ☆OP
      link
      fedilink
      arrow-up
      8
      ·
      1 month ago

      Any problem that’s not repeatable is incredibly frustrating, and you’re rarely sure if you’ve truly fixed it in the end.

  • headerfile@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    4
    ·
    1 month ago

    i have so may questions; why are the top right and dead center duplicates? why do they have different images? why are the phrases inconsistent? why are the images and phrases distributed at random? how did you miss this?