WEBVTT 00:00:00.000 --> 00:00:02.040 Welcome back to The Deep Dive, where we transform 00:00:02.040 --> 00:00:04.799 your stack of sources, comprehensive profiles, 00:00:05.120 --> 00:00:07.360 the dense research, the technical papers, into 00:00:07.360 --> 00:00:09.359 the most essential and fascinating conversation 00:00:09.359 --> 00:00:11.740 that gets you truly well -informed. Our commitment 00:00:11.740 --> 00:00:14.359 is to synthesize all this information, cut through 00:00:14.359 --> 00:00:17.019 the sheer volume of facts, and really find those 00:00:17.019 --> 00:00:19.379 unexpected insights, you know, the aha moments 00:00:19.379 --> 00:00:21.980 that make the history and the technology truly 00:00:21.980 --> 00:00:25.679 stick. And today, we are embarking on a deep 00:00:25.679 --> 00:00:29.300 dive into a figure who is, well... arguably the 00:00:29.300 --> 00:00:31.320 true founder of the information age as we know 00:00:31.320 --> 00:00:34.149 it, Rear Admiral Grace Brewster Hopper. Her life 00:00:34.149 --> 00:00:37.189 story is just this magnificent tapestry. It's 00:00:37.189 --> 00:00:39.850 woven from these threads that seem so disparate. 00:00:39.869 --> 00:00:42.109 You have advanced mathematics on one hand, then 00:00:42.109 --> 00:00:44.350 this unrelenting military service that spans, 00:00:44.429 --> 00:00:46.909 what, four decades? And then these completely 00:00:46.909 --> 00:00:49.329 revolutionary computer science breakthroughs. 00:00:49.329 --> 00:00:51.450 When you really look at her career, the sheer 00:00:51.450 --> 00:00:53.630 scope is just, it's almost overwhelming. She 00:00:53.630 --> 00:00:58.009 was a Yale PhD, a Navy Admiral, and an architect 00:00:58.009 --> 00:01:00.520 of global commerce. But the common thread, the 00:01:00.520 --> 00:01:02.539 thing that runs through all of those roles, is 00:01:02.539 --> 00:01:05.340 her relentless fight against complexity. That's 00:01:05.340 --> 00:01:08.420 the key. Exactly. We are unpacking a comprehensive 00:01:08.420 --> 00:01:11.200 biographical profile today, and we're going to 00:01:11.200 --> 00:01:13.920 trace her journey from a child who literally 00:01:13.920 --> 00:01:16.819 disassembled her world to figure out how it worked. 00:01:16.879 --> 00:01:19.060 I love that story. All the way through her work 00:01:19.060 --> 00:01:21.780 on the earliest mechanical computers and into 00:01:21.780 --> 00:01:24.340 her final act as the oldest active duty officer 00:01:24.340 --> 00:01:26.980 in the U .S. Navy. And our mission here for you 00:01:26.980 --> 00:01:29.599 is to understand how her technical genius was 00:01:29.599 --> 00:01:32.579 constantly paired with this really uncompromising 00:01:32.579 --> 00:01:35.379 dedication to accessibility. We want to grasp 00:01:35.379 --> 00:01:38.659 the full implications of the concept she championed, 00:01:38.659 --> 00:01:41.439 machine -independent programming. That concept, 00:01:41.540 --> 00:01:43.540 I mean, that's the absolute core of her legacy. 00:01:43.719 --> 00:01:46.040 The idea that programs should be written in English, 00:01:46.239 --> 00:01:49.140 not mathematical symbols or some cryptic machine 00:01:49.140 --> 00:01:51.560 code. It sounds so simple to us now. Of course. 00:01:51.700 --> 00:01:54.609 But before Hopper... To instruct a computer, 00:01:54.750 --> 00:01:56.689 you had to speak its native tongue. And that 00:01:56.689 --> 00:01:59.069 tongue was assembly language, or worse, just 00:01:59.069 --> 00:02:02.209 raw binary or octal code. It was a language only 00:02:02.209 --> 00:02:04.829 a handful of specialists could ever hope to master. 00:02:05.159 --> 00:02:07.120 She fundamentally challenged that assumption, 00:02:07.319 --> 00:02:10.139 the assumption that computational power was inherently 00:02:10.139 --> 00:02:12.900 restricted to this tiny, mathematically elite 00:02:12.900 --> 00:02:15.620 group. Right. She recognized that if computers 00:02:15.620 --> 00:02:17.780 were ever going to move beyond government labs 00:02:17.780 --> 00:02:20.240 and specialized military projects, they had to 00:02:20.240 --> 00:02:23.560 be usable, usable by business managers, accountants, 00:02:23.560 --> 00:02:25.979 you know, general data processors. She looked 00:02:25.979 --> 00:02:30.159 at this incredibly complex, bespoke, just difficult 00:02:30.159 --> 00:02:32.580 process of programming, and she just declared 00:02:32.580 --> 00:02:36.460 it inefficient. unnecessarily hard yeah and her 00:02:36.460 --> 00:02:39.280 simple belief That we should communicate with 00:02:39.280 --> 00:02:41.599 the machine using human language. It required 00:02:41.599 --> 00:02:44.099 a multi -decade battle against institutional 00:02:44.099 --> 00:02:47.120 resistance. But it is precisely the reason why 00:02:47.120 --> 00:02:49.400 you can use a smartphone or run a spreadsheet 00:02:49.400 --> 00:02:51.960 today. She built that bridge. It wasn't just 00:02:51.960 --> 00:02:54.120 a technical invention, you see. It was an economic 00:02:54.120 --> 00:02:57.000 and really a philosophical mandate. She saw the 00:02:57.000 --> 00:02:59.800 computer not as some complex calculation engine, 00:02:59.900 --> 00:03:02.919 but as an indispensable utility for general commerce. 00:03:03.259 --> 00:03:05.909 Her work was all about abstraction. building 00:03:05.909 --> 00:03:08.250 a tool that hid the terrifying complexity of 00:03:08.250 --> 00:03:10.750 the hardware beneath a simple, clear interface. 00:03:11.129 --> 00:03:13.430 That's the perfect way to put it. Okay, let's 00:03:13.430 --> 00:03:15.430 unpack this journey. And we have to start at 00:03:15.430 --> 00:03:17.569 the beginning. Before she was Admiral Hopper, 00:03:17.650 --> 00:03:20.469 she was Grace Brewster Murray, born in New York 00:03:20.469 --> 00:03:24.189 City on December 9, 1906. But the key to her 00:03:24.189 --> 00:03:27.189 entire personality, her whole career, was this 00:03:27.189 --> 00:03:31.009 trait she exhibited almost immediately, an insatiable 00:03:31.009 --> 00:03:34.370 and, I'd say, disruptive curiosity. The famous 00:03:34.370 --> 00:03:36.449 childhood anecdote illustrates this perfectly. 00:03:36.889 --> 00:03:39.469 I mean, at the age of seven, she was already 00:03:39.469 --> 00:03:42.150 obsessed with mechanisms. She needed to know 00:03:42.150 --> 00:03:44.530 what made the clocks tick. And this wasn't some, 00:03:44.550 --> 00:03:46.469 you know, passive intellectual interest. This 00:03:46.469 --> 00:03:48.590 was active deconstruction. She didn't just look 00:03:48.590 --> 00:03:50.930 at one clock. The story goes that she systematically 00:03:50.930 --> 00:03:54.069 dismantled seven different alarm clocks, trying 00:03:54.069 --> 00:03:56.150 to figure out the internal mechanisms before 00:03:56.150 --> 00:03:58.129 her mother finally stepped in. And confiscated 00:03:58.129 --> 00:04:00.669 the parts. Exactly. Limited her future investigations 00:04:00.669 --> 00:04:03.400 to a single clock at a time. But that behavior, 00:04:03.539 --> 00:04:06.419 that drive to just take apart a complex system, 00:04:06.580 --> 00:04:09.180 understand its guts, and then presumably figure 00:04:09.180 --> 00:04:11.979 out how to put it back together. That's the blueprint 00:04:11.979 --> 00:04:15.180 for her entire career in computing. She wasn't 00:04:15.180 --> 00:04:17.620 satisfied with the black box. She had to see 00:04:17.620 --> 00:04:20.100 the cogs turning, whether they were actual brass 00:04:20.100 --> 00:04:23.709 gears or later electrical relays. And what's 00:04:23.709 --> 00:04:26.829 so fascinating is how that exact same trait shows 00:04:26.829 --> 00:04:30.069 up decades later after she's retired as a literal 00:04:30.069 --> 00:04:33.170 philosophical tool. Yeah. The sources all mentioned 00:04:33.170 --> 00:04:35.610 she had this clock on her wall. The one that 00:04:35.610 --> 00:04:37.850 ran counterclockwise. The one that ran counterclockwise. 00:04:37.949 --> 00:04:40.069 And that clock wasn't just some quirky decorative 00:04:40.069 --> 00:04:41.990 choice. No, it was a prop. It was a teaching 00:04:41.990 --> 00:04:45.310 tool. It served as this constant, tangible reminder 00:04:45.310 --> 00:04:47.910 of her lifelong battle against the inertia of 00:04:47.910 --> 00:04:50.370 established systems. And the quote that goes 00:04:50.370 --> 00:04:52.629 with it is crucial to understanding her. She 00:04:52.629 --> 00:04:55.439 said, Humans are allergic to change. They love 00:04:55.439 --> 00:04:57.600 to say, we've always done it this way. I try 00:04:57.600 --> 00:04:59.420 to fight that. It just shows she wasn't just 00:04:59.420 --> 00:05:01.339 a technical innovator. She was a cultural warrior. 00:05:01.720 --> 00:05:04.879 Absolutely. If the entire computing world was 00:05:04.879 --> 00:05:08.040 running clockwise, insisting on complexity, on 00:05:08.040 --> 00:05:11.139 rigid adherence to assembly code hopper, was 00:05:11.139 --> 00:05:14.160 the one running counterclockwise, demonstrating 00:05:14.160 --> 00:05:16.759 that breaking established patterns was, well... 00:05:17.160 --> 00:05:20.100 necessary for progress. And this iconoclasm was 00:05:20.100 --> 00:05:22.899 forged in a highly, highly rigorous academic 00:05:22.899 --> 00:05:25.980 environment. Her educational background is so 00:05:25.980 --> 00:05:27.939 important because it provides the foundation 00:05:27.939 --> 00:05:31.040 for the precision and the abstraction she later 00:05:31.040 --> 00:05:33.279 brought to programming. She attended Vassar College, 00:05:33.639 --> 00:05:37.279 graduating Phi Beta Kappa in 1928 with a BA in 00:05:37.279 --> 00:05:39.180 mathematics and physics. And then moved directly 00:05:39.180 --> 00:05:41.480 to Yale, which... I mean, that speaks volumes 00:05:41.480 --> 00:05:43.660 about her intellectual drive at the time. She 00:05:43.660 --> 00:05:45.980 earned her master of science degree in 1930 and 00:05:45.980 --> 00:05:47.939 most significantly, her Ph .D. in mathematics 00:05:47.939 --> 00:05:51.100 in 1934. We really have to pause on that PhD 00:05:51.100 --> 00:05:53.680 achievement. This was the mid -1930s. Earning 00:05:53.680 --> 00:05:56.220 a PhD in pure mathematics from Yale was an elite 00:05:56.220 --> 00:05:58.339 achievement for anyone, let alone a woman at 00:05:58.339 --> 00:06:00.220 that time. Oh, absolutely. It placed her firmly 00:06:00.220 --> 00:06:02.300 in the highest tiers of theoretical academics. 00:06:02.680 --> 00:06:05.560 Her doctoral advisor was the distinguished Norwegian 00:06:05.560 --> 00:06:08.420 mathematician Einstein Orr. And her dissertation 00:06:08.420 --> 00:06:11.800 title? New types of irreducibility criteria. 00:06:12.300 --> 00:06:15.379 It just highlights her intellectual depth. This 00:06:15.379 --> 00:06:18.459 wasn't applied math. This was high -level... 00:06:23.519 --> 00:06:26.019 And this is precisely the connection we need 00:06:26.019 --> 00:06:29.050 to make for you, the listener. Her deep, deep 00:06:29.050 --> 00:06:31.930 understanding of theoretical mathematics is what 00:06:31.930 --> 00:06:33.990 enabled her to see the unnecessary complexity 00:06:33.990 --> 00:06:36.569 later on. It's a great point. Because she was 00:06:36.569 --> 00:06:39.649 so fluent in symbolic manipulation, she recognized 00:06:39.649 --> 00:06:42.370 that 99 % of the people who needed to use a computer, 00:06:42.589 --> 00:06:45.230 the data processors, they didn't need that fluency. 00:06:45.490 --> 00:06:47.970 Her quest for simplicity wasn't born out of an 00:06:47.970 --> 00:06:50.310 inability to handle complexity. It was born out 00:06:50.310 --> 00:06:52.329 of a mastery of it. So she starts teaching math 00:06:52.329 --> 00:06:55.629 at Vassar in 1931, rises pretty quickly to associate 00:06:55.629 --> 00:06:58.649 professor by 1941. So by the time World War II 00:06:58.649 --> 00:07:01.689 breaks out, she is a tenured, highly respected 00:07:01.689 --> 00:07:04.350 academic theorist. A very established life. A 00:07:04.350 --> 00:07:06.329 very established life that was about to be completely 00:07:06.329 --> 00:07:08.569 upended by the needs of the Navy. And the war, 00:07:08.610 --> 00:07:10.629 well, it changes everything. She decides she 00:07:10.629 --> 00:07:13.129 needs to serve her country. She tries to join 00:07:13.129 --> 00:07:16.790 the Navy Reserve. But right away, we see a preview 00:07:16.790 --> 00:07:19.930 of her future battles against bureaucracy. Even 00:07:19.930 --> 00:07:23.399 just enlisting was a fight. It was almost laughably 00:07:23.399 --> 00:07:25.759 difficult. She was initially turned down, what, 00:07:25.800 --> 00:07:28.399 three times? Three times. And the reasons are 00:07:28.399 --> 00:07:31.120 just this perfect microcosm of the rigid institutional 00:07:31.120 --> 00:07:33.699 thinking she would later spend her life dismantling. 00:07:34.279 --> 00:07:37.579 First, she was 34 years old. Too old. Considered 00:07:37.579 --> 00:07:40.379 too old for commissioning. Second, the Navy decided 00:07:40.379 --> 00:07:43.019 her teaching job at Vassar was too valuable to 00:07:43.019 --> 00:07:45.279 the war effort for her to leave. And the third 00:07:45.279 --> 00:07:47.860 rejection, this one is simply incredible. She 00:07:47.860 --> 00:07:51.189 was rejected because she was too... Right. The 00:07:51.189 --> 00:07:53.269 weight -to -height ratio requirement stipulated 00:07:53.269 --> 00:07:56.230 a minimum weight of 120 pounds, and she was 15 00:07:56.230 --> 00:07:58.670 pounds below that. She literally had to get a 00:07:58.670 --> 00:08:01.709 weight exemption to serve her country. But Hopper, 00:08:01.750 --> 00:08:04.910 being Hopper, she persisted. Of course. She took 00:08:04.910 --> 00:08:07.389 a leave of absence from Vassar, got the exemption, 00:08:07.670 --> 00:08:10.029 and was sworn into the U .S. Navy Reserve in 00:08:10.029 --> 00:08:12.889 1943, joining the women accepted for volunteer 00:08:12.889 --> 00:08:16.610 emergency service. The waves. And again, she 00:08:16.610 --> 00:08:19.939 excelled. graduated first in her class from the 00:08:19.939 --> 00:08:23.819 Naval Reserve Midshipman School in 1944. She 00:08:23.819 --> 00:08:25.439 was commissioned as a lieutenant junior grade, 00:08:25.620 --> 00:08:28.100 and almost immediately she was assigned to a 00:08:28.100 --> 00:08:30.139 place that would determine the rest of her life, 00:08:30.600 --> 00:08:34.019 the Bureau of Ships Computation Project at Harvard 00:08:34.019 --> 00:08:36.320 University. And this is the moment, this is where 00:08:36.320 --> 00:08:38.620 the theoretical mathematician meets the physical 00:08:38.620 --> 00:08:41.639 reality of computing. She was assigned to the 00:08:41.639 --> 00:08:44.139 programming staff for the Harvard Mark I computer. 00:08:44.700 --> 00:08:46.419 The automatic sequence -controlled calculator. 00:08:46.620 --> 00:08:49.179 Which was the absolute vanguard of computational 00:08:49.179 --> 00:08:51.980 technology at the time. To truly appreciate her 00:08:51.980 --> 00:08:55.539 role here, we really have to set the stage. What 00:08:55.539 --> 00:08:57.679 was the mark I like? It wasn't silicon. It wasn't 00:08:57.679 --> 00:08:59.919 electronic. It was electromechanical. Yeah, that's 00:08:59.919 --> 00:09:02.179 a term we don't hear much anymore. Imagine a 00:09:02.179 --> 00:09:05.679 machine that was 51 feet long, 8 feet high, and 00:09:05.679 --> 00:09:08.519 weighed nearly 5 tons. This is massive. It was 00:09:08.519 --> 00:09:10.899 incredibly loud. You'd hear it constantly clanking 00:09:10.899 --> 00:09:14.399 as the mechanical relays opened and closed. Calculations 00:09:14.399 --> 00:09:16.940 were slow. I mean, a simple multiplication could 00:09:16.940 --> 00:09:20.059 take around 6 seconds. This was a physical giant 00:09:20.059 --> 00:09:22.539 built of steel and glass running on electric 00:09:22.539 --> 00:09:25.960 motors and relays. A beast. And programming it 00:09:25.960 --> 00:09:29.059 was a brutally physical process. You weren't... 00:09:29.480 --> 00:09:32.639 Typing on a screen, there was no screen. You 00:09:32.639 --> 00:09:34.720 were literally working with switches and punch 00:09:34.720 --> 00:09:37.299 cards. And sometimes manually wiring the machine, 00:09:37.460 --> 00:09:39.419 right, to set up the sequence of calculations. 00:09:39.639 --> 00:09:42.980 Exactly. It was a painstaking, labor -intensive 00:09:42.980 --> 00:09:46.340 process, incredibly prone to errors, and it required 00:09:46.340 --> 00:09:48.779 immense precision. And Hopper was one of the 00:09:48.779 --> 00:09:51.090 very first... people in the world to be called 00:09:51.090 --> 00:09:53.990 a programmer for this kind of machine. Her specific 00:09:53.990 --> 00:09:56.350 initial task was calculating missile trajectory 00:09:56.350 --> 00:09:59.929 tables for the Navy. So, complex partial differential 00:09:59.929 --> 00:10:02.389 equations that required thousands upon thousands 00:10:02.389 --> 00:10:04.110 of steps. All done on this clanking mechanical 00:10:04.110 --> 00:10:06.470 monster. And her contribution was immediate. 00:10:06.629 --> 00:10:08.789 It was fundamental to scaling the practice of 00:10:08.789 --> 00:10:11.450 computing. She co -authored three essential papers 00:10:11.450 --> 00:10:13.230 on the machine's operation with its director, 00:10:13.389 --> 00:10:16.750 Howard H. Aiken. But more importantly, she offered 00:10:16.750 --> 00:10:18.929 what is widely considered the first computer 00:10:18.929 --> 00:10:22.240 manual. That manual, a manual of operation for 00:10:22.240 --> 00:10:24.480 the automatic sequence controlled calculator, 00:10:24.879 --> 00:10:28.110 is a landmark document. Think about that for 00:10:28.110 --> 00:10:30.389 a moment. In an environment that's dominated 00:10:30.389 --> 00:10:33.629 by trial and error, by sort of, you know, proprietary 00:10:33.629 --> 00:10:36.389 knowledge. Yeah, tribal knowledge. Right. She 00:10:36.389 --> 00:10:39.549 created the standardized written documentation, 00:10:39.830 --> 00:10:42.730 the instruction set, that allowed others to replicate 00:10:42.730 --> 00:10:45.590 and utilize the machine efficiently. She was 00:10:45.590 --> 00:10:47.549 defining the engineering discipline of computer 00:10:47.549 --> 00:10:50.490 science before it was even named. It's interesting 00:10:50.490 --> 00:10:52.590 to consider the context, though. Here is a Yale 00:10:52.590 --> 00:10:55.629 Ph .D. mathematician, but in the military structure, 00:10:55.789 --> 00:10:58.289 she was a subordinate. officer under Aiken. Was 00:10:58.289 --> 00:11:00.090 there ever a tension between her theoretical 00:11:00.090 --> 00:11:03.429 genius and the practical, you know, hierarchical 00:11:03.429 --> 00:11:06.009 military environment? Oh, absolutely. The military 00:11:06.009 --> 00:11:08.590 environment valued hierarchy and defined procedures, 00:11:08.769 --> 00:11:10.889 which would naturally clash with the academic 00:11:10.889 --> 00:11:14.149 mindset of open exploration. But Hopper, she 00:11:14.149 --> 00:11:16.529 thrived on structure, but only when it led to 00:11:16.529 --> 00:11:19.210 clarity. Her brilliance, which is shown by her 00:11:19.210 --> 00:11:22.389 writing that manual, was in translating the operational 00:11:22.389 --> 00:11:27.059 chaos of a brand new machine into a predictable, 00:11:27.240 --> 00:11:29.679 logical process that the Navy could actually 00:11:29.679 --> 00:11:32.740 use. She formalized the process. So after the 00:11:32.740 --> 00:11:35.059 war, she wants to transfer to the regular Navy. 00:11:35.220 --> 00:11:37.940 But bureaucracy strikes again. She was two years 00:11:37.940 --> 00:11:40.600 over the age cutoff of 38, so she was denied 00:11:40.600 --> 00:11:43.500 the transfer. But this administrative roadblock, 00:11:43.679 --> 00:11:46.700 it led to a really pivotal career choice. She 00:11:46.700 --> 00:11:48.879 remained at the Harvard Computation Lab as a 00:11:48.879 --> 00:11:51.879 research fellow under a Navy contract until 1949. 00:11:52.139 --> 00:11:54.799 And during this time, Vassar offered her a full 00:11:54.799 --> 00:11:58.179 professorship. A highly prestigious, safe, established 00:11:58.179 --> 00:12:00.539 academic position. And she turned it down. She 00:12:00.539 --> 00:12:02.860 declined the security and the prestige of a full 00:12:02.860 --> 00:12:05.019 professorship to stay with the blinking lights 00:12:05.019 --> 00:12:07.200 and the whirring mechanisms of early computing. 00:12:07.519 --> 00:12:10.259 That decision, I mean, it speaks volumes. It 00:12:10.259 --> 00:12:12.360 really does. She recognized that the theoretical 00:12:12.360 --> 00:12:14.600 world she had mastered was being eclipsed by 00:12:14.600 --> 00:12:18.159 this new, practical, applied science. She chose 00:12:18.159 --> 00:12:21.149 the future over the comfortable past. And that 00:12:21.149 --> 00:12:23.809 choice led her straight into the rapidly emerging 00:12:23.809 --> 00:12:26.610 and very volatile commercial computing market. 00:12:26.789 --> 00:12:31.210 So in 1949, Hopper leaves that academic and military 00:12:31.210 --> 00:12:34.149 cocoon of Harvard, and she joins the Eckhart 00:12:34.149 --> 00:12:36.970 Moschley Computer Corporation as a senior mathematician. 00:12:37.090 --> 00:12:40.009 This shift was critical because Eckhart Moschley 00:12:40.009 --> 00:12:43.149 was building the UNIVAC, a first large -scale 00:12:43.149 --> 00:12:46.110 electronic computer designed specifically... 00:12:46.330 --> 00:12:48.009 For the commercial market. Right. The context 00:12:48.009 --> 00:12:50.450 here is changing drastically. At Harvard, the 00:12:50.450 --> 00:12:52.929 goal was scientific calculation. Now, the goal 00:12:52.929 --> 00:12:56.129 was business. It was payroll, inventory, logistics. 00:12:56.590 --> 00:12:58.570 Remington Rand later takes over the company, 00:12:58.690 --> 00:13:01.529 but Hopper stays focused on the UNIVAC, which 00:13:01.529 --> 00:13:03.870 would hit the market in 1951. And it was in this 00:13:03.870 --> 00:13:06.009 commercial setting dealing with the demands of 00:13:06.009 --> 00:13:08.350 business users that she devised the theory that 00:13:08.350 --> 00:13:11.200 fundamentally changed computing. machine -independent 00:13:11.200 --> 00:13:13.559 programming languages. Let's dive into the technical 00:13:13.559 --> 00:13:15.539 problems she was solving here. Yeah. Because 00:13:15.539 --> 00:13:18.100 it was a huge one. The problem was one of efficiency 00:13:18.100 --> 00:13:21.279 and cost. To program the UNIVAC, you still needed 00:13:21.279 --> 00:13:23.940 assembly language or machine code. This required 00:13:23.940 --> 00:13:26.759 highly specialized, rare, and very expensive 00:13:26.759 --> 00:13:30.100 programmers. And if a programmer made one tiny 00:13:30.100 --> 00:13:33.840 error, a missing comma, a wrong switch setting, 00:13:34.039 --> 00:13:37.159 the entire program failed and debugging was a 00:13:37.159 --> 00:13:40.129 complete nightmare. The labor cost and the technical 00:13:40.129 --> 00:13:42.929 debt were enormous, just astronomical. And that's 00:13:42.929 --> 00:13:45.110 where her famous quote about symbol manipulators 00:13:45.110 --> 00:13:48.049 comes in. She wasn't being dismissive of mathematicians. 00:13:48.049 --> 00:13:49.850 She was just highlighting the market reality. 00:13:50.230 --> 00:13:53.860 Precisely. She stated. Very few people are really 00:13:53.860 --> 00:13:56.179 simple manipulators. If they are, they become 00:13:56.179 --> 00:13:58.740 professional mathematicians, not data processors. 00:13:59.159 --> 00:14:01.440 She saw that the people who needed to run the 00:14:01.440 --> 00:14:03.860 payroll, the data processors, were fundamentally 00:14:03.860 --> 00:14:06.799 interested in business logic, not the internal 00:14:06.799 --> 00:14:09.000 octal code of the machine. They needed clarity 00:14:09.000 --> 00:14:12.259 and speed. So she proposed this simple yet profound 00:14:12.259 --> 00:14:15.279 solution. Create a language based on English, 00:14:15.460 --> 00:14:17.379 which would then be automatically translated 00:14:17.379 --> 00:14:19.960 by the computer into the complex machine code 00:14:19.960 --> 00:14:22.419 required to run the hardware. This is the moment 00:14:22.419 --> 00:14:24.580 of abstraction. She introduced the concept of 00:14:24.580 --> 00:14:27.059 the compiler. It's a brilliant conceptual leap, 00:14:27.240 --> 00:14:30.039 but it was met with fierce, immediate resistance. 00:14:30.519 --> 00:14:33.080 Oh, yeah. She fought for this idea for three 00:14:33.080 --> 00:14:35.679 years. And the resistance, it wasn't just technical. 00:14:35.700 --> 00:14:38.639 It was ideological. It was economic. Why did 00:14:38.639 --> 00:14:43.659 so many engineers reject the idea so, so vehemently? 00:14:43.720 --> 00:14:46.799 Well, for several reasons. Ideologically, engineers 00:14:46.799 --> 00:14:49.220 and programmers of the time, they believed they 00:14:49.220 --> 00:14:51.399 had to be in absolute control of the machine. 00:14:51.679 --> 00:14:54.299 They thought if you introduced an intermediary 00:14:54.299 --> 00:14:57.179 layer, a translator, you introduced inefficiency 00:14:57.179 --> 00:15:00.419 and a loss of control. And economically. Economically, 00:15:00.600 --> 00:15:02.860 assembly language programmers were highly paid 00:15:02.860 --> 00:15:06.500 and this new system threatened to democratize 00:15:06.500 --> 00:15:08.059 their specialized knowledge. It was a threat 00:15:08.059 --> 00:15:10.500 to their job security, really. The critics famously 00:15:10.500 --> 00:15:13.000 told her computers didn't understand English. 00:15:13.220 --> 00:15:15.210 And she refuted that by saying. Essentially, 00:15:15.590 --> 00:15:17.679 they don't have to. The compiler understands 00:15:17.679 --> 00:15:20.460 English, and the compiler then translates that 00:15:20.460 --> 00:15:23.039 clear human instruction into the language the 00:15:23.039 --> 00:15:24.899 machine does understand. She talked about the 00:15:24.899 --> 00:15:26.600 frustration. She said, I had a writing compiler 00:15:26.600 --> 00:15:28.759 and nobody would touch it. They told me computers 00:15:28.759 --> 00:15:30.500 could only do arithmetic. They were just locked 00:15:30.500 --> 00:15:33.120 into that mindset, the idea that the input must 00:15:33.120 --> 00:15:36.379 equal the output in complexity. But she persisted. 00:15:36.379 --> 00:15:39.240 In 1952, she published her first paper on the 00:15:39.240 --> 00:15:41.940 subject. And despite all the internal skepticism, 00:15:42.200 --> 00:15:45.139 she had an operational program linker, which 00:15:45.139 --> 00:15:48.379 she named the... A compiler, specifically the 00:15:48.379 --> 00:15:51.649 A0 system. the a0 system is often mischaracterized 00:15:51.649 --> 00:15:53.889 as just a translator but its core innovation 00:15:53.889 --> 00:15:56.490 was the automation of subroutine handling and 00:15:56.490 --> 00:15:58.470 linking okay so what does that mean in practical 00:15:58.470 --> 00:16:00.950 terms well before a0 if you needed to calculate 00:16:00.950 --> 00:16:03.590 a square root you had to manually write out the 00:16:03.590 --> 00:16:05.809 complex sequence of instructions every single 00:16:05.809 --> 00:16:08.289 time you needed it in your program which is incredibly 00:16:08.289 --> 00:16:10.509 tedious and just begging for an error exactly 00:16:10.509 --> 00:16:14.549 a0 allowed programmers to define and reuse blocks 00:16:14.549 --> 00:16:17.389 of code subroutines by linking them together 00:16:17.389 --> 00:16:19.500 automatically you would just call the subroutine 00:16:19.500 --> 00:16:22.340 by name, and the Azera system would weave the 00:16:22.340 --> 00:16:24.740 pre -written machine code into the master program. 00:16:25.059 --> 00:16:27.360 So it's a birth of modular programming. It is. 00:16:27.539 --> 00:16:29.980 It dramatically reduced the amount of raw code 00:16:29.980 --> 00:16:32.360 a programmer had to write, and it massively increased 00:16:32.360 --> 00:16:35.080 the reliability of the software. It was a direct 00:16:35.080 --> 00:16:37.700 attack on the technical debt of manual coding. 00:16:37.899 --> 00:16:42.220 And by 1954... Remington Rand, seeing the undeniable 00:16:42.220 --> 00:16:44.480 reduction in programming time and the subsequent 00:16:44.480 --> 00:16:47.399 cost savings, they finally embraced the concept. 00:16:47.639 --> 00:16:49.700 Right, and Hopper was made the company's first 00:16:49.700 --> 00:16:52.000 director of automatic programming. Under her 00:16:52.000 --> 00:16:53.940 leadership, the department released the next 00:16:53.940 --> 00:16:56.620 generation of compiler -based languages. Two 00:16:56.620 --> 00:16:59.259 of the major early ones were Mathematic and Flomatic. 00:16:59.559 --> 00:17:02.279 And this is a crucial distinction to make. Mathematic, 00:17:02.379 --> 00:17:04.640 as the name suggests, was aimed at scientific 00:17:04.640 --> 00:17:07.160 users. It let them input algebraic notation, 00:17:07.460 --> 00:17:11.390 but Flomatic... That was the true spiritual predecessor 00:17:11.390 --> 00:17:14.490 to Kabul. Absolutely. Flowmatic was designed 00:17:14.490 --> 00:17:16.910 specifically for data processing, and it used 00:17:16.910 --> 00:17:19.490 English -like syntax almost exclusively. It was 00:17:19.490 --> 00:17:21.589 revolutionary. Programmers could write commands 00:17:21.589 --> 00:17:24.950 like input inventory file A, move A to B, and 00:17:24.950 --> 00:17:27.410 compare B with 10. It was the first time that 00:17:27.410 --> 00:17:29.490 business people could actually look at a program 00:17:29.490 --> 00:17:31.609 and reasonably understand what the computer was 00:17:31.609 --> 00:17:34.130 doing without needing an assembly language dictionary. 00:17:34.410 --> 00:17:36.950 It was a massive leap forward. And it's important 00:17:36.950 --> 00:17:39.630 to give credit where it's due. Hopper's work, 00:17:39.710 --> 00:17:42.269 it built on the foundation laid by others, showing 00:17:42.269 --> 00:17:45.130 how innovation really snowballs. The sources 00:17:45.130 --> 00:17:47.450 mentioned the Laning and Zierler system as an 00:17:47.450 --> 00:17:49.230 influence. Yeah, that was the first compiler 00:17:49.230 --> 00:17:52.950 to accept algebraic notation as input. It was 00:17:52.950 --> 00:17:54.710 a parallel development focused on scientific 00:17:54.710 --> 00:17:57.910 calculation at MIT. Hopper's genius was realizing 00:17:57.910 --> 00:18:00.670 that the same principle of translation and abstraction 00:18:00.670 --> 00:18:03.329 could be applied not just to math, but to the 00:18:03.329 --> 00:18:06.130 generalized language of business. And that realization, 00:18:06.349 --> 00:18:09.609 that set the stage for total industry standardization. 00:18:09.849 --> 00:18:12.910 Which brings us to COBOL. Moving beyond internal 00:18:12.910 --> 00:18:15.349 commercial development, the need for industry 00:18:15.349 --> 00:18:17.829 -wide standardization became impossible to ignore. 00:18:18.240 --> 00:18:20.099 You can see why. If every company has its own 00:18:20.099 --> 00:18:22.519 unique English -like language, they can't share 00:18:22.519 --> 00:18:25.039 programs or data across systems. It's chaos. 00:18:25.400 --> 00:18:27.460 This led to the formation of the Conference on 00:18:27.460 --> 00:18:29.779 Data Systems Languages, CODISL, in the spring 00:18:29.779 --> 00:18:32.960 of 1959. This was a landmark industry gathering. 00:18:33.140 --> 00:18:35.859 You had competitors, government officials, academics, 00:18:36.039 --> 00:18:39.099 all in the same room. Their goal was monumental. 00:18:40.039 --> 00:18:43.660 Create a single, unified, machine -independent 00:18:43.660 --> 00:18:46.240 programming language for business use. And Hopper 00:18:46.240 --> 00:18:48.319 was there as a technical consultant, and her 00:18:48.319 --> 00:18:51.200 influence was absolutely pivotal. They took her 00:18:51.200 --> 00:18:54.259 proven working model, the FLOMATIC language, 00:18:54.619 --> 00:18:57.759 and made it the foundation. The result, created 00:18:57.759 --> 00:19:01.339 in record time, was COBOL, Common Business Oriented 00:19:01.339 --> 00:19:04.599 Language. It explicitly extended FLOMATIC, integrating 00:19:04.599 --> 00:19:06.819 the best ideas from various sources, including 00:19:06.819 --> 00:19:10.319 IBM's competing language, COAMTRAN. COBOL wasn't 00:19:10.319 --> 00:19:12.519 just a technical compromise. It was Hopper's 00:19:12.519 --> 00:19:15.579 philosophical victory writ large. It cemented 00:19:15.579 --> 00:19:17.740 the idea that clarity was paramount. It gave 00:19:17.740 --> 00:19:19.740 the business world the ability to use commands 00:19:19.740 --> 00:19:23.059 like subtract income tax from pay. Just contrast 00:19:23.059 --> 00:19:26.319 that simple, easily audited English command with 00:19:26.319 --> 00:19:28.920 the cryptic hexadecimal or octal code required 00:19:28.920 --> 00:19:30.960 to perform the same operation in raw machine 00:19:30.960 --> 00:19:33.529 language. This change wasn't about elegance. 00:19:33.549 --> 00:19:36.349 It was about reliability, transferability, and 00:19:36.349 --> 00:19:39.589 human error reduction. And the economic impact 00:19:39.589 --> 00:19:43.130 was massive. Because COBOL was machine -independent 00:19:43.130 --> 00:19:45.250 and standardized, a company could buy hardware 00:19:45.250 --> 00:19:47.769 from, say, vendor A, write a massive payroll 00:19:47.769 --> 00:19:50.150 program in COBOL. And if they later upgraded 00:19:50.150 --> 00:19:53.309 to a different machine from vendor B, their foundational 00:19:53.309 --> 00:19:56.869 software still worked. This concept, portability, 00:19:57.109 --> 00:20:00.259 was revolutionary. Before COBOL, software was 00:20:00.259 --> 00:20:02.819 tied to specific hardware, meaning every time 00:20:02.819 --> 00:20:04.819 you upgraded, you had to rewrite everything. 00:20:05.079 --> 00:20:07.660 What a nightmare. COBOL protected massive business 00:20:07.660 --> 00:20:10.019 investments and fostered the entire ecosystem 00:20:10.019 --> 00:20:12.019 of independent business software development. 00:20:12.319 --> 00:20:14.859 It became the most ubiquitous business language 00:20:14.859 --> 00:20:17.619 globally, running critical infrastructure right 00:20:17.619 --> 00:20:20.279 up to the present day. So her work then transitions 00:20:20.279 --> 00:20:23.450 from creation to enforcement. After she was recalled 00:20:23.450 --> 00:20:25.789 to active Navy duty, she served as the director 00:20:25.789 --> 00:20:27.750 of the Navy Programming Languages Group from 00:20:27.750 --> 00:20:31.589 1967 to 1977. She was promoted to captain in 00:20:31.589 --> 00:20:34.569 1973. This is where she embraced the often unpopular 00:20:34.569 --> 00:20:36.750 role of the standards champion. She was charged 00:20:36.750 --> 00:20:39.049 with developing validation software for COBOL 00:20:39.049 --> 00:20:41.410 for the entire Navy. So she was the quality control. 00:20:41.789 --> 00:20:44.450 She was the gatekeeper. She insisted on strict 00:20:44.450 --> 00:20:46.910 adherence to the standards. If a vendor claimed 00:20:46.910 --> 00:20:49.849 their compiler ran COBOL, they had to pass Hopper's 00:20:49.849 --> 00:20:53.170 stringent conformance tests. No exceptions. Why 00:20:53.170 --> 00:20:55.529 was this standardization so critical for the 00:20:55.529 --> 00:20:58.430 military? Interoperability and cost control. 00:20:58.920 --> 00:21:01.059 The Defense Department was the largest single 00:21:01.059 --> 00:21:03.420 purchaser of computer hardware in the world. 00:21:03.539 --> 00:21:06.420 If every vendor had a slightly different dialect 00:21:06.420 --> 00:21:09.779 of COBOL, moving personnel or data between bases 00:21:09.779 --> 00:21:12.460 or departments becomes an impossible logistical 00:21:12.460 --> 00:21:15.400 headache. Hopper's validation tests forced vendors 00:21:15.400 --> 00:21:17.900 to converge their programming language dialects, 00:21:17.920 --> 00:21:20.539 saving the Navy billions and ensuring systems 00:21:20.539 --> 00:21:22.849 could actually communicate with each other. And 00:21:22.849 --> 00:21:24.890 this emphasis on standardization leads directly 00:21:24.890 --> 00:21:26.869 to one of her most incredible forward -thinking 00:21:26.869 --> 00:21:29.349 insights, one that sounds like she was predicting 00:21:29.349 --> 00:21:32.130 the modern internet and cloud architecture decades 00:21:32.130 --> 00:21:34.269 early. This is where it gets really interesting, 00:21:34.430 --> 00:21:36.950 the argument for distributed networks. In the 00:21:36.950 --> 00:21:39.670 1970s, the computing status symbol was the centralized 00:21:39.670 --> 00:21:43.230 mainframe, a massive, expensive computer often 00:21:43.230 --> 00:21:45.789 housed in an entire room, running everything 00:21:45.789 --> 00:21:48.740 for a huge organization. And Hopper looked at 00:21:48.740 --> 00:21:51.140 this model and she saw profound vulnerability 00:21:51.140 --> 00:21:54.680 and inefficiency. She advocated fiercely for 00:21:54.680 --> 00:21:56.599 the Defense Department to switch to networks 00:21:56.599 --> 00:21:59.740 of small distributed computers. It was a deeply 00:21:59.740 --> 00:22:03.000 controversial stance. She saw the immense processing 00:22:03.000 --> 00:22:06.259 bottleneck caused by centralization. Instead, 00:22:06.500 --> 00:22:09.119 she pushed for smaller, cheaper minicomputers 00:22:09.119 --> 00:22:12.440 distributed across the user base, but all connected. 00:22:12.740 --> 00:22:15.660 The key was that users on any node could access 00:22:15.660 --> 00:22:18.559 common shared databases. So she was essentially 00:22:18.559 --> 00:22:20.839 arguing for the power of the network over the 00:22:20.839 --> 00:22:23.440 power of the single central machine. Yes, and 00:22:23.440 --> 00:22:26.180 her rationale was twofold, cost and resiliency. 00:22:26.859 --> 00:22:28.980 Many computers were far cheaper than mainframes, 00:22:29.180 --> 00:22:31.579 making computation accessible to smaller departments. 00:22:31.960 --> 00:22:34.740 More critically for the Navy, if a large centralized 00:22:34.740 --> 00:22:37.140 system went down due to attack or malfunction, 00:22:37.579 --> 00:22:40.740 the entire organization would just halt. A distributed 00:22:40.740 --> 00:22:43.579 network provided resiliency. If one node failed, 00:22:43.740 --> 00:22:46.250 the others could carry on. She was conceptualizing 00:22:46.250 --> 00:22:48.730 the architecture that eventually led to client 00:22:48.730 --> 00:22:52.069 -server models, local area networks, and what 00:22:52.069 --> 00:22:55.809 we now call cloud distribution. She saw the future 00:22:55.809 --> 00:22:58.210 of connectivity before the hardware even existed 00:22:58.210 --> 00:23:00.849 to support it universally. And this standards 00:23:00.849 --> 00:23:03.490 work was so effective that the conformance tests 00:23:03.490 --> 00:23:05.349 she developed for languages like Fortran and 00:23:05.349 --> 00:23:07.589 COBOL were eventually assumed by the National 00:23:07.589 --> 00:23:10.789 Bureau of Standards, now NIST. She literally 00:23:10.789 --> 00:23:13.369 gave the government the tools to reliably procure 00:23:13.369 --> 00:23:16.529 and manage complex software. This brings us to 00:23:16.529 --> 00:23:18.390 the astonishing conclusion of her professional 00:23:18.390 --> 00:23:21.230 life, the military service that simply refused 00:23:21.230 --> 00:23:24.529 to end. She retired for the first time in 1966 00:23:24.529 --> 00:23:27.589 as a commander, adhering to the mandatory Navy 00:23:27.589 --> 00:23:30.390 attrition regulations at age 60. But the Navy, 00:23:30.670 --> 00:23:33.170 grappling with the very complexities of standardized 00:23:33.170 --> 00:23:35.710 computing that she had pioneered, they realized 00:23:35.710 --> 00:23:38.609 they could not afford to lose her specific institutional 00:23:38.609 --> 00:23:41.109 and technical knowledge. So she was immediately 00:23:41.109 --> 00:23:44.569 recalled to active duty in August 1967. That 00:23:44.569 --> 00:23:46.650 initial recall was only supposed to be for six 00:23:46.650 --> 00:23:49.089 months, a quick fix to a standardization problem. 00:23:49.349 --> 00:23:51.250 And that six -month assignment turned into nearly 00:23:51.250 --> 00:23:54.730 20 years. She retired again in 1971, was recalled 00:23:54.730 --> 00:23:58.839 in 1972. The pattern just continued. Her unique 00:23:58.839 --> 00:24:01.660 role in ensuring massive federal software systems 00:24:01.660 --> 00:24:04.460 were compliant and secure made her irreplaceable. 00:24:04.599 --> 00:24:07.200 She continuously outlasted the normal service 00:24:07.200 --> 00:24:09.700 tenure regulations. The promotions followed. 00:24:09.839 --> 00:24:14.279 She was made captain in 1973. Then in 1983, President 00:24:14.279 --> 00:24:16.940 Ronald Reagan promoted her to Commodore. After 00:24:16.940 --> 00:24:18.799 a representative on the Armed Services Committee, 00:24:19.019 --> 00:24:21.700 who had seen her featured on 60 Minutes, recognized 00:24:21.700 --> 00:24:24.500 her immense value. The rank of Commodore was 00:24:24.500 --> 00:24:28.619 renamed Rear Admiral, Lower Half, in 1985. At 00:24:28.619 --> 00:24:30.940 a time when female officers were extremely rare, 00:24:31.180 --> 00:24:33.359 this promotion elevated her to one of the highest 00:24:33.359 --> 00:24:35.799 ranks in the Navy, cementing her place in military 00:24:35.799 --> 00:24:38.900 history. She finally, definitively, retired in 00:24:38.900 --> 00:24:41.980 1986, closing out a military career that spanned 00:24:41.980 --> 00:24:45.819 more than 42 years. At 79 years, 8 months, and 00:24:45.819 --> 00:24:48.359 5 days old, she was the oldest active duty commissioned 00:24:48.359 --> 00:24:51.099 officer in the U .S. Navy. Her retirement ceremony 00:24:51.099 --> 00:24:53.339 was such a symbolic moment. It was held aboard 00:24:53.339 --> 00:24:55.460 the USS Constitution, the oldest commissioned 00:24:55.460 --> 00:24:58.559 ship in the U .S. Navy. The perfect juxtaposition 00:24:58.559 --> 00:25:01.480 of the Navy's deep history and its most modern 00:25:01.480 --> 00:25:04.519 pioneer. She received the Defense Distinguished 00:25:04.519 --> 00:25:07.380 Service Medal for her dedication. But the tireless 00:25:07.380 --> 00:25:10.740 energy, it didn't stop there. Immediately upon 00:25:10.740 --> 00:25:13.140 retiring from the Navy, she was hired by Digital 00:25:13.140 --> 00:25:16.660 Equipment Corporation, DEC, as a principal corporate 00:25:16.660 --> 00:25:20.200 consulting engineer. At DEC, her role was largely 00:25:20.200 --> 00:25:22.799 that of a public educator and a goodwill ambassador. 00:25:23.240 --> 00:25:26.200 She traveled constantly, lecturing to massive 00:25:26.200 --> 00:25:28.859 audiences, promoting the ethos of ease of use 00:25:28.859 --> 00:25:31.829 and sharing the history of early computing. And 00:25:31.829 --> 00:25:34.230 this is where we see that rebellious nature shine 00:25:34.230 --> 00:25:37.069 through again. She frequently wore her Navy full 00:25:37.069 --> 00:25:39.750 dress uniform to these civilian lectures. Despite 00:25:39.750 --> 00:25:42.049 Department of Defense policy forbidding former 00:25:42.049 --> 00:25:44.269 officers from wearing the uniform in such circumstances. 00:25:44.289 --> 00:25:46.470 She essentially used her senior status to just 00:25:46.470 --> 00:25:49.170 ignore rules she found pointless. It perfectly 00:25:49.170 --> 00:25:51.490 captures her blend of dedication and defiance. 00:25:51.950 --> 00:25:53.829 She was the rigorous mathematician who became 00:25:53.829 --> 00:25:56.049 the stern admiral, but always with a playful 00:25:56.049 --> 00:25:59.369 disdain for unnecessary restrictions. One colleague 00:25:59.369 --> 00:26:02.150 called her the pirate dying to be released. And 00:26:02.150 --> 00:26:04.930 her favorite part of this post -Navy career wasn't 00:26:04.930 --> 00:26:07.750 the accolades or the salary, but the mentorship. 00:26:08.230 --> 00:26:10.930 She cited training young people as her most important 00:26:10.930 --> 00:26:13.710 accomplishment, second only to the compiler itself. 00:26:14.029 --> 00:26:17.059 Her philosophy for mentorship was simple. but 00:26:17.059 --> 00:26:20.920 so powerful. Encourage action and risk -taking. 00:26:21.180 --> 00:26:23.380 She'd tell them, they come to me, you know, and 00:26:23.380 --> 00:26:25.559 say, do you think we can do this? I say, try 00:26:25.559 --> 00:26:28.619 it. And I back them up. That persistent encouragement 00:26:28.619 --> 00:26:32.259 to take chances is the spirit of innovation she 00:26:32.259 --> 00:26:34.740 instilled in an entire generation of programmers. 00:26:35.289 --> 00:26:37.869 And she employed some ingenious, really memorable 00:26:37.869 --> 00:26:40.970 tools to teach fundamental concepts. The most 00:26:40.970 --> 00:26:43.190 famous, of course, are the nanoseconds. She even 00:26:43.190 --> 00:26:45.250 brought them onto national TV to demonstrate. 00:26:45.650 --> 00:26:47.529 This teaching tool was born out of frustration, 00:26:47.750 --> 00:26:50.089 right? People, particularly decision makers, 00:26:50.250 --> 00:26:52.670 they couldn't grasp the extreme timescales of 00:26:52.670 --> 00:26:55.049 computation and electronic communication. Exactly. 00:26:55.049 --> 00:26:57.490 They would ask her why the satellite link took 00:26:57.490 --> 00:26:59.910 so long to send a message. So she needed a tangible 00:26:59.910 --> 00:27:02.690 analogy. So she carried pieces of wire, each 00:27:02.690 --> 00:27:06.309 one precisely 11 .8 inches long. This length 00:27:06.309 --> 00:27:08.869 represents the distance that light, or an electrical 00:27:08.869 --> 00:27:12.089 signal, travels in a vacuum in one nanosecond, 00:27:12.210 --> 00:27:14.890 one billionth of a second. She called them her 00:27:14.890 --> 00:27:17.670 nanoseconds. It's a genius application of physics 00:27:17.670 --> 00:27:20.559 to engineering. She would use the tiny wire to 00:27:20.559 --> 00:27:22.700 demonstrate why computers needed to be physically 00:27:22.700 --> 00:27:25.460 small. If you wanted a calculation to take less 00:27:25.460 --> 00:27:28.220 than a few nanoseconds, the distance the signal 00:27:28.220 --> 00:27:30.660 had to travel had to be incredibly short. If 00:27:30.660 --> 00:27:32.920 the wires were long, the speed of light, though 00:27:32.920 --> 00:27:35.859 immense, became the limiting factor. To contrast, 00:27:36.099 --> 00:27:38.740 she would then produce this massive coiled length 00:27:38.740 --> 00:27:42.660 of wire, 984 feet long, representing a single 00:27:42.660 --> 00:27:45.259 microsecond. This physical contrast instantly 00:27:45.259 --> 00:27:47.460 explained why minimizing physical distance in 00:27:47.460 --> 00:27:49.779 hardware was paramount for speed. Later, she 00:27:49.779 --> 00:27:51.839 even used tiny grains of pepper to represent 00:27:51.839 --> 00:27:54.579 picoseconds. Trillions of a second. She made 00:27:54.579 --> 00:27:57.299 these abstract concepts physically graspable. 00:27:57.400 --> 00:27:59.440 The other essential anecdote, of course, is the 00:27:59.440 --> 00:28:02.019 origin of the term bug in computing. This happened 00:28:02.019 --> 00:28:04.160 in 1947 while she was working on the Mark II 00:28:04.160 --> 00:28:06.359 computer. Right. The Mark II was malfunctioning. 00:28:06.599 --> 00:28:09.559 Hopper's team traced the issue down and discovered 00:28:09.559 --> 00:28:11.819 that the source of the problem was a physical, 00:28:11.920 --> 00:28:15.980 literal insect. A moth. It had flown into a relay 00:28:15.980 --> 00:28:18.380 and was physically stopping the electromechanical 00:28:18.380 --> 00:28:21.160 flow. They removed the moth and taped it directly 00:28:21.160 --> 00:28:23.799 into the logbook for that day with the classic 00:28:23.799 --> 00:28:27.460 deadpan notation. First actual case of bug being 00:28:27.460 --> 00:28:30.359 found. Now, while electrical engineers had used 00:28:30.359 --> 00:28:32.859 the term bug for technical issues for decades 00:28:32.859 --> 00:28:36.180 before even Thomas Edison used it, Hopper is 00:28:36.180 --> 00:28:39.059 rightly credited with popularizing the term debugging 00:28:39.059 --> 00:28:41.700 within the burgeoning computer industry. And 00:28:41.700 --> 00:28:45.079 that logbook with the actual moth is now preserved 00:28:45.079 --> 00:28:47.779 at the Smithsonian Institution. It's a wonderful 00:28:47.779 --> 00:28:49.980 reminder that sometimes the most profound technical 00:28:49.980 --> 00:28:52.539 concepts have the most humble literal origins. 00:28:52.619 --> 00:28:55.200 All these contributions, the compiler, the military 00:28:55.200 --> 00:28:58.000 standardization, the legendary stories, and the 00:28:58.000 --> 00:29:00.519 fierce mentorship earned her the industry's most 00:29:00.519 --> 00:29:04.390 affectionate title, Grandma Kobol. Grace Hopper 00:29:04.390 --> 00:29:07.490 passed away in 1992, but her impact is not historical. 00:29:07.650 --> 00:29:10.849 It is infrastructural. The sheer volume of awards 00:29:10.849 --> 00:29:13.710 and namesakes demonstrates how deeply her work 00:29:13.710 --> 00:29:16.670 is woven into the fabric of our modern world. 00:29:16.869 --> 00:29:19.950 She received dozens of honorary degrees, but 00:29:19.950 --> 00:29:23.089 let's focus on the highest recognition. Posthumously, 00:29:23.480 --> 00:29:27.039 In 2016, she was awarded the Presidential Medal 00:29:27.039 --> 00:29:30.339 of Freedom by President Barack Obama, the highest 00:29:30.339 --> 00:29:32.700 civilian honor in the United States. During her 00:29:32.700 --> 00:29:34.539 lifetime, she received the National Medal of 00:29:34.539 --> 00:29:38.000 Technology in 1991. And the citation, it sums 00:29:38.000 --> 00:29:40.720 up her entire philosophy beautifully. For her 00:29:40.720 --> 00:29:42.720 pioneering accomplishments in the development 00:29:42.720 --> 00:29:44.859 of computer programming languages that simplified 00:29:44.859 --> 00:29:47.420 computer technology and opened the door to a 00:29:47.420 --> 00:29:50.039 significantly larger universe of users. That 00:29:50.039 --> 00:29:52.519 universe includes every single person who uses 00:29:52.519 --> 00:29:54.519 a computer. computer today for anything other 00:29:54.519 --> 00:29:57.180 than pure research. She was a global figure in 00:29:57.180 --> 00:29:59.680 this emerging field. In 1973, she was the first 00:29:59.680 --> 00:30:02.240 American and the first woman of any nationality 00:30:02.240 --> 00:30:04.160 to be made a distinguished fellow of the British 00:30:04.160 --> 00:30:06.819 Computer Society. And she was inducted into the 00:30:06.819 --> 00:30:09.859 National Women's Hall of Fame in 1994. The Navy, 00:30:10.039 --> 00:30:11.980 which she served for so long, has honored her 00:30:11.980 --> 00:30:14.680 legacy in some really enduring ways. The Arleigh 00:30:14.680 --> 00:30:17.420 Burke -class guided missile destroyer USS Hopper 00:30:17.420 --> 00:30:20.599 was named for her. Affectionately nicknamed Amazing 00:30:20.599 --> 00:30:23.730 Grace. Of course. But perhaps the most telling 00:30:23.730 --> 00:30:26.170 institutional honor is at the U .S. Naval Academy. 00:30:27.170 --> 00:30:29.369 Hopper Hall houses the Cyber Science Department, 00:30:29.710 --> 00:30:32.089 and it holds the distinction of being the very 00:30:32.089 --> 00:30:35.130 first building at any U .S. service academy to 00:30:35.130 --> 00:30:37.410 be named after a woman. It just signifies her 00:30:37.410 --> 00:30:40.009 foundational role in military computation and 00:30:40.009 --> 00:30:41.750 cybersecurity. And the modern infrastructure 00:30:41.750 --> 00:30:44.549 of technology, too. It pays homage. The Cray 00:30:44.549 --> 00:30:48.130 XE6 Hopper supercomputer, the Google undersea 00:30:48.130 --> 00:30:50.690 network cable named Grace Hopper. connecting 00:30:50.690 --> 00:30:53.869 the US, UK and Spain. And most recently, the 00:30:53.869 --> 00:30:57.230 NVIDIA GPU architecture released in 2024 is also 00:30:57.230 --> 00:30:59.869 named Hopper. She is literally the nameplate 00:30:59.869 --> 00:31:01.589 on the machines that are powering the modern 00:31:01.589 --> 00:31:04.009 world. And her commitment to mentorship continues 00:31:04.009 --> 00:31:06.329 through the annual Grace Hopper Celebration of 00:31:06.329 --> 00:31:08.650 Women in Computing. This conference, inspired 00:31:08.650 --> 00:31:11.890 by her tireless advocacy and career, has become 00:31:11.890 --> 00:31:14.069 the world's largest gathering focused on the 00:31:14.069 --> 00:31:16.089 research and career interests of women in the 00:31:16.089 --> 00:31:18.789 technical fields. It's the ultimate continuation 00:31:18.789 --> 00:31:21.509 of her mantra. If the established system tells 00:31:21.509 --> 00:31:24.069 you no, try it anyway and bring others with you. 00:31:24.730 --> 00:31:27.170 So what does this deep dive into Grace Hopper 00:31:27.170 --> 00:31:30.210 mean for you, the learner? When we analyze the 00:31:30.210 --> 00:31:33.130 sources, we see a career defined by astonishing 00:31:33.130 --> 00:31:37.789 technical mastery paired with this... uncompromising 00:31:37.789 --> 00:31:40.309 vision for accessibility. Her defining legacy 00:31:40.309 --> 00:31:43.390 is abstraction. She created the compiler concept 00:31:43.390 --> 00:31:46.329 with the A0 system. She fought for its adoption 00:31:46.329 --> 00:31:49.009 and she ensured its standardization through COBOL. 00:31:49.130 --> 00:31:51.869 She took the arcane and made it clear, expanding 00:31:51.869 --> 00:31:54.369 the potential user base of computers from a few 00:31:54.369 --> 00:31:56.809 hundred experts to literally billions of people. 00:31:57.319 --> 00:31:59.619 And she did all this while pioneering the fight 00:31:59.619 --> 00:32:02.299 for modernization in the Navy for over 42 years, 00:32:02.579 --> 00:32:06.000 constantly running counterclockwise to institutional 00:32:06.000 --> 00:32:08.839 inertia. Her career is the ultimate proof that 00:32:08.839 --> 00:32:10.519 challenging the status quo that we've always 00:32:10.519 --> 00:32:13.099 done it this way mentality is the engine of true 00:32:13.099 --> 00:32:15.920 lasting change. Her gifts to us are knowledge, 00:32:15.980 --> 00:32:19.059 portability, system clarity, and the courage 00:32:19.059 --> 00:32:21.259 to simplify. But here's where it gets really 00:32:21.259 --> 00:32:23.400 interesting, connecting her historical vision 00:32:23.400 --> 00:32:26.099 to our modern reality. We spent considerable 00:32:26.099 --> 00:32:29.980 time discussing how, in the 1970s, Admiral Hopper 00:32:29.980 --> 00:32:32.259 was fiercely advocating for the Defense Department 00:32:32.259 --> 00:32:35.759 to switch away from large, centralized mainframe 00:32:35.759 --> 00:32:37.980 computer systems. And instead move toward distributed 00:32:37.980 --> 00:32:40.740 networks. She prized resilience and efficiency 00:32:40.740 --> 00:32:44.079 through decentralization. She predicted the systemic 00:32:44.079 --> 00:32:46.839 risk inherent in putting all computational power 00:32:46.839 --> 00:32:49.470 in one single basket. Advocating for networks 00:32:49.470 --> 00:32:52.630 where users had local access to common shared 00:32:52.630 --> 00:32:56.190 databases across multiple nodes. Given that foresight 00:32:56.190 --> 00:32:58.130 and given that she was the woman who popularized 00:32:58.130 --> 00:33:00.789 the bug found in a physical computer relay, what 00:33:00.789 --> 00:33:02.849 would Admiral Hopper, the advocate for decentralized 00:33:02.849 --> 00:33:05.970 power and user -friendly access, say about the 00:33:05.970 --> 00:33:08.700 landscape we navigate today? Would she be concerned 00:33:08.700 --> 00:33:10.759 that the vast majority of our digital lives, 00:33:10.839 --> 00:33:13.380 our data, our communications, our commerce is 00:33:13.380 --> 00:33:15.279 now controlled and funneled through the massive 00:33:15.279 --> 00:33:18.039 centralized server farms of just a handful of 00:33:18.039 --> 00:33:20.359 massive tech giants? That structure presents 00:33:20.359 --> 00:33:22.900 the very single point of failure she warned the 00:33:22.900 --> 00:33:26.119 Navy against decades ago. Only now that single 00:33:26.119 --> 00:33:28.420 point of failure is global. So we leave you to 00:33:28.420 --> 00:33:31.890 consider. Would Grandma Coble see today's highly 00:33:31.890 --> 00:33:34.789 centralized digital infrastructure as the triumph 00:33:34.789 --> 00:33:37.490 of efficiency or a fundamental architectural 00:33:37.490 --> 00:33:40.069 bug that threatens the resiliency and freedom 00:33:40.069 --> 00:33:43.289 of the entire information age? Think about that. 00:33:43.410 --> 00:33:45.630 Thank you for joining us for the Deep Dive. We 00:33:45.630 --> 00:33:47.369 hope this comprehensive knowledge serves you 00:33:47.369 --> 00:33:48.230 well. Until next time.