agilob@programming.dev to Programming@programming.devEnglish · 11 months agoThings to say when you're losing a technical argumentweb.archive.orgexternal-linkmessage-square22fedilinkarrow-up1135arrow-down12
arrow-up1133arrow-down1external-linkThings to say when you're losing a technical argumentweb.archive.orgagilob@programming.dev to Programming@programming.devEnglish · 11 months agomessage-square22fedilink
minus-squarexmunk@sh.itjust.workslinkfedilinkarrow-up5·11 months agoYea, 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.
minus-squareSocsa@sh.itjust.workslinkfedilinkarrow-up7·edit-211 months agoMe, 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:
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: