Rickover's Lessons
chinatalk.media
Rickover's Lessons
1–10 of 103 posts
Re: Rickover's Lessons
#2It's certainly true the strategic arms processes and nuclear submarine engineering benefited in a long term view.
I just find myself asking if the US army recruiting tag line Be The Best You Can Be was really met, or if Rickover achieved what might be more akin to crystallography "local optimum" where there are better peaks out there, but this one is mine. (To borrow another army concept)
Viewed from Australia the current state of US submarine construction is woeful. We're on the brink of being ripped off having prepaid for access to Virginia class subs soon, and AUKUS subs in future. We expect to be told we cannot have Virginia class subs ever, we cannot have longterm crewing or command ever, but we can host them retained in US HANDS and we can continue to pay for them.
Not that Rickover made that happen, but whatever his lessons are, the US submarine building industry doesn't seem to have learned then, or be able to apply them.
Re: Rickover's Lessons
#3Re: Rickover's Lessons
#4His writing style is very good, and he succinctly summarizes the phenomenon where a technology that is substantially complete to the point that it has known issues is looked down upon while a technology that is purely "on paper" (the "paper reactor" as he calls it) is treated as a good alternative, since the paper technology isn't far enough along for the problems to even be known. That's not even a good TL;DR, so you should just read Rickover's essay.
Re: Rickover's Lessons
#5I don't know how many people on HN have served and heard of Rickover? But I'm pretty sure most people on HN could not function in a Rickover style management context. It gets things done, but it's not terribly polite about going about getting them done.
To the article's credit, it does touch on this aspect of his management style. But engineers today are from the Millennial or GenZ generations. A lot of that just would not fly. I chuckle thinking about the shock and surprise on the average HN'ers face when one morning they come in and find out they're fired because a hypothetical "Rickover" did a code review last night and found a long existing bug they didn't fix yet.
And keep in mind, this hypothetical "Rickover" would review your code, and that of all your reports, every night. He doesn't like the architecture you chose? You're gone. He finds issues in the code of one of your subordinates? That subordinate is gone and you are too.
It's harsh. I'm not sure today's Americans are ready for that?
Re: Rickover's Lessons
#6Um. I don't know how many people on HN have served and heard of Rickover? But I'm pretty sure most people on HN could not function in a Rickover style management context. It gets things done, but it's not terribly polite about going about getting them done. To the article's credit, it does touch on this aspect of his management style. But engineers today are from the Millennial or GenZ generations. A lot of that just…
Re: Rickover's Lessons
#7His best lesson, in my opinion: https://whatisnuclear.com/rickover.html His writing style is very good, and he succinctly summarizes the phenomenon where a technology that is substantially complete to the point that it has known issues is looked down upon while a technology that is purely "on paper" (the "paper reactor" as he calls it) is treated as a good alternative, since the paper technology isn't far enough alon…
Re: Rickover's Lessons
#8Um. I don't know how many people on HN have served and heard of Rickover? But I'm pretty sure most people on HN could not function in a Rickover style management context. It gets things done, but it's not terribly polite about going about getting them done. To the article's credit, it does touch on this aspect of his management style. But engineers today are from the Millennial or GenZ generations. A lot of that just…
Ex-Navy nuke here; I had to interview with the KOG [*] to get into The Program.
My guess is that most people on HN would do fine in a Rickover-style program — albeit likely after some culture shock. After 50 years I can still recite my own interview with the man pretty much verbatim. I served only five years on active duty; I've forgotten most of what I knew about the specific subject of nuclear engineering. But the no-bullshit, face-the-facts general management style that Rickover created and propagated in the nuclear Navy was likely the single biggest professional influence of my life. To this day I regularly quote Rickover to my law students: You get what you INspect, not what you EXpect.
And in the fleet, most of us nukes were regular people, not nearly as abrasive or peremptory as he could be.
[*] KOG = Kindly Old Gentleman: Of those four things, Rickover was at most two.
Re: Rickover's Lessons
#9His best lesson, in my opinion: https://whatisnuclear.com/rickover.html His writing style is very good, and he succinctly summarizes the phenomenon where a technology that is substantially complete to the point that it has known issues is looked down upon while a technology that is purely "on paper" (the "paper reactor" as he calls it) is treated as a good alternative, since the paper technology isn't far enough alon…
It's like the current situation with "vibe coding". An LLM can build you something which demonstrates a principle in some kind of hand-wavy fashion, but the gap between the thing produced by the LLM and a sustainable product is just huge. And, as with the gap between Rickover's paper reactor and his practical reactor, it's often extraordinary difficult to explain to a non-specialist why that is so -- because the diff…
A lot of the bubbles in our field have been like that.
Re: Rickover's Lessons
#10That's downright un-American!
I love hearing stories about him. One that I have heard, a couple of times, is that a salesgoblin went into his second-floor office at the Pentagon, with a sample of some electronic equipment.
Rickover is said to have grabbed the device, walked over to his window, and dropped it to the ground beneath. He then said something along the lines of "If it still works, we can talk."