Comment on Hours of work

ExtraMedicated@lemmy.world ⁨1⁩ ⁨year⁩ ago

• jadero@programming.dev ⁨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.

  source
• theKalash@feddit.ch ⁨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.

  source

  • agressivelyPassive@feddit.de ⁨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.

    source
  • FuntyMcCraiger@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

    Or worse, it was an n:1 and they want it n:n

    source
• sphericth0r@kbin.social ⁨1⁩ ⁨year⁩ ago

  Even worse, they'll claim it was a bug

  source

  • sip@programming.dev ⁨1⁩ ⁨year⁩ ago

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

    source
• eluvatar@programming.dev ⁨1⁩ ⁨year⁩ ago

  Oof

  source