| ▲ | filearts 7 hours ago |
| I think it is distasteful and disrespectful to call out an employee by name in this way, regardless of the merit of the rest of the OP's post. |
|
| ▲ | iloveplants 6 hours ago | parent | next [-] |
| well, it was distasteful of to them to close op's pr and apply the same patch with improper attribution, and then use ai to respond when they were asked about it |
| |
| ▲ | atonse 6 hours ago | parent | next [-] | | I agree with the parent post that it's distasteful. There's no value in naming the employee. Whatever that employee did, if the company needed to figure out who it was, they can from the commit hashes, etc. But there's no value in the public knowing the employee's name. Remember that if someone Googles this person for a newer job, it might show up. This is the sort of stuff that can disproportionately harm that person's ability to get a job in the future, even if they made a small mistake (they even apologized for it and was open about what caused it). So no, it's completely unnecessary and irrelevant to the post. | | |
| ▲ | Freak_NL 5 hours ago | parent | next [-] | | > Remember that if someone Googles this person for a newer job, it might show up. Not to sound too harsh, but this is a person who rudely let AI perform a task badly which should have been handled by just… merging/rebasing the PR after confirming it does what it should do, then couldn't be bothered to reply and instead let the robot handle it, and then refused to fix the mess they made (making the apology void). That's three strikes. | | |
| ▲ | abraae 5 hours ago | parent | next [-] | | What if it's some junior given a job beyond their abilities, and struggling manfully using whatever tools they have to hand. Is it worth publicly trashing their name? What does their name really add to this article? | | | |
| ▲ | technion 5 hours ago | parent | prev [-] | | I agree what occurred is quite egregious. But "use ai to talk to customers" and "play games with signed commits" sound much more like corporate policy than one employees mistake. |
| |
| ▲ | mmsc 40 minutes ago | parent | prev | next [-] | | Why would the company need to figure it out from commit hashes? It's all public, in public GitHub repositories, with the person's personal GitHub account: https://github.com/auth0/nextjs-auth0/pull/2381 | |
| ▲ | Exoristos 5 hours ago | parent | prev | next [-] | | > This is the sort of stuff that can disproportionately harm that person's ability to get a job in the future. Isn't that beneficial in this case? | |
| ▲ | parliament32 5 hours ago | parent | prev [-] | | > Remember that if someone Googles this person for a newer job, it might show up. That's the whole point; I sincerely hope it does. Why would anyone want to hire someone that delegates their core job to a slop generator? |
| |
| ▲ | 6 hours ago | parent | prev [-] | | [deleted] |
|
|
| ▲ | mmsc 42 minutes ago | parent | prev | next [-] |
| (op here) On the one hand, you're right, it is distasteful, I completely agree. On the other hand, GitHub and Google and the public domain internet isn't everybody's CV that they can pick and choose which of their actions are publicised, tailored towards only their successes. |
|
| ▲ | merrvk 5 hours ago | parent | prev | next [-] |
| They maintain a public repo. |
| |
| ▲ | nstart 2 hours ago | parent [-] | | Yea. I can see what the parent is getting at. However the linked PR's contain the employee name. Their username is the same name mentioned in the article. So it would have been the same even if the author had just mentioned the username instead (which would be completely acceptable in all cases). I think junior employee or not, it's clear that they have the autonomy to check a PR for errors and fix it. So it's very much on them. |
|
|
| ▲ | DrammBA 5 hours ago | parent | prev [-] |
| I don't think it is distasteful or disrespectful, he's just explaining what happened and why, and he's obviously unhappy with the whole ordeal. |
