889
Hours of work
(programming.dev)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 23 Aug 2023
889 points (98.1% liked)
Programmer Humor
19503 readers
580 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
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?"
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.
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.
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.
Or worse, it was an n:1 and they want it n:n
Even worse, they'll claim it was a bug
this is ongoing now. Our "creators" were supposed to be "matched" for a "job" based on "skills", not "skill". pure chaos
Oof