138
Things to say when you're losing a technical argument
(web.archive.org)
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 01 Dec 2023
138 points (97.9% liked)
Programming
17691 readers
271 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
are you losing because youre wrong or because someone wants to do something a different way and they have more buy in from the rest of the team?
If it’s the first thing just admit youre wrong and move on. If it’s the second thing either bring the data to show your way is better or just go with the other proposal. Having disagreements drag on for too long is going to make everybody unhappy.
edit: ah this is a joke article and not a question from op
Yea, a good developer, especially a senior developer, will fight like hell for the right answer... and if they realize their answer was wrong they should concede the point and maybe self-examine why they'd overlooked that possibility.
Me, giving a two hour presentation on why Jira is hot garbage at my performance review for three years straight:
Me, giving a six hour presentation on why Jira is hot garbage at my next job interview:
Me, explaining to the judge why Jira is hot garbage at my murder trial:
My last words on death row, reciting my self published book on why Jira is hot garbage: