• ExtraMedicated@lemmy.world
    link
    fedilink
    English
    arrow-up
    101
    ·
    1 year ago

    3 months ago:

    “Can you comfirm that each user account can have no more than one of these entities?”

    “Yes. Definitely.”


    Today:

    “Oh by the way, we have some users who need to have multiple entities. Can you fix it?”

    • jadero@programming.dev
      link
      fedilink
      arrow-up
      50
      ·
      1 year ago

      I eventually learned to never trust any restrictions on the user.

      I quickly learned to make sure everyone had a copy of decisions made, so that I could charge by the hour for changes. I eventually learned to include examples of what would and would not be possible in any specification or change order.

    • Kalash@feddit.ch
      link
      fedilink
      arrow-up
      31
      ·
      1 year ago

      I’m in the exact same boat right now.

      Also this change from 1:1 to 1:n entity was like one “minor” feature in a rather larger list of feature requests. It so far has caused more work then all the other features combined.

      • AggressivelyPassive@feddit.de
        link
        fedilink
        arrow-up
        18
        ·
        1 year ago

        And months later you’ll find out, that your change completely fucks over some internal optimizer statistic and causes the DB to turn into lava.

        I definitely don’t know that, because of several hour long outages and millions of lost revenue.

      • sip@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        this is ongoing now. Our “creators” were supposed to be “matched” for a “job” based on “skills”, not “skill”. pure chaos