Hours of work

Comments

• ExtraMedicated@lemmy.world ⁨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?”

  source

  • 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
• BearJCC@lemmy.sdf.org ⁨1⁩ ⁨year⁩ ago

  Jokes on them I charge by the hour

  source

  • jet@hackertalks.com ⁨1⁩ ⁨year⁩ ago

    I was about to say. Rejoice! If this is a client these are billable hours

    source

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

      yea, but it stops being fun when they say it’s a bug and it’s always supposed to work like that.

      source

      • -> View More Comments
• bob_wiley@lemmy.world ⁨1⁩ ⁨year⁩ ago

  [deleted]

  source

  • RagnarokOnline@reddthat.com ⁨1⁩ ⁨year⁩ ago

    “When you do things the right way, people won’t be sure you’ve done anything at all.”

    source
  • agressivelyPassive@feddit.de ⁨1⁩ ⁨year⁩ ago

    That’s why you get everything in writing. No change without detailed description of what you’re doing and a written reply stating that yes, this is what they want. Otherwise you’ll be in a constant refactoring treadmill.

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

  It’s a good thing I’m a hobbyist so that I can avoi- hmm, now that I think about it this feature could be really cool and shouldn’t take too long to implement…

  source

  • queque31@lemmy.world ⁨1⁩ ⁨year⁩ ago

    2am me: why the fuck this doesn’t work anymore!!!

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

  If you do this enough you know how to design your solutions to be relatively flexible. At least for your backends.

  Your frontend will always churn, that’s the nature of the job.

  source

  • vivadanang@lemm.ee ⁨1⁩ ⁨year⁩ ago

    Your frontend will always churn, that’s the nature of the job.

    Yep. The trick is to be gone before anyone finds the gross stuff needed to make it all work.

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

  Bro that’s just Tuesday

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

  I just had to rewrite all my code for 3rd time in a row and I am the customer. Ughhhh

  source

  • ripened_avacado@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Twitter API user found.

    source

    • Immersive_Matthew@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

      I mean I am the one causing myself to have to rewrite my code. I am developing a VR Theme Park.

      source
• jadegear@lemm.ee ⁨1⁩ ⁨year⁩ ago

  Sounds like job security to me.

  source
• idunnololz@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Jokes on you, I like refactoring code.

  source

  • deadbeef79000@lemmy.nz ⁨1⁩ ⁨year⁩ ago

    Refactoring is healthy for code.

    This is a good thing!

    source
• peopleproblems@lemmy.world ⁨1⁩ ⁨year⁩ ago

  3 years and $5m down the drain for something we just got in production this year.

  Could have been worse?

  source
• Feathercrown@lemmy.world ⁨1⁩ ⁨year⁩ ago

  I pretend I do not see it

  source
• Duke_Nukem_1990@feddit.de ⁨1⁩ ⁨year⁩ ago

  Thats what end of life-ing your products is for 😎

  source

  • Jerkface@lemmy.world ⁨1⁩ ⁨year⁩ ago

    How about end of life-ing your client?

    source

    • bruhduh@lemmy.world ⁨1⁩ ⁨year⁩ ago

      😎

      source