Email or username:

Password:

Forgot your password?
3 posts total
Jason Lefkowitz

Founded in 1974, Tandem Computers was a leader in high-availability computing. For decades, if you had an application that absolutely could not tolerate unplanned downtime -- a bank, a stock exchange, a telephone network -- Tandem's "NonStop" computers were aimed at you.

NonStop machines achieved reliability through massive hardware redundancy. A NonStop computer was a cluster of computing modules, each with its own processors, memory, disks. A failure in one couldn't affect the others.

Redundancy made Tandem. So naturally, when they made some coffee mugs, it was important that they feature redundancy too.

en.wikipedia.org/wiki/Tandem_C

Founded in 1974, Tandem Computers was a leader in high-availability computing. For decades, if you had an application that absolutely could not tolerate unplanned downtime -- a bank, a stock exchange, a telephone network -- Tandem's "NonStop" computers were aimed at you.

NonStop machines achieved reliability through massive hardware redundancy. A NonStop computer was a cluster of computing modules, each with its own processors, memory, disks. A failure in one couldn't affect the others.

Show previous comments
Stephen Hoffman

@jalefkowit Around time of the failed ports of NSK to Alpha and then to Itanium, the redundancy switched from being hardware lockstep to firmware. (None of the commodity processors support lockstep.)

The NSK product line and most of the HP “server” business (and whatever little was left of DEC) was eventually ceded to HPE.

Here is some info on the post-Tandem-hardware commodity designs, from 2008:

availabilitydigest.com/public_

LeoBurr :leoburr:

@jalefkowit I was at Compaq during the Tandem merger.

I thought we all were getting free or discounted dual stick popsicles.

Sonikku

@jalefkowit
I encountered Tandem during my 6+ year tenure in the banking industry. Some banks in my country still use these systems, because of the high reliability required.

Jason Lefkowitz

Free advice from someone who's been at this for a while: when you realize you're going to miss a deadline, send an email to the person you promised the thing to saying "hey, I just wanted to let you know I'm going to miss the deadline."

I know that's a hard email to send. But you need to.

95% of the time, it will turn out that the person is actually fine with you missing the deadline. And the other 5% of the time, you will still be better off than if you'd said nothing at all, or waited till the last minute. The sooner you tell the person that, the less upset they will be.

Pull off that band-aid. Send the email.

Free advice from someone who's been at this for a while: when you realize you're going to miss a deadline, send an email to the person you promised the thing to saying "hey, I just wanted to let you know I'm going to miss the deadline."

I know that's a hard email to send. But you need to.

95% of the time, it will turn out that the person is actually fine with you missing the deadline. And the other 5% of the time, you will still be better off than if you'd said nothing at all, or waited till the...

Show previous comments
Tom Lorenz

@jalefkowit I learned that lesson years ago when I started doing tech support for real, and I live by it to this day.

This is the way.

malte

@jalefkowit The minimum level of responsibility you can have for anything is to recognize and tell people who are dependent on you that you cannot be responsible any longer. The most demanding people to collaborate with are those you need to check in with regularly to confirm they haven't dropped the ball because they wouldn't tell you if they did.

Bruce Mirken

@jalefkowit Oh god yes. I used to edit reports for an advocacy nonprofit, and it drove me crazy when colleagues blew off a deadline with no warning. They apparently never considered that I'd organized my week around their big project and they'd just disrupted it all.

Go Up