News for hackers. Stuff that matters.
Re:When management went nuclear on an innocent software engi... by goldenkey on Saturday May 28, 2022 @07:26AM (#31539455)
As usual, half of the story is the truth and rest is bullshit. "bonuses all around" - good one. I suppose they had a last supper scene too, with dollar bills on the dinner table?

I forget the term for this type of journalism. It's been previously said on HN that it's almost a rule for on-call stories to be embellished beyond reason.

Re:When management went nuclear on an innocent software engi... by jeauxlb on Sunday May 29, 2022 @07:00PM (#31553726)
Interesting style of story-telling that seems to flips the chronology of the lie being told about time to fix (2 weeks) and the contractor being fired. Can't help but think if "Ellen" were honest about timeframes --- which a competent professional should be, even in the face of an obvious professional advantage --- then nobody need have lost their jobs for the mistaken attempt to progress the struggling project.
Re:When management went nuclear on an innocent software engi... by yunohn on Saturday May 28, 2022 @04:17AM (#31538568)
> And when you cloned the disks, you changed the DECNet address on each PC?

Kind of odd that the entire fail safe seems to depend on self-declared addresses.

Re:When management went nuclear on an innocent software engi... by the_biot on Saturday May 28, 2022 @06:55AM (#31539280)
As opposed to one assigned on the basis of a self-declared MAC address?

I find it much more odd -- if not surprising, particularly in the pager era -- that the whole thing, every component of it, was completely locked in to one vendor. Not just the VAX cluster and the PCs, but even the network protocol.

This was not unusual decades ago, but it was always insane.

Re:When management went nuclear on an innocent software engi... by yunohn on Saturday May 28, 2022 @07:08AM (#31539356)
That's fair, but a hardcoded address in a disk clone seems like a quick point of failure.