893
Hours of work (programming.dev)
submitted 2 years ago by to c/programmer_humor@programming.dev
48 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 104 points 2 years ago (4 children)

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?"

  • permalink
  • fedilink
  • source
  • hideshow 8 child comments
    •
  • [–] 52 points 2 years 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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 34 points 2 years ago (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 19 points 2 years 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.

  • permalink
  • fedilink
  • source
  • parent