WEBVTT

1
00:00:01.080 --> 00:00:02.960
<v Speaker 1>How'd you like to listen to dot net Rocks with

2
00:00:03.040 --> 00:00:03.799
<v Speaker 1>no ads?

3
00:00:04.440 --> 00:00:04.799
<v Speaker 2>Easy?

4
00:00:05.320 --> 00:00:08.560
<v Speaker 1>Become a patron for just five dollars a month. You

5
00:00:08.599 --> 00:00:11.320
<v Speaker 1>get access to a private RSS feed where all the

6
00:00:11.359 --> 00:00:14.560
<v Speaker 1>shows have no ads. Twenty dollars a month, we'll get

7
00:00:14.599 --> 00:00:17.679
<v Speaker 1>you that and a special dot net Rocks patron mug.

8
00:00:18.160 --> 00:00:35.000
<v Speaker 1>Sign up now at Patreon dot dot netroocks dot com. Hey,

9
00:00:35.079 --> 00:00:38.439
<v Speaker 1>welcome back to dot net Rocks episode nineteen hundred and

10
00:00:38.560 --> 00:00:41.399
<v Speaker 1>ninety nine. I'm Carl Franklin and I'm Richard Campbell. We

11
00:00:41.520 --> 00:00:43.359
<v Speaker 1>got some stories for you today, don't we.

12
00:00:43.520 --> 00:00:45.960
<v Speaker 2>No, boy, Well, we did a while to figure out

13
00:00:45.960 --> 00:00:48.359
<v Speaker 2>how we're going to do this show. Yeah, I really

14
00:00:48.359 --> 00:00:50.320
<v Speaker 2>did want to talk about Y two K, just because

15
00:00:50.399 --> 00:00:52.920
<v Speaker 2>it was a big part of my life, sure, dealing

16
00:00:52.960 --> 00:00:56.000
<v Speaker 2>with it, and I think, you know, twenty seven years on,

17
00:00:57.039 --> 00:00:59.479
<v Speaker 2>people forgotten or didn't know. You know, if you came

18
00:00:59.479 --> 00:01:01.719
<v Speaker 2>to the industry later, you just don't know what we did.

19
00:01:01.840 --> 00:01:04.040
<v Speaker 2>So I thought it'd be a perfect time to sort

20
00:01:04.040 --> 00:01:04.920
<v Speaker 2>of dig into all that.

21
00:01:05.120 --> 00:01:07.680
<v Speaker 1>Yeah, but we got some stuff to do. This being

22
00:01:07.760 --> 00:01:11.799
<v Speaker 1>nineteen ninety nine, let's talk about what happened that year. Well,

23
00:01:12.439 --> 00:01:15.239
<v Speaker 1>NATO bombing of Yugoslavia was a big story for sure.

24
00:01:15.840 --> 00:01:18.480
<v Speaker 2>Yeah, that's first time NATO had ever done anything like that.

25
00:01:19.040 --> 00:01:22.120
<v Speaker 1>Right, and it was to stop ethnic cleansing in Kosovo,

26
00:01:22.200 --> 00:01:25.159
<v Speaker 1>which you know, we kind of stood by and watched

27
00:01:25.200 --> 00:01:28.640
<v Speaker 1>all this horror play out and finally said enough of that.

28
00:01:28.920 --> 00:01:31.799
<v Speaker 2>Yeah, slow Adameinlosovich gets arrested. At the beginning of the

29
00:01:31.799 --> 00:01:33.840
<v Speaker 2>whole World Court. There's a lot of things that happened

30
00:01:33.879 --> 00:01:34.799
<v Speaker 2>in that. Yeah.

31
00:01:34.879 --> 00:01:37.680
<v Speaker 1>Of course the y two K bug Pananic, which we'll

32
00:01:37.680 --> 00:01:41.560
<v Speaker 1>talk about here. Bill Clinton was impeached, Yeah, having too

33
00:01:41.640 --> 00:01:42.959
<v Speaker 1>much fun with a cigar or.

34
00:01:42.879 --> 00:01:46.000
<v Speaker 2>Something like that, perhaps well, but was ultimately acquitted by

35
00:01:46.000 --> 00:01:46.400
<v Speaker 2>the Senate.

36
00:01:46.480 --> 00:01:51.200
<v Speaker 1>Yeah. Another big one, sad the Columbine High School masker,

37
00:01:51.359 --> 00:01:54.799
<v Speaker 1>which really was one of the first of those sort

38
00:01:54.799 --> 00:01:55.680
<v Speaker 1>of the things.

39
00:01:56.000 --> 00:01:59.359
<v Speaker 2>Yeah, I think, I mean, it'd happened before, but maybe

40
00:01:59.400 --> 00:02:02.560
<v Speaker 2>it's because the was around that the visibility of it changed.

41
00:02:02.799 --> 00:02:09.000
<v Speaker 1>Yeah. East Timor Indonesia voted for independence from Indonesia and

42
00:02:09.120 --> 00:02:12.159
<v Speaker 1>there was some violent unrest and the UN got involved

43
00:02:12.159 --> 00:02:15.599
<v Speaker 1>there too. The euro was introduced in nineteen ninety nine. Yeah,

44
00:02:15.639 --> 00:02:16.680
<v Speaker 1>I forgot about that.

45
00:02:16.800 --> 00:02:18.919
<v Speaker 2>It's not that long ago, is it. Yeah, it's the

46
00:02:18.919 --> 00:02:19.479
<v Speaker 2>beginning of that.

47
00:02:19.879 --> 00:02:24.280
<v Speaker 1>Yep, there was an egypt Air Flight nine ninety crash.

48
00:02:24.560 --> 00:02:28.039
<v Speaker 1>Boeing seven sixty seven crashed into the Atlantic Ocean two

49
00:02:28.120 --> 00:02:33.000
<v Speaker 1>hundred and seventeen perished, and that caused an international raw.

50
00:02:33.280 --> 00:02:35.800
<v Speaker 2>Yeah, there was concern that it was deliberate.

51
00:02:35.960 --> 00:02:40.639
<v Speaker 1>Yep, vlad Putin becomes Prime Minister of Russia.

52
00:02:40.280 --> 00:02:43.360
<v Speaker 2>When Boris Yeltsin resigns. Well, he was already prime minister,

53
00:02:43.479 --> 00:02:47.639
<v Speaker 2>but then Yeltsin resigns as president, so Putin gets to

54
00:02:47.639 --> 00:02:51.439
<v Speaker 2>be both. Yeah, at least temporarily anyway, and never leaves office.

55
00:02:51.560 --> 00:02:51.800
<v Speaker 3>Yeah.

56
00:02:51.840 --> 00:02:54.080
<v Speaker 2>Basically, you're right, you're.

57
00:02:53.960 --> 00:02:57.639
<v Speaker 1>Going to talk about Mars Climate orbiterter. I'm sure, yes,

58
00:02:58.000 --> 00:02:59.759
<v Speaker 1>So why don't we switch over to space.

59
00:03:00.120 --> 00:03:04.680
<v Speaker 2>Sure, so let's start with polar Lander. So there's a

60
00:03:04.680 --> 00:03:06.400
<v Speaker 2>bunch of Mars missions in ninety nine and they all

61
00:03:06.400 --> 00:03:11.560
<v Speaker 2>go badly. Polar Lander launches in January, arrives in December,

62
00:03:11.599 --> 00:03:15.479
<v Speaker 2>and on its way down they suddenly lose contact with it.

63
00:03:15.479 --> 00:03:18.680
<v Speaker 2>It takes a we've never really found out exactly what

64
00:03:18.719 --> 00:03:22.800
<v Speaker 2>happened to polar Lander, but in the post lost testing

65
00:03:23.240 --> 00:03:26.319
<v Speaker 2>they come to the realization that in the final stages

66
00:03:26.360 --> 00:03:29.520
<v Speaker 2>of its landing, after it's gone through aerobraking in the

67
00:03:29.560 --> 00:03:31.800
<v Speaker 2>shell and all this stuff, and it's on its engines.

68
00:03:32.520 --> 00:03:35.919
<v Speaker 2>There's a point of literally less than a minute from

69
00:03:36.000 --> 00:03:39.360
<v Speaker 2>landing where it extends its legs and there's a sensor,

70
00:03:39.479 --> 00:03:42.439
<v Speaker 2>there's a contact sensor on those legs that helps tell

71
00:03:42.560 --> 00:03:45.759
<v Speaker 2>when it's actually landed, and that shuts the engines off. Well,

72
00:03:45.800 --> 00:03:48.360
<v Speaker 2>the shock of extending the legs shakes the sensor enough

73
00:03:48.400 --> 00:03:50.479
<v Speaker 2>that it thinks it's landed, so it shuts the engines

74
00:03:50.520 --> 00:03:52.960
<v Speaker 2>off one hundred and fifty feet in the air. Yikes,

75
00:03:53.080 --> 00:03:55.960
<v Speaker 2>bumber bummer. Can't blame it on the Y two K bug,

76
00:03:56.000 --> 00:03:58.639
<v Speaker 2>can we? No? And although the other Mars went out

77
00:03:58.639 --> 00:04:00.439
<v Speaker 2>of the way as well, which is in September where

78
00:04:00.439 --> 00:04:06.479
<v Speaker 2>the Mars Climate orbiter and using the wrong type of

79
00:04:06.560 --> 00:04:10.680
<v Speaker 2>numbers using Newton's instead of foot pounds, does not do

80
00:04:10.840 --> 00:04:13.599
<v Speaker 2>its burn correctly to insert itself into the orbit of

81
00:04:13.599 --> 00:04:16.279
<v Speaker 2>Mars and instead flies directly into Mars and burns up.

82
00:04:16.319 --> 00:04:18.279
<v Speaker 1>So after this, we're a bunch of programmers at NASA.

83
00:04:18.399 --> 00:04:21.720
<v Speaker 2>Let go there was You know. The sad part is

84
00:04:21.759 --> 00:04:23.279
<v Speaker 2>that it's not the only one lost for the sort

85
00:04:23.279 --> 00:04:24.319
<v Speaker 2>of thing. I think it was one of the first

86
00:04:24.360 --> 00:04:27.160
<v Speaker 2>times they dealt with They got the numbers wrong. What's

87
00:04:27.199 --> 00:04:31.639
<v Speaker 2>funny is that both those missions where reflights of instruments

88
00:04:31.639 --> 00:04:34.199
<v Speaker 2>from another other lost flights, and then they two were

89
00:04:34.240 --> 00:04:37.279
<v Speaker 2>lost although there were other flights. Getting to Mars is hard,

90
00:04:37.600 --> 00:04:39.600
<v Speaker 2>two ways about it. Yeah, So let's get on more

91
00:04:39.639 --> 00:04:44.240
<v Speaker 2>of the good news parts. In February, the Stardust Comet

92
00:04:44.319 --> 00:04:48.879
<v Speaker 2>Sample Return Mission launches. So this is a small vehicle

93
00:04:48.959 --> 00:04:52.800
<v Speaker 2>designed to intercept a comet called eighty one P Wild

94
00:04:53.519 --> 00:04:56.680
<v Speaker 2>and it will actually put a great fly, yeah, fly

95
00:04:56.759 --> 00:05:00.800
<v Speaker 2>behind the comet into its coma the tail coming out

96
00:05:00.839 --> 00:05:03.920
<v Speaker 2>the back, extend these little platters to collect the material

97
00:05:04.120 --> 00:05:07.759
<v Speaker 2>the stardust, and then by two thousand and six it'll

98
00:05:07.800 --> 00:05:09.920
<v Speaker 2>return those samples safely to Earth.

99
00:05:10.040 --> 00:05:11.519
<v Speaker 1>That's got to be a sturdy platter.

100
00:05:11.680 --> 00:05:11.920
<v Speaker 2>Yeah.

101
00:05:12.279 --> 00:05:15.720
<v Speaker 1>You know, if you think about trying to catch something

102
00:05:15.720 --> 00:05:17.680
<v Speaker 1>in a hurricane with a paper plate, you know.

103
00:05:17.680 --> 00:05:22.000
<v Speaker 2>Basically there's this error. This is gel that stuff gets

104
00:05:22.000 --> 00:05:25.560
<v Speaker 2>embedded in. It was very clever design. The Cassini mission

105
00:05:25.720 --> 00:05:28.399
<v Speaker 2>is on its way to Jupiter, and in June it

106
00:05:28.399 --> 00:05:30.759
<v Speaker 2>does a fly by a Venus to get a gravitational

107
00:05:30.800 --> 00:05:32.000
<v Speaker 2>assistant help them get out there.

108
00:05:33.000 --> 00:05:34.160
<v Speaker 1>Didn't it take pictures too?

109
00:05:34.519 --> 00:05:40.199
<v Speaker 2>Yeah? Many times? Remember Venus Yeah. It was a phenomenal machine, massive,

110
00:05:40.279 --> 00:05:42.040
<v Speaker 2>right size of a school box. One of the very

111
00:05:42.079 --> 00:05:46.319
<v Speaker 2>last gigantic observatories. We've not built anything like that since.

112
00:05:47.360 --> 00:05:54.279
<v Speaker 2>Speaking of gigantic observatories, the Chandra X ray Observatory was

113
00:05:54.319 --> 00:05:57.399
<v Speaker 2>flown on the Columbia Space Shuttle. Aileen Collins was the

114
00:05:57.399 --> 00:06:00.519
<v Speaker 2>first shuttle commander. This was the heaviest payload ever lifted

115
00:06:00.519 --> 00:06:04.399
<v Speaker 2>by shuttles fifty thousand pounds wow, and that it was

116
00:06:04.639 --> 00:06:07.879
<v Speaker 2>to be clear, it was successful. Chandra is still operational today,

117
00:06:08.000 --> 00:06:10.600
<v Speaker 2>provided it continues to get funding. But a lot of

118
00:06:10.680 --> 00:06:15.600
<v Speaker 2>scary stuff happened on this flight. A few seconds after

119
00:06:15.639 --> 00:06:19.360
<v Speaker 2>the launch, there was a pin in the right engine

120
00:06:19.360 --> 00:06:23.800
<v Speaker 2>that came loose and tore into the side of the bell,

121
00:06:24.319 --> 00:06:27.519
<v Speaker 2>damaging some cooling lines that have liquid hydrogen flowing through them.

122
00:06:27.600 --> 00:06:30.480
<v Speaker 2>That's not good, not enough to cause an abard, of course,

123
00:06:30.600 --> 00:06:33.439
<v Speaker 2>there's no real good abort modes, but it does mean

124
00:06:33.439 --> 00:06:36.959
<v Speaker 2>that they're losing fuel, and so the computers automatically compensate

125
00:06:37.040 --> 00:06:40.600
<v Speaker 2>by throttling that engine up further, running it hotter, which

126
00:06:40.680 --> 00:06:43.800
<v Speaker 2>runs it out of fuel even faster. It'll end up

127
00:06:43.800 --> 00:06:46.560
<v Speaker 2>getting to orbit successfully, just a lower orbit than planned,

128
00:06:46.759 --> 00:06:48.920
<v Speaker 2>but that's not the only thing that happens with the engines.

129
00:06:49.279 --> 00:06:53.040
<v Speaker 2>An electrical short happens. It takes out two of the

130
00:06:53.680 --> 00:06:55.839
<v Speaker 2>engine controllers, one for the center engine and one for

131
00:06:55.879 --> 00:06:59.079
<v Speaker 2>the right engine. Fortunately, both their backups kick in. At

132
00:06:59.079 --> 00:07:01.759
<v Speaker 2>that point there are no failure modes left. If anything

133
00:07:01.839 --> 00:07:04.160
<v Speaker 2>else had gone wrong, they would have had to do

134
00:07:04.399 --> 00:07:08.279
<v Speaker 2>an abort that had been designed but never tested.

135
00:07:08.199 --> 00:07:10.959
<v Speaker 1>And they would have to use thrusters only, right, I

136
00:07:11.000 --> 00:07:11.480
<v Speaker 1>mean the worst.

137
00:07:12.639 --> 00:07:14.800
<v Speaker 2>Yeah, that's it. You know, if you're down to minimum

138
00:07:14.839 --> 00:07:17.040
<v Speaker 2>life support that at this point you're not quite yet

139
00:07:17.040 --> 00:07:21.279
<v Speaker 2>in orbit, but you're so there's only two failure modes possible.

140
00:07:21.720 --> 00:07:24.160
<v Speaker 2>Presumably your past the solids. The salids are gone, so

141
00:07:24.199 --> 00:07:26.480
<v Speaker 2>you're not going to have a challenger issue, but you

142
00:07:26.519 --> 00:07:28.120
<v Speaker 2>don't have enough thrust to make it to orbit. So

143
00:07:28.160 --> 00:07:32.600
<v Speaker 2>the two choices are either what they call a transitlandic aboart,

144
00:07:32.800 --> 00:07:35.519
<v Speaker 2>where you would continue running the engine enough that you

145
00:07:35.560 --> 00:07:38.759
<v Speaker 2>can make it across probably Despain. There Goza where they

146
00:07:38.759 --> 00:07:41.319
<v Speaker 2>had a runaway big enough for shuttle, dump the tank

147
00:07:41.839 --> 00:07:45.240
<v Speaker 2>and do an emergency landing of the shuttle there. Yeah,

148
00:07:45.360 --> 00:07:47.800
<v Speaker 2>we should be great, everybody's safe. Then payload makes it back.

149
00:07:47.839 --> 00:07:49.680
<v Speaker 2>There's a question because it was the heaviest mission ever,

150
00:07:49.839 --> 00:07:52.040
<v Speaker 2>Like what that would that would do? Yeah, And also

151
00:07:53.480 --> 00:07:55.560
<v Speaker 2>there was a big question about how the heck to

152
00:07:55.600 --> 00:07:58.560
<v Speaker 2>get the shuttle back after an abort like that, because

153
00:07:58.759 --> 00:08:00.759
<v Speaker 2>you can find the seven forty seven over, but the

154
00:08:00.759 --> 00:08:04.079
<v Speaker 2>equipment to lift it is so large. The more practical

155
00:08:04.120 --> 00:08:07.319
<v Speaker 2>thing ultimately to do would be to actually transport it

156
00:08:07.439 --> 00:08:09.680
<v Speaker 2>to a dock and put it on aircraft carrier to

157
00:08:09.680 --> 00:08:13.959
<v Speaker 2>be brought back. Wow, that's not the crazy abort mode, Carl.

158
00:08:14.160 --> 00:08:17.920
<v Speaker 2>Here's the crazy abort mode. It's it's called the return

159
00:08:18.040 --> 00:08:23.079
<v Speaker 2>to landing abort mode. So get this. If your boosters,

160
00:08:23.120 --> 00:08:24.879
<v Speaker 2>you're gone. You haven't got enough thrust to make it

161
00:08:24.879 --> 00:08:32.279
<v Speaker 2>into orbit, so you underpower turn the shuttle around and

162
00:08:32.440 --> 00:08:37.279
<v Speaker 2>fly backwards to decelerate the vehicle and try and get

163
00:08:37.320 --> 00:08:42.600
<v Speaker 2>it back to Kennedy. Wow. This only was attempted in simulators,

164
00:08:42.600 --> 00:08:45.559
<v Speaker 2>and almost all simulator attempts failed. Once in a while,

165
00:08:45.679 --> 00:08:48.080
<v Speaker 2>somebody could manage to pull it off to actually be

166
00:08:48.159 --> 00:08:50.840
<v Speaker 2>able to land it. So I don't remember all this drama.

167
00:08:51.200 --> 00:08:53.519
<v Speaker 2>They never well, none of this happened. None of it

168
00:08:53.600 --> 00:08:57.840
<v Speaker 2>happened because ultimately they made it over. These were contingencies.

169
00:08:58.080 --> 00:09:01.080
<v Speaker 1>Oh, Okay, these were potential agency if they didn't have

170
00:09:01.200 --> 00:09:02.399
<v Speaker 1>enough thrust to make it back.

171
00:09:02.679 --> 00:09:04.440
<v Speaker 2>This is what they were going These are the things

172
00:09:04.480 --> 00:09:07.519
<v Speaker 2>they were going to need to do. So yeah, Columbia

173
00:09:07.559 --> 00:09:10.519
<v Speaker 2>came very close to that particular occasion. In May there

174
00:09:10.600 --> 00:09:13.519
<v Speaker 2>was the Discovery went to the space station to bring

175
00:09:13.559 --> 00:09:15.159
<v Speaker 2>cargo up for the ISS, which at this point is

176
00:09:15.200 --> 00:09:19.879
<v Speaker 2>only two modules, Aazaria and Unity. And in December there

177
00:09:19.960 --> 00:09:24.240
<v Speaker 2>is a Hubble servicing mission off of Discovery. This had

178
00:09:24.279 --> 00:09:27.159
<v Speaker 2>been regally been scheduled for two thousand, but were they

179
00:09:27.200 --> 00:09:30.159
<v Speaker 2>already had three gyros failed on Hubble at this point

180
00:09:30.200 --> 00:09:32.279
<v Speaker 2>in ninety nine, and so they went up to bring

181
00:09:32.279 --> 00:09:34.519
<v Speaker 2>them a new set of six gyro, some redundancy, and

182
00:09:34.559 --> 00:09:39.159
<v Speaker 2>a new fine guidance computer some other two nups as well. Also,

183
00:09:39.600 --> 00:09:42.159
<v Speaker 2>this is the year that China flies the first shen

184
00:09:42.279 --> 00:09:46.039
<v Speaker 2>Zou vehicle. This is their manned space program. All this

185
00:09:46.080 --> 00:09:48.799
<v Speaker 2>particular test was not manned. It's a derivative of Soyu's

186
00:09:48.799 --> 00:09:50.559
<v Speaker 2>a bit bigger with more modern equipment in it. And

187
00:09:50.799 --> 00:09:53.639
<v Speaker 2>so I brought it up because they'll fly their first

188
00:09:53.679 --> 00:09:55.080
<v Speaker 2>man mission in two thousand and three. And this is

189
00:09:55.080 --> 00:09:57.840
<v Speaker 2>the beginning of manned flight by the Chinese, which you

190
00:09:57.879 --> 00:10:00.440
<v Speaker 2>know here in twenty twenty six they have a space station.

191
00:10:01.039 --> 00:10:03.679
<v Speaker 2>It is continuously occupied. Very cool. All right, Moving off

192
00:10:03.720 --> 00:10:09.120
<v Speaker 2>from space, let's talk about computing. AOL completes the acquisition

193
00:10:09.200 --> 00:10:14.799
<v Speaker 2>of Netscape. Hooray, hooray. It's you know, it's twenty ninety nine.

194
00:10:14.879 --> 00:10:17.759
<v Speaker 1>Now everybody's everybody's got mail now.

195
00:10:18.240 --> 00:10:22.639
<v Speaker 2>Well but more saliently like that was the IPO Darling

196
00:10:22.799 --> 00:10:25.240
<v Speaker 2>just a few years earlier, and now they're broke and

197
00:10:25.320 --> 00:10:28.799
<v Speaker 2>have been acquired for pennies on the dollar. So you know,

198
00:10:28.879 --> 00:10:30.840
<v Speaker 2>we see the end of the dot com boom here

199
00:10:30.879 --> 00:10:33.120
<v Speaker 2>where the original catalyst of it is kind of tank.

200
00:10:34.399 --> 00:10:39.240
<v Speaker 2>In June, Sean Fanning and Sean Parker release Napster. Yea.

201
00:10:39.360 --> 00:10:44.000
<v Speaker 1>As we talked about this last last year nineteen ninety eight,

202
00:10:44.039 --> 00:10:45.440
<v Speaker 1>there was the beginnings of that.

203
00:10:45.639 --> 00:10:47.639
<v Speaker 2>Yeah. Of course, by the end of the year, the

204
00:10:47.720 --> 00:10:49.840
<v Speaker 2>RI will be pursuing them because remember we had the

205
00:10:49.919 --> 00:10:54.399
<v Speaker 2>DCMA Act is already in play, so they're not putting

206
00:10:54.440 --> 00:10:57.080
<v Speaker 2>up the CMA as what the Digital Millennium Copyright Act

207
00:10:57.080 --> 00:11:01.200
<v Speaker 2>digital copyright yeah, which specifically says, hey, you know, you

208
00:11:01.240 --> 00:11:03.720
<v Speaker 2>don't have to control the content per se. And remember

209
00:11:04.000 --> 00:11:06.879
<v Speaker 2>what Napster actually is is a file sharing strategy. Now

210
00:11:06.879 --> 00:11:09.360
<v Speaker 2>that they have the files that you can it's just

211
00:11:09.399 --> 00:11:12.399
<v Speaker 2>sharing where files are so that you know they're making

212
00:11:12.440 --> 00:11:14.919
<v Speaker 2>the argument. It's like, it's not us, but that's not

213
00:11:14.960 --> 00:11:17.720
<v Speaker 2>going to Google. Google gets their first round of funding

214
00:11:17.759 --> 00:11:19.720
<v Speaker 2>and the site is up, so the beginning of their

215
00:11:19.759 --> 00:11:24.399
<v Speaker 2>search engine is starting to fly. Blogging already exists, but

216
00:11:24.480 --> 00:11:27.080
<v Speaker 2>it's really only for people who are very web savvy.

217
00:11:27.879 --> 00:11:32.840
<v Speaker 2>But Netscape releases RSS zero point nine zero, which they

218
00:11:32.919 --> 00:11:36.240
<v Speaker 2>call the mean RDF side summary. It's really I think,

219
00:11:36.279 --> 00:11:39.399
<v Speaker 2>with titles and links in it for you know, getting

220
00:11:39.440 --> 00:11:42.679
<v Speaker 2>summaries of data to auditional reading, and this beginning of

221
00:11:42.759 --> 00:11:45.159
<v Speaker 2>sort of the blog engine. Dave Weiner will take a

222
00:11:45.159 --> 00:11:47.759
<v Speaker 2>hold of that specification and improve it substantially with additional

223
00:11:47.759 --> 00:11:49.360
<v Speaker 2>information in XML and so forth.

224
00:11:49.399 --> 00:11:53.639
<v Speaker 1>I remember we interviewed Robert Scobel about all that stuff

225
00:11:53.720 --> 00:11:56.440
<v Speaker 1>much later, of course, yeah, later on, but this, but

226
00:11:56.519 --> 00:11:59.000
<v Speaker 1>he was he was one of the first big blog advocates.

227
00:11:59.080 --> 00:12:01.639
<v Speaker 2>Yeah, it was great and still is great, I know, honestly.

228
00:12:02.240 --> 00:12:04.679
<v Speaker 2>Even more relevantly, in ninety nine, a company called Pyra

229
00:12:04.759 --> 00:12:07.840
<v Speaker 2>Labs launches a site called Blogger where you don't need

230
00:12:07.879 --> 00:12:10.200
<v Speaker 2>to know anything about HTML and so forth. You literally

231
00:12:10.440 --> 00:12:13.000
<v Speaker 2>sign up an account, create a blog from them, and

232
00:12:13.080 --> 00:12:15.600
<v Speaker 2>just write so you know, beginning of all of those things.

233
00:12:16.200 --> 00:12:19.080
<v Speaker 2>Over on the Microsoft side, I E five is released,

234
00:12:19.120 --> 00:12:21.279
<v Speaker 2>announced as I E four done right.

235
00:12:21.879 --> 00:12:27.879
<v Speaker 4>Yeah, we see pre release versions a euphour, yah boy boy,

236
00:12:28.799 --> 00:12:32.559
<v Speaker 4>we see pre release that's over now, thank god.

237
00:12:33.200 --> 00:12:36.240
<v Speaker 2>We see pre release versions of Windows two thousand, including

238
00:12:36.240 --> 00:12:41.679
<v Speaker 2>our first look at active directory. And in November, Microsoft

239
00:12:41.720 --> 00:12:44.399
<v Speaker 2>is can declare the pernicious monopoly by the Department of Justice.

240
00:12:44.519 --> 00:12:47.639
<v Speaker 2>Na Michel kick off a whole bunch of fun. A

241
00:12:47.679 --> 00:12:51.759
<v Speaker 2>little company you may have heard of called Nvidia Releases

242
00:12:51.759 --> 00:12:54.080
<v Speaker 2>is one of the first consumer GPUs ever. It's called

243
00:12:54.080 --> 00:12:55.000
<v Speaker 2>the g Force.

244
00:12:54.799 --> 00:12:59.240
<v Speaker 1>Twent fifty six, and they will IPO that year if

245
00:12:59.240 --> 00:13:01.639
<v Speaker 1>they only knew that graphics was not going to be

246
00:13:01.679 --> 00:13:02.519
<v Speaker 1>their cash cow.

247
00:13:03.080 --> 00:13:05.159
<v Speaker 2>Well at least not right now, you know, not now,

248
00:13:05.240 --> 00:13:07.159
<v Speaker 2>but who knows what's gonna be Like a little while later,

249
00:13:08.200 --> 00:13:14.000
<v Speaker 2>Over in Japan, NTT DoCoMo releases the specifications for mobile data,

250
00:13:14.039 --> 00:13:18.440
<v Speaker 2>including a simpl fied HTML. It's only in japad Over

251
00:13:18.519 --> 00:13:21.840
<v Speaker 2>in the US, it's the Consumer Electronics Show, the first

252
00:13:21.960 --> 00:13:25.039
<v Speaker 2>TVO Wow Divo.

253
00:13:25.000 --> 00:13:27.679
<v Speaker 1>That t I remember one of our first conversations with

254
00:13:27.720 --> 00:13:31.039
<v Speaker 1>you was about TVO and you said that in Canada,

255
00:13:31.080 --> 00:13:33.399
<v Speaker 1>TVO doesn't get metadata.

256
00:13:32.799 --> 00:13:36.600
<v Speaker 2>Like you can't use it. No, yeah, I used. I

257
00:13:36.639 --> 00:13:40.039
<v Speaker 2>had to replay TV with some and DNS redirects.

258
00:13:40.159 --> 00:13:42.639
<v Speaker 1>But yeah, yeah, because you couldn't get metadata in Canada

259
00:13:42.679 --> 00:13:43.399
<v Speaker 1>for some reason.

260
00:13:43.279 --> 00:13:47.000
<v Speaker 2>Right, Yeah, it just never was supported. The I Triple

261
00:13:47.039 --> 00:13:50.519
<v Speaker 2>E combines their specification known as a TOO two dot

262
00:13:50.559 --> 00:13:54.200
<v Speaker 2>one one B alongside of a security protocol a bad

263
00:13:54.200 --> 00:13:59.279
<v Speaker 2>one called web and calls it Wi Fi. So the

264
00:13:59.320 --> 00:14:05.200
<v Speaker 2>rebrand that name never stick, never got job. A little

265
00:14:05.240 --> 00:14:08.360
<v Speaker 2>company called M Systems. We now notice sand Disc releases

266
00:14:08.399 --> 00:14:10.240
<v Speaker 2>the first USB flash drives.

267
00:14:10.600 --> 00:14:12.200
<v Speaker 1>Wow, and Kyo.

268
00:14:12.080 --> 00:14:15.720
<v Speaker 2>Sera releases their visual phone known as the VP two ten,

269
00:14:15.759 --> 00:14:18.399
<v Speaker 2>which is the first consumer phone with a camera on

270
00:14:18.519 --> 00:14:21.360
<v Speaker 2>board with a whole one hundred and ten thousand pixels.

271
00:14:21.480 --> 00:14:24.559
<v Speaker 2>What a great idea that was. Yeah. Two more pieces

272
00:14:24.559 --> 00:14:26.200
<v Speaker 2>of software to talk about and then we can move on.

273
00:14:26.399 --> 00:14:29.960
<v Speaker 2>The first is SETI at Home. Oh yeah, another thing

274
00:14:30.000 --> 00:14:32.159
<v Speaker 2>we talked about back in the day. All right, So

275
00:14:32.240 --> 00:14:34.840
<v Speaker 2>there's a great joke that you did on one of

276
00:14:34.879 --> 00:14:36.960
<v Speaker 2>your first shows. Maybe it was the show you were

277
00:14:36.960 --> 00:14:40.360
<v Speaker 2>a guest on where you were running SETI at home

278
00:14:40.399 --> 00:14:45.600
<v Speaker 2>work units to raise the CPU so that your water

279
00:14:45.799 --> 00:14:52.360
<v Speaker 2>cooled connected coffee or tea warmer. Yeah, would I would

280
00:14:52.440 --> 00:14:54.320
<v Speaker 2>warm your tea. My coffee is getting cold. I got

281
00:14:54.320 --> 00:14:58.000
<v Speaker 2>to run some SETI at homework units. Yeah, I had

282
00:14:58.000 --> 00:15:00.519
<v Speaker 2>a little of course, it did early water cooling because

283
00:15:00.519 --> 00:15:03.519
<v Speaker 2>I'm an idiot and I had this. I found this

284
00:15:03.600 --> 00:15:05.480
<v Speaker 2>plate that was designed for sitting coffee on that had

285
00:15:05.480 --> 00:15:07.759
<v Speaker 2>the water loop in it. And yeah, you could make

286
00:15:07.759 --> 00:15:10.120
<v Speaker 2>the machine horder if you ran it hard enough. And

287
00:15:10.159 --> 00:15:12.240
<v Speaker 2>the last piece of software I talk about is the

288
00:15:12.279 --> 00:15:16.000
<v Speaker 2>Melissa virus. Oh yeah, written by David Smith, and it

289
00:15:16.799 --> 00:15:19.120
<v Speaker 2>is certainly not the first virus. It was just a propagator,

290
00:15:19.159 --> 00:15:21.840
<v Speaker 2>no payload. It was an innocent time back then. But

291
00:15:22.120 --> 00:15:24.480
<v Speaker 2>with the innovation that Smith came up with was it

292
00:15:24.519 --> 00:15:27.519
<v Speaker 2>was an email propagator. So when you opened an email,

293
00:15:28.480 --> 00:15:30.480
<v Speaker 2>it would run a macro that would go through your

294
00:15:30.559 --> 00:15:33.120
<v Speaker 2>entire contact list and email everybody in your contact list.

295
00:15:33.200 --> 00:15:36.320
<v Speaker 2>And it was huge. It went everywhere.

296
00:15:36.440 --> 00:15:40.159
<v Speaker 1>I don't recall getting spammed by it. So he avoid

297
00:15:40.240 --> 00:15:43.919
<v Speaker 1>eye one. Yeah that's that's did you get it? I

298
00:15:44.000 --> 00:15:44.639
<v Speaker 1>think I did.

299
00:15:44.799 --> 00:15:47.480
<v Speaker 2>I think we did see that one go through because

300
00:15:47.480 --> 00:15:50.440
<v Speaker 2>it crippled mail servers, right, just it would drop mail

301
00:15:50.480 --> 00:15:52.879
<v Speaker 2>service to its knees because all of you, suddenly, each

302
00:15:52.919 --> 00:15:57.000
<v Speaker 2>person you know, opening one email sends five hundred more

303
00:15:57.200 --> 00:15:59.480
<v Speaker 2>right hanging on the sides of the contact list. And

304
00:15:59.519 --> 00:16:01.639
<v Speaker 2>so the real problem is if you were a popular

305
00:16:01.679 --> 00:16:04.600
<v Speaker 2>contact and I was, you got a lot of those emails,

306
00:16:04.679 --> 00:16:06.080
<v Speaker 2>you got it, and then you know, I think I

307
00:16:06.080 --> 00:16:08.480
<v Speaker 2>didn't set it off because suddenly I had fifty of

308
00:16:08.519 --> 00:16:11.000
<v Speaker 2>the same email from all different people. You like, Right,

309
00:16:11.159 --> 00:16:15.279
<v Speaker 2>that's not good. That looks bad. That's right, that's not right.

310
00:16:16.519 --> 00:16:19.559
<v Speaker 1>All right, let's talk about the top ten grossing movies

311
00:16:19.559 --> 00:16:24.440
<v Speaker 1>of nineteen ninety nine. Number ten, Runaway Bride, number nine,

312
00:16:24.559 --> 00:16:29.879
<v Speaker 1>Austin Powers, The Spy Who Shagged Me? Oh Man, Number eight,

313
00:16:29.919 --> 00:16:34.879
<v Speaker 1>American Beauty seven, The World Is Not Enough six Nodding Hill.

314
00:16:35.240 --> 00:16:37.600
<v Speaker 1>It's a movie my wife still wants me to watch

315
00:16:37.639 --> 00:16:41.519
<v Speaker 1>with her, and I'm kind of rolling my eyes. Five

316
00:16:41.879 --> 00:16:44.559
<v Speaker 1>Tarzan for the Matrix.

317
00:16:44.600 --> 00:16:47.399
<v Speaker 2>Oh Boy, one of my very favorites nineteen ninety nine.

318
00:16:47.480 --> 00:16:50.080
<v Speaker 1>Oh yeah, that kind of blew. It's only number four.

319
00:16:50.480 --> 00:16:53.840
<v Speaker 1>It's only number four because number three is Toy Story two,

320
00:16:54.799 --> 00:16:58.480
<v Speaker 1>great great film. Number two is the sixth Sense m

321
00:16:58.879 --> 00:17:02.200
<v Speaker 1>I see lots of doll yes, six hundred and seventy

322
00:17:02.200 --> 00:17:06.039
<v Speaker 1>three million to be exact, and number one Star Wars

323
00:17:06.319 --> 00:17:09.920
<v Speaker 1>episode one, the Phantom Menace, which came in at one

324
00:17:10.160 --> 00:17:11.680
<v Speaker 1>point three.

325
00:17:11.720 --> 00:17:14.440
<v Speaker 2>Billion dollars and disappointed so many people.

326
00:17:14.599 --> 00:17:17.960
<v Speaker 1>Yeah, charge our banks kind of killed it for me.

327
00:17:17.960 --> 00:17:18.119
<v Speaker 5>But.

328
00:17:20.160 --> 00:17:24.440
<v Speaker 2>Admitichlorians are a parasite, Like just yeah, yeah, I'm a

329
00:17:24.440 --> 00:17:26.759
<v Speaker 2>big believer in the machete order of how you watch

330
00:17:26.799 --> 00:17:30.200
<v Speaker 2>the movies, where you actually watch episode four first, then

331
00:17:30.319 --> 00:17:33.960
<v Speaker 2>two and three? Are you watch four and five first, right,

332
00:17:34.359 --> 00:17:36.640
<v Speaker 2>so you see Empire strikes back, You're like, wow, what's

333
00:17:36.680 --> 00:17:38.359
<v Speaker 2>going on? Then you watch two and three sort of

334
00:17:38.359 --> 00:17:41.200
<v Speaker 2>the invention of Darth Vader, and then six is the Redemption.

335
00:17:41.599 --> 00:17:43.599
<v Speaker 2>You know, you don't watch You don't watch episode one

336
00:17:44.000 --> 00:17:46.359
<v Speaker 2>because it does nothing. You don't need it for anything.

337
00:17:46.400 --> 00:17:50.799
<v Speaker 2>It's unnecessary. I remember we took our oldest daughter, Emmy two.

338
00:17:51.200 --> 00:17:54.119
<v Speaker 2>She was our only daughter at that point, and she

339
00:17:54.279 --> 00:17:58.720
<v Speaker 2>was young, and she got so upset when Anakin had

340
00:17:58.720 --> 00:18:02.200
<v Speaker 2>to leave his mom. Yeah, she got so upset she

341
00:18:02.279 --> 00:18:05.200
<v Speaker 2>ran out of the theater. Crime fair enough. That's what

342
00:18:05.240 --> 00:18:06.079
<v Speaker 2>the kids see, right.

343
00:18:06.279 --> 00:18:08.720
<v Speaker 1>They knew how to Lucas knew how to tug on

344
00:18:08.759 --> 00:18:12.960
<v Speaker 1>the kid's heart strings, that's for sure. All right, let's

345
00:18:13.200 --> 00:18:15.440
<v Speaker 1>get into better no framework, I got a good one

346
00:18:15.480 --> 00:18:15.680
<v Speaker 1>for you.

347
00:18:15.839 --> 00:18:25.079
<v Speaker 2>Awesome, Oh man, what do you got?

348
00:18:25.319 --> 00:18:29.240
<v Speaker 1>So I went looking in the trending repos on GitHub,

349
00:18:29.240 --> 00:18:32.039
<v Speaker 1>but I didn't limit it to C sharp, but just

350
00:18:32.079 --> 00:18:34.960
<v Speaker 1>the English language, and I found one at the very

351
00:18:35.000 --> 00:18:40.480
<v Speaker 1>top called build your Own X and it's basically the

352
00:18:40.519 --> 00:18:44.000
<v Speaker 1>repository is a compilation of well written, step by step

353
00:18:44.039 --> 00:18:48.680
<v Speaker 1>guides for recreating our favorite technologies from scratch. So the

354
00:18:48.720 --> 00:18:51.400
<v Speaker 1>whole idea isn't that you want to replace, you know,

355
00:18:51.480 --> 00:18:53.880
<v Speaker 1>something that you have with something you can write. But

356
00:18:53.920 --> 00:18:57.240
<v Speaker 1>it's for learning. Oh interesting, Yeah, it's for learning how

357
00:18:57.279 --> 00:19:00.960
<v Speaker 1>to write code. Yea, doing stuff from scratch with an

358
00:19:01.119 --> 00:19:04.079
<v Speaker 1>end goal that you already know what it does. So

359
00:19:04.480 --> 00:19:07.079
<v Speaker 1>here's some of the things you can build. Three D renderer,

360
00:19:07.480 --> 00:19:13.640
<v Speaker 1>an AI model, augmented reality, a bit torrent client, blockchain, cryptocurrency,

361
00:19:14.160 --> 00:19:18.240
<v Speaker 1>a bot, command line tool, database dock because everybody needs

362
00:19:18.279 --> 00:19:21.079
<v Speaker 1>to write their own database before they die. Okay, I

363
00:19:21.119 --> 00:19:27.960
<v Speaker 1>did that once once. Docer an emulator or virtual machine

364
00:19:28.319 --> 00:19:33.359
<v Speaker 1>front end frameworker library, a game, GIT memory allocator, network stack,

365
00:19:33.559 --> 00:19:39.359
<v Speaker 1>neural network operating system, physics engine, processor programming language, rej

366
00:19:39.400 --> 00:19:43.839
<v Speaker 1>ex engine, search engine, shell template engine, text editor, visual

367
00:19:43.920 --> 00:19:47.720
<v Speaker 1>recognition system, a vox cell engine, a web browser, a

368
00:19:47.720 --> 00:19:54.079
<v Speaker 1>web server, and then there's a category called uncategorized. But

369
00:19:54.119 --> 00:19:56.880
<v Speaker 1>I mean, this is real stuff. You know, it's cool,

370
00:19:57.279 --> 00:19:59.839
<v Speaker 1>it's very cool. So I wanted to give a shout

371
00:19:59.839 --> 00:20:03.240
<v Speaker 1>out to these guys. And you know, if there's anybody

372
00:20:03.319 --> 00:20:08.079
<v Speaker 1>left on the planet who wants to learn programming, and

373
00:20:08.160 --> 00:20:10.559
<v Speaker 1>they should, this is a way to do it.

374
00:20:10.680 --> 00:20:12.880
<v Speaker 2>Let's cool. Yeah, nice, fine, well done.

375
00:20:13.000 --> 00:20:15.200
<v Speaker 1>So that's what I got. Who's talking to us today, Richard.

376
00:20:15.640 --> 00:20:17.519
<v Speaker 2>Knowing this is an unusual show and we're sort of

377
00:20:17.519 --> 00:20:20.319
<v Speaker 2>put in pieces together, I wanted to do an unusual comment,

378
00:20:21.519 --> 00:20:25.519
<v Speaker 2>call it an erratum or a correction or retractions from

379
00:20:25.519 --> 00:20:28.119
<v Speaker 2>episode nineteen ninety six, which was when we did with

380
00:20:28.200 --> 00:20:31.599
<v Speaker 2>Dan Roth talking about ASP dot net core. And I

381
00:20:31.920 --> 00:20:36.960
<v Speaker 2>mentioned in the history part about Alexa in nineteen ninety six. Okay,

382
00:20:37.319 --> 00:20:41.759
<v Speaker 2>and so with the pseudonym eternal twenty one is is comment.

383
00:20:41.799 --> 00:20:43.920
<v Speaker 2>I thought the close claiming Alexa was released in ninetety

384
00:20:43.960 --> 00:20:46.319
<v Speaker 2>six was an abul fool's joke. I think you were

385
00:20:46.359 --> 00:20:48.640
<v Speaker 2>just able to start ordering books online around that time.

386
00:20:48.759 --> 00:20:52.279
<v Speaker 2>Amazon Alexa was officially released in November twenty fourteen, alongside

387
00:20:52.440 --> 00:20:56.119
<v Speaker 2>the Amos on Echo smart speaker twenty eleven, under the

388
00:20:56.160 --> 00:20:59.839
<v Speaker 2>code named Doppler from Amazon's labs. That makes sense, Yeah,

389
00:21:00.079 --> 00:21:03.319
<v Speaker 2>that's the Alexa that I mentioned. What I meant to

390
00:21:03.400 --> 00:21:06.160
<v Speaker 2>talk about was a different Alexa. But I messed up

391
00:21:06.160 --> 00:21:08.440
<v Speaker 2>my notes because in nineteen ninety six there were a

392
00:21:08.559 --> 00:21:13.119
<v Speaker 2>new website was stood up called Alexa and it was

393
00:21:13.240 --> 00:21:17.359
<v Speaker 2>a site for doing web traffic data and global rankings.

394
00:21:17.519 --> 00:21:20.039
<v Speaker 2>In ninety six, like right at the beginning of all

395
00:21:20.039 --> 00:21:23.440
<v Speaker 2>of this, and just to make it more complicated, it

396
00:21:23.519 --> 00:21:27.720
<v Speaker 2>was acquired by Amazon. Oh boy, so my mistake. I

397
00:21:27.839 --> 00:21:30.680
<v Speaker 2>mixed up the name of two different things that Amazon

398
00:21:30.759 --> 00:21:34.799
<v Speaker 2>ultimately owned. They did shut down the website ultimately in

399
00:21:34.839 --> 00:21:39.519
<v Speaker 2>twenty two. Yeah, but yeah, that's what happened there. My apologies,

400
00:21:39.559 --> 00:21:42.400
<v Speaker 2>but eternal thank you so much for your comment, and

401
00:21:42.440 --> 00:21:44.160
<v Speaker 2>a copy of music Cobi is on its way to you.

402
00:21:44.200 --> 00:21:45.839
<v Speaker 2>And if you'd like copy of music go buy right

403
00:21:45.880 --> 00:21:47.960
<v Speaker 2>a comment on the website at dot rocks dot com

404
00:21:48.039 --> 00:21:49.799
<v Speaker 2>or on the Facebook. So we publish every show there

405
00:21:50.039 --> 00:21:51.319
<v Speaker 2>and if you comment there and I read it on

406
00:21:51.359 --> 00:21:52.480
<v Speaker 2>the show, I'll send you a copy of.

407
00:21:52.559 --> 00:21:54.680
<v Speaker 1>Us to go by, and so just to lay the

408
00:21:54.680 --> 00:21:57.880
<v Speaker 1>groundwork for what you're going to hear next, we have

409
00:21:58.039 --> 00:22:01.279
<v Speaker 1>a bunch of just individuals store worries from individuals who

410
00:22:01.319 --> 00:22:04.559
<v Speaker 1>worked on the Y two K bug in nineteen ninety nine. Yeah,

411
00:22:04.599 --> 00:22:09.039
<v Speaker 1>and so we're going to listen to those now. Hi.

412
00:22:09.720 --> 00:22:13.640
<v Speaker 3>Back in nineteen ninety seven, my first ever professional software

413
00:22:13.759 --> 00:22:16.359
<v Speaker 3>development role was working with a company that had the loans,

414
00:22:16.559 --> 00:22:19.680
<v Speaker 3>higher purchase and leasing products written in quick Basic seven

415
00:22:19.720 --> 00:22:23.119
<v Speaker 3>point one that we needed to make Y two K compatible.

416
00:22:24.160 --> 00:22:27.200
<v Speaker 3>And to say it was painful with being understatement. We

417
00:22:27.279 --> 00:22:29.559
<v Speaker 3>had to go through every single dot bass file looking

418
00:22:29.599 --> 00:22:32.440
<v Speaker 3>for every usage of dates, and the variable names were

419
00:22:33.000 --> 00:22:36.039
<v Speaker 3>pretty consistently bad as you can imagine, like today's date

420
00:22:36.119 --> 00:22:39.079
<v Speaker 3>was usually a dollar, and sometimes a dollar was used

421
00:22:39.119 --> 00:22:42.000
<v Speaker 3>not just for today's date but for other values as well.

422
00:22:42.880 --> 00:22:45.039
<v Speaker 3>On the once all the logic was fixed, and then

423
00:22:45.079 --> 00:22:47.079
<v Speaker 3>as a ship all the floppy disks to all the

424
00:22:47.119 --> 00:22:49.920
<v Speaker 3>customers and that was a massive effort as well. So

425
00:22:50.400 --> 00:22:53.519
<v Speaker 3>in the end we had all the customers working with

426
00:22:53.799 --> 00:22:56.240
<v Speaker 3>smoothly without any issues and they all went to plan,

427
00:22:56.319 --> 00:22:59.319
<v Speaker 3>which is quite extraordinary really, So it was Yeah, it

428
00:22:59.400 --> 00:23:02.039
<v Speaker 3>was a massive excess though, pretty painful.

429
00:23:07.119 --> 00:23:09.720
<v Speaker 6>I'm Sean Wildemuth and I've been listening to the podcast

430
00:23:09.720 --> 00:23:11.680
<v Speaker 6>since the early days. I think it was the early

431
00:23:11.720 --> 00:23:14.759
<v Speaker 6>two thousands. Actually, I did work for a Y two

432
00:23:14.839 --> 00:23:19.440
<v Speaker 6>K company. Actually they did SNMP audits to find y

433
00:23:19.440 --> 00:23:22.799
<v Speaker 6>two k problems. As soon as two thousand were old around,

434
00:23:23.079 --> 00:23:24.920
<v Speaker 6>they were out of business and I was out of

435
00:23:24.920 --> 00:23:25.359
<v Speaker 6>a job.

436
00:23:25.519 --> 00:23:26.039
<v Speaker 2>Go figure.

437
00:23:27.359 --> 00:23:29.319
<v Speaker 6>Early on, I listened to dot net Rocks to hear

438
00:23:29.359 --> 00:23:31.400
<v Speaker 6>about what was new in dot net, because those were

439
00:23:31.480 --> 00:23:34.920
<v Speaker 6>the early days of one O beta and eventually one

440
00:23:34.920 --> 00:23:38.240
<v Speaker 6>to one. Over the years, I've been invited on the

441
00:23:38.279 --> 00:23:43.000
<v Speaker 6>podcast seventeen times. Carl and Richard have been incredibly kind

442
00:23:43.039 --> 00:23:46.039
<v Speaker 6>and generous with their time, and it's helped my career tremendously.

443
00:23:46.720 --> 00:23:50.119
<v Speaker 6>Twenty years on, it's still worth listening to every episode.

444
00:23:51.680 --> 00:23:55.160
<v Speaker 1>So Richard Guy Royce is here to tell us his

445
00:23:55.279 --> 00:23:58.000
<v Speaker 1>experiences with Y two K. Hi Guy, Hey, how's it

446
00:23:58.039 --> 00:24:00.920
<v Speaker 1>going good? How are you? I'm doing all right? You know,

447
00:24:01.079 --> 00:24:03.279
<v Speaker 1>I always like to say I'm fair to Midland. How

448
00:24:03.359 --> 00:24:05.880
<v Speaker 1>was your nineteen ninety nine profitable?

449
00:24:09.720 --> 00:24:11.599
<v Speaker 2>My line for a while now has been I bought

450
00:24:11.599 --> 00:24:14.359
<v Speaker 2>a house off the back of what I made.

451
00:24:14.119 --> 00:24:14.920
<v Speaker 1>With Y two K?

452
00:24:15.079 --> 00:24:17.599
<v Speaker 5>Yeah, yeah, It was a great time to be a consultant.

453
00:24:17.680 --> 00:24:21.599
<v Speaker 5>It really was. You know, I was fairly young, relatively

454
00:24:21.640 --> 00:24:25.240
<v Speaker 5>early in my career, and I was doing a lot

455
00:24:25.240 --> 00:24:30.519
<v Speaker 5>of C plus plus and oh man, I wasn't on

456
00:24:30.559 --> 00:24:34.240
<v Speaker 5>a C plus plus project that actually needed remediation. To

457
00:24:34.519 --> 00:24:36.920
<v Speaker 5>work with Y two k. It was a let's just

458
00:24:36.960 --> 00:24:39.279
<v Speaker 5>throw away this old system and completely rewrite it in

459
00:24:39.359 --> 00:24:42.759
<v Speaker 5>C plus plush, and that was the solution that they

460
00:24:42.759 --> 00:24:44.359
<v Speaker 5>had come up with. But I had a whole bunch

461
00:24:44.359 --> 00:24:46.240
<v Speaker 5>of mainframe integration and stuff in it as well.

462
00:24:46.319 --> 00:24:49.279
<v Speaker 2>I mean, great that you're a consultant, because that's just bucks.

463
00:24:49.400 --> 00:24:51.799
<v Speaker 2>But from a from an architect's point of view, it's like,

464
00:24:51.839 --> 00:24:53.880
<v Speaker 2>is this really the right thing to rewrite? And C

465
00:24:54.039 --> 00:24:55.960
<v Speaker 2>plus plus? Yeah?

466
00:24:56.039 --> 00:24:58.680
<v Speaker 5>You know, it's probably worth noting that the company got

467
00:24:58.680 --> 00:25:00.880
<v Speaker 5>bought up by someone in the and someone else, and

468
00:25:00.920 --> 00:25:04.000
<v Speaker 5>now it's not really a thing anymore. I could probably

469
00:25:04.000 --> 00:25:05.119
<v Speaker 5>talk about the company honestly.

470
00:25:05.319 --> 00:25:08.960
<v Speaker 2>Yeah, but obviously somebody got paid like it worked out

471
00:25:09.000 --> 00:25:13.160
<v Speaker 2>for them. Yeah, but you weren't actually remediating a C

472
00:25:13.279 --> 00:25:15.440
<v Speaker 2>plus plus. It was just to rewrite. Yeah.

473
00:25:15.480 --> 00:25:19.359
<v Speaker 5>They had was The client was Sterling Commerce, which if

474
00:25:19.400 --> 00:25:22.039
<v Speaker 5>you've ever heard of them, they were like a EDI

475
00:25:22.319 --> 00:25:25.039
<v Speaker 5>broker kind of thing before the Internet really took off.

476
00:25:25.359 --> 00:25:26.279
<v Speaker 2>Sure, it's nine.

477
00:25:26.359 --> 00:25:28.440
<v Speaker 5>And so they had like DN lines coming in from

478
00:25:28.480 --> 00:25:33.200
<v Speaker 5>various big clients wow, and various ways of getting data

479
00:25:33.200 --> 00:25:34.880
<v Speaker 5>in and out. And then they would take data from

480
00:25:34.960 --> 00:25:38.400
<v Speaker 5>say a retailer, which is with a bunch of purchase orders,

481
00:25:38.400 --> 00:25:40.119
<v Speaker 5>and then transform it into a format that would be

482
00:25:40.160 --> 00:25:42.400
<v Speaker 5>suitable to and over a wire protocol that would be

483
00:25:42.400 --> 00:25:46.240
<v Speaker 5>acceptable by some supplier that they bought their supplies from,

484
00:25:46.720 --> 00:25:49.160
<v Speaker 5>and those sorts of things. And so you'd take in

485
00:25:49.279 --> 00:25:51.960
<v Speaker 5>like one would come over the Internet using just like

486
00:25:52.000 --> 00:25:55.160
<v Speaker 5>an IP tunnel of some sort, and then it would

487
00:25:55.200 --> 00:25:57.480
<v Speaker 5>go off over FTP to some other server.

488
00:25:57.599 --> 00:25:59.960
<v Speaker 1>Or rue Goldberg.

489
00:26:00.240 --> 00:26:00.440
<v Speaker 5>Yeah.

490
00:26:00.519 --> 00:26:00.839
<v Speaker 2>Yeah.

491
00:26:00.880 --> 00:26:02.799
<v Speaker 5>And so they were just they were the hub and

492
00:26:02.880 --> 00:26:05.240
<v Speaker 5>they had all these spokes and so the hub itself

493
00:26:05.279 --> 00:26:08.319
<v Speaker 5>wasn't really that complicated, but the spokes were where all

494
00:26:08.319 --> 00:26:09.160
<v Speaker 5>the effort was at.

495
00:26:09.559 --> 00:26:11.559
<v Speaker 2>But that means you're bringing other people's data. Are you

496
00:26:11.640 --> 00:26:14.599
<v Speaker 2>now trying to enforce four digit years? No?

497
00:26:14.599 --> 00:26:16.279
<v Speaker 5>No, that was all and then we're just we're just

498
00:26:16.519 --> 00:26:19.680
<v Speaker 5>carrying the data around, right okay. Yeah, And some of

499
00:26:19.680 --> 00:26:21.599
<v Speaker 5>them were integrated through the mainframe as well, so we

500
00:26:21.640 --> 00:26:26.240
<v Speaker 5>had to like tie in with we used host Integration server.

501
00:26:26.519 --> 00:26:30.319
<v Speaker 5>If anyone remembers host Integration Server, yeah, wow, there's a

502
00:26:30.359 --> 00:26:32.680
<v Speaker 5>music story. I don't know if that's podcast safe about that, but.

503
00:26:35.160 --> 00:26:37.839
<v Speaker 7>Well yeah, my first question was going to be were

504
00:26:37.880 --> 00:26:40.759
<v Speaker 7>you dealing with code or data or both? I mean,

505
00:26:40.799 --> 00:26:44.519
<v Speaker 7>it sounds like it was in memory, but what about persistence?

506
00:26:44.799 --> 00:26:47.160
<v Speaker 7>And I thought that was where the real problem was.

507
00:26:47.519 --> 00:26:50.680
<v Speaker 5>It was mostly it was dealing with code and data,

508
00:26:51.000 --> 00:26:54.599
<v Speaker 5>but the data itself. They had data themselves that need

509
00:26:54.599 --> 00:26:59.000
<v Speaker 5>to be remediated for their application, but the code was

510
00:26:59.039 --> 00:27:00.880
<v Speaker 5>really the bulk of the work. The data that we

511
00:27:00.880 --> 00:27:05.400
<v Speaker 5>were carrying on behalf of the clients. We just carried it.

512
00:27:05.799 --> 00:27:08.000
<v Speaker 2>There was no and you I presume we carried it

513
00:27:08.079 --> 00:27:10.559
<v Speaker 2>as string, so you don't care what's in it? Really

514
00:27:10.680 --> 00:27:14.839
<v Speaker 2>like bytes, you're not actually doing any data. That's okay.

515
00:27:15.119 --> 00:27:18.319
<v Speaker 5>Yeah, someone wasn't even strings. It was just bytes like

516
00:27:18.319 --> 00:27:19.480
<v Speaker 5>some of the health I don't know if that. I

517
00:27:19.519 --> 00:27:21.400
<v Speaker 5>don't remember if we did healthcare data or not. I

518
00:27:21.440 --> 00:27:23.359
<v Speaker 5>don't think we did. I remember we had like various

519
00:27:23.480 --> 00:27:27.400
<v Speaker 5>EDI formats, but it was really more about taking it

520
00:27:27.960 --> 00:27:29.960
<v Speaker 5>and there was a transformation. But there's no Y two

521
00:27:30.000 --> 00:27:33.960
<v Speaker 5>is K compatibility in there. Right then, at least not

522
00:27:34.000 --> 00:27:36.440
<v Speaker 5>in any of the parts that I worked on. The

523
00:27:36.480 --> 00:27:39.160
<v Speaker 5>thing I specifically remember spending the most time on was

524
00:27:41.119 --> 00:27:44.839
<v Speaker 5>a obscure protocol that was popular in Europe called OFTP,

525
00:27:46.079 --> 00:27:50.200
<v Speaker 5>the ODEBT file Transfer Protocol, which god, I don't know

526
00:27:50.240 --> 00:27:52.160
<v Speaker 5>if that exists anymore or not if anyone's still using it.

527
00:27:52.240 --> 00:27:54.319
<v Speaker 5>It's some standard. It goes like back to the seventies

528
00:27:54.400 --> 00:27:54.759
<v Speaker 5>or something.

529
00:27:54.839 --> 00:27:57.440
<v Speaker 2>Oh oh, debt dot Org. Dude, I'll include it in

530
00:27:57.440 --> 00:27:58.519
<v Speaker 2>the show notes for people who.

531
00:27:58.440 --> 00:28:02.279
<v Speaker 5>Will have it's still out there. Yeah, wow, good news.

532
00:28:02.279 --> 00:28:07.279
<v Speaker 5>They're up to version two. Up the version two the

533
00:28:07.319 --> 00:28:12.640
<v Speaker 5>seventies have called they want their version one back. Yeah,

534
00:28:12.680 --> 00:28:15.119
<v Speaker 5>but yeah, it was. It was a really weird time though,

535
00:28:15.119 --> 00:28:18.599
<v Speaker 5>because I mean, some companies took advantage of y twok

536
00:28:18.720 --> 00:28:21.039
<v Speaker 5>to get budget to do rewrites that they kind of

537
00:28:21.039 --> 00:28:21.960
<v Speaker 5>needed to do anyhow.

538
00:28:22.119 --> 00:28:22.400
<v Speaker 1>Sure.

539
00:28:22.480 --> 00:28:26.119
<v Speaker 2>Yeah. Tact it was a cover for all kinds of

540
00:28:26.160 --> 00:28:26.880
<v Speaker 2>technical debt.

541
00:28:27.079 --> 00:28:29.839
<v Speaker 5>Yeah yeah. It was like a tech debt slush fund.

542
00:28:29.920 --> 00:28:37.039
<v Speaker 5>Yeah yeah. And some companies were and consulting companies were

543
00:28:37.039 --> 00:28:39.920
<v Speaker 5>happy to take the money to do those projects. And

544
00:28:40.400 --> 00:28:41.799
<v Speaker 5>it was it was weird because it was one of

545
00:28:41.839 --> 00:28:45.599
<v Speaker 5>those times when it absolutely positively had to be done

546
00:28:45.640 --> 00:28:47.880
<v Speaker 5>by a hard deadline that was completely inflexible.

547
00:28:47.960 --> 00:28:51.960
<v Speaker 2>So this was the us FED deadline of June thirtieth,

548
00:28:52.079 --> 00:28:56.519
<v Speaker 2>no no or voices. It was literally that nineteen ninety nine.

549
00:28:56.559 --> 00:28:58.759
<v Speaker 2>Like you will know you got January first.

550
00:28:58.839 --> 00:29:02.160
<v Speaker 5>Yeah, yeah, of twenty of two thousand, it's like, well

551
00:29:02.240 --> 00:29:05.240
<v Speaker 5>it's not done by then, then we've got a problem, right, Yeah.

552
00:29:06.279 --> 00:29:09.039
<v Speaker 5>And so everyone just sand bagged all the estimates on

553
00:29:09.079 --> 00:29:11.480
<v Speaker 5>everything and you know, and then threw a lot of

554
00:29:11.480 --> 00:29:15.240
<v Speaker 5>money at it, and then everyone met the date. And

555
00:29:15.279 --> 00:29:18.440
<v Speaker 5>I was happy to be a part of it. You know,

556
00:29:18.720 --> 00:29:22.759
<v Speaker 5>I was young, making money. It was great, good, good times.

557
00:29:23.200 --> 00:29:24.000
<v Speaker 1>Nothing wrong with that.

558
00:29:24.359 --> 00:29:26.920
<v Speaker 2>Yeah. You can also see from a C plus plus

559
00:29:26.960 --> 00:29:28.799
<v Speaker 2>point of view because the way you did data structure,

560
00:29:28.880 --> 00:29:32.200
<v Speaker 2>especially back then, like it's just no easy migration path.

561
00:29:32.240 --> 00:29:34.400
<v Speaker 2>You have to build new structures to store data to

562
00:29:34.440 --> 00:29:36.039
<v Speaker 2>the dates differently, right. Yeah.

563
00:29:36.039 --> 00:29:38.680
<v Speaker 5>I think I think that was even before like STL

564
00:29:38.799 --> 00:29:40.839
<v Speaker 5>was a thing, right, or at least it was popularized

565
00:29:40.839 --> 00:29:42.839
<v Speaker 5>because I remember the first C plus plus project I

566
00:29:42.920 --> 00:29:52.000
<v Speaker 5>did professionally was for a a Central Ohio based lingerie

567
00:29:52.359 --> 00:29:54.599
<v Speaker 5>company who has a secret.

568
00:29:56.839 --> 00:30:03.079
<v Speaker 1>Okay, not just one secret, yeah, we got more than one. Yeah,

569
00:30:03.440 --> 00:30:04.160
<v Speaker 1>many secrets.

570
00:30:04.240 --> 00:30:07.079
<v Speaker 5>Yeah, and the first thing we did on that project

571
00:30:07.240 --> 00:30:09.000
<v Speaker 5>was okay, well we got to build our link lists

572
00:30:09.000 --> 00:30:11.240
<v Speaker 5>and our hash tables and all of our conventional trastructures

573
00:30:11.240 --> 00:30:15.200
<v Speaker 5>because they weren't baked in. This was really before the

574
00:30:15.240 --> 00:30:18.079
<v Speaker 5>standard template libraries became part of C plus plus. Yeah,

575
00:30:18.279 --> 00:30:19.839
<v Speaker 5>you know, I haven't really been in this plus plus

576
00:30:19.880 --> 00:30:21.200
<v Speaker 5>world a lot since then. I don't know if they're

577
00:30:21.200 --> 00:30:22.000
<v Speaker 5>there anymore or not.

578
00:30:22.079 --> 00:30:24.839
<v Speaker 1>But inflexible memory structures.

579
00:30:24.599 --> 00:30:27.400
<v Speaker 2>Yeah, yeah, that was just a nature of the beast. Yeah,

580
00:30:27.559 --> 00:30:30.599
<v Speaker 2>sdls from the mid nineties, So by two thousand you

581
00:30:30.720 --> 00:30:33.680
<v Speaker 2>may or may not have implemented against it yet, right, Like,

582
00:30:33.839 --> 00:30:35.480
<v Speaker 2>it's just still early.

583
00:30:36.240 --> 00:30:39.079
<v Speaker 1>So your structure has basically had two bytes for a date?

584
00:30:40.160 --> 00:30:43.359
<v Speaker 1>Just why why is that? Can we boil it down

585
00:30:43.359 --> 00:30:43.599
<v Speaker 1>to that?

586
00:30:44.200 --> 00:30:45.759
<v Speaker 5>For the parts I worked on, I didn't really have to.

587
00:30:45.880 --> 00:30:47.440
<v Speaker 5>It was it was y two K, And it wasn't

588
00:30:47.599 --> 00:30:50.559
<v Speaker 5>y two K in a way because a lot of

589
00:30:50.680 --> 00:30:53.599
<v Speaker 5>was just faring the data along or transforming it from

590
00:30:53.599 --> 00:30:56.880
<v Speaker 5>one standard to another. And I don't remember, honestly if

591
00:30:56.880 --> 00:31:01.960
<v Speaker 5>the standards how they handled dates. Some of them, I'm

592
00:31:02.000 --> 00:31:03.759
<v Speaker 5>sure I mean n C plus plaus Land, I'm sure

593
00:31:03.759 --> 00:31:06.359
<v Speaker 5>a lot of these dates were being handled by just

594
00:31:06.519 --> 00:31:08.720
<v Speaker 5>unix states, which means the problem is coming back up

595
00:31:08.720 --> 00:31:09.480
<v Speaker 5>here real soon.

596
00:31:11.400 --> 00:31:15.240
<v Speaker 2>Right, And that's the second since nineteen seventy. Yeah, or

597
00:31:15.359 --> 00:31:17.720
<v Speaker 2>two bits solution that needs to has been that has

598
00:31:17.759 --> 00:31:20.000
<v Speaker 2>been converted to a sixty four bit solution if you've

599
00:31:20.000 --> 00:31:20.799
<v Speaker 2>done the conversion.

600
00:31:20.880 --> 00:31:26.119
<v Speaker 5>Yeah, But I just remember the weird file protocols that

601
00:31:26.119 --> 00:31:29.279
<v Speaker 5>we were are not file the weird wire protocols that

602
00:31:29.279 --> 00:31:33.279
<v Speaker 5>we were implementing to send these things, these files around.

603
00:31:33.119 --> 00:31:34.759
<v Speaker 5>Had we built this one big core though, that did

604
00:31:34.759 --> 00:31:37.000
<v Speaker 5>something that wasn't on that part of the project. Specifically,

605
00:31:37.480 --> 00:31:41.079
<v Speaker 5>this big core that did so take like an EEDI

606
00:31:41.200 --> 00:31:43.200
<v Speaker 5>thing and turn it into some other format that is

607
00:31:43.279 --> 00:31:44.440
<v Speaker 5>amenable for that company.

608
00:31:44.720 --> 00:31:44.920
<v Speaker 2>Right.

609
00:31:46.000 --> 00:31:48.559
<v Speaker 5>But I didn't get too deep into that specific aspect

610
00:31:48.559 --> 00:31:51.599
<v Speaker 5>of it. It was more just building a lot of

611
00:31:51.599 --> 00:31:54.160
<v Speaker 5>the protocol adapts to allow these files to be transferred

612
00:31:54.160 --> 00:31:56.119
<v Speaker 5>across different wire formats.

613
00:31:56.440 --> 00:31:59.880
<v Speaker 2>Right. So it sounds like you were a transport guy, Yeah,

614
00:32:00.440 --> 00:32:02.359
<v Speaker 2>deal with all the different ways and stuff moving around

615
00:32:03.680 --> 00:32:06.720
<v Speaker 2>and just C plus plus or another languages floating around.

616
00:32:07.119 --> 00:32:10.240
<v Speaker 5>There was some COBAL involved, but I didn't touch it.

617
00:32:10.240 --> 00:32:12.039
<v Speaker 2>Of course, because you had the main frame stuff. Yeah.

618
00:32:12.039 --> 00:32:14.319
<v Speaker 5>Because well, one of the integration points was the main frame.

619
00:32:14.720 --> 00:32:16.720
<v Speaker 1>I was gonna say, cob I think Cobol is the

620
00:32:16.759 --> 00:32:18.480
<v Speaker 1>star of nineteen ninety ninety.

621
00:32:18.519 --> 00:32:21.720
<v Speaker 7>Yeah, in terms of Y two K, there was so much,

622
00:32:21.799 --> 00:32:23.720
<v Speaker 7>so much Cobal that had to be redone.

623
00:32:23.799 --> 00:32:25.960
<v Speaker 5>I'm actually really surprised that I didn't find myself doing

624
00:32:26.000 --> 00:32:28.000
<v Speaker 5>more of it, because it is it is something that

625
00:32:28.240 --> 00:32:30.039
<v Speaker 5>I can do, well, could do. I don't know that

626
00:32:30.079 --> 00:32:33.279
<v Speaker 5>I could do it today, maybe a couple of weeks

627
00:32:33.359 --> 00:32:35.480
<v Speaker 5>get up to speed. But I did do Cobyl early

628
00:32:35.519 --> 00:32:36.119
<v Speaker 5>in my career.

629
00:32:36.160 --> 00:32:38.400
<v Speaker 1>And well, you know, chat ept you could do anything.

630
00:32:38.799 --> 00:32:43.720
<v Speaker 5>Yeah, yeah, whatever, I did do Cobyl in my career.

631
00:32:43.799 --> 00:32:46.720
<v Speaker 5>My first job out out of college was as a

632
00:32:46.720 --> 00:32:50.119
<v Speaker 5>Cobal developer on DOS, a DOS based Cobyl system. So

633
00:32:51.640 --> 00:32:56.519
<v Speaker 5>but it just never didn't line up that way. But yeah,

634
00:32:56.559 --> 00:32:58.920
<v Speaker 5>it was, it was, it was fun, it's awesome.

635
00:32:58.920 --> 00:33:02.440
<v Speaker 7>Only Cobal I ever did was in college. I have

636
00:33:02.559 --> 00:33:06.279
<v Speaker 7>computer science class. The tests, right, yeah, just to pass

637
00:33:06.319 --> 00:33:08.920
<v Speaker 7>the test, I mean, couple is not hard. It's just

638
00:33:10.079 --> 00:33:11.720
<v Speaker 7>it's actually it's pretty easy.

639
00:33:12.000 --> 00:33:15.400
<v Speaker 2>Yeah, it's just everything's just a text file. Man, it's

640
00:33:15.440 --> 00:33:18.039
<v Speaker 2>just like it's it's batch processing. It's fine.

641
00:33:18.160 --> 00:33:20.039
<v Speaker 5>It wasn't even it's not even any more for both

642
00:33:20.119 --> 00:33:20.880
<v Speaker 5>than modern Java.

643
00:33:21.319 --> 00:33:25.480
<v Speaker 2>So I'm a couple doesn't have a lot of dot

644
00:33:25.519 --> 00:33:30.960
<v Speaker 2>notation I think some ways is less for both. Well, guy,

645
00:33:31.079 --> 00:33:33.799
<v Speaker 2>thanks for your viewpoint on this. It sounds like it

646
00:33:33.839 --> 00:33:36.480
<v Speaker 2>was a cool project. And look a mitly twenty six

647
00:33:36.599 --> 00:33:38.920
<v Speaker 2>years ago. Twenty seven years ago, so a long time ago.

648
00:33:39.200 --> 00:33:40.880
<v Speaker 5>Yeah, it's it's hard to believe it's been that long.

649
00:33:41.200 --> 00:33:44.400
<v Speaker 1>Yeah, and thanks for making sure the world didn't blow up.

650
00:33:44.440 --> 00:33:45.319
<v Speaker 2>Yeah, I appreciate that.

651
00:33:45.319 --> 00:33:48.759
<v Speaker 5>Well, you're welcome to make sure that home Depot can

652
00:33:48.759 --> 00:33:51.640
<v Speaker 5>get their data routed to their wholesalers so that they

653
00:33:51.640 --> 00:33:52.640
<v Speaker 5>can you know exactly.

654
00:33:53.160 --> 00:33:54.839
<v Speaker 2>Do you ever wonder about how much of your code

655
00:33:55.000 --> 00:33:56.599
<v Speaker 2>is from then he's still in use?

656
00:33:57.240 --> 00:33:59.319
<v Speaker 5>I do, actually, and I think there's a little bit,

657
00:33:59.400 --> 00:34:01.440
<v Speaker 5>but not a lot.

658
00:34:01.640 --> 00:34:03.440
<v Speaker 2>You would hope, right, Like I kind of want to

659
00:34:03.759 --> 00:34:06.119
<v Speaker 2>kind of I'm hoping people aren't using that code anymore. Yeah,

660
00:34:06.240 --> 00:34:07.960
<v Speaker 2>I met that guy. He was that right, you know,

661
00:34:08.039 --> 00:34:08.760
<v Speaker 2>like that's a long time.

662
00:34:09.480 --> 00:34:14.039
<v Speaker 5>I was really an idiot back then. Yeah, and it's

663
00:34:14.079 --> 00:34:15.880
<v Speaker 5>a bit more that I'm still an idiot, but.

664
00:34:17.679 --> 00:34:20.000
<v Speaker 2>A very experienced idiot. Yeah.

665
00:34:20.159 --> 00:34:23.000
<v Speaker 7>Excellent guy, Thanks a lot, Thanks a lot, good chatting

666
00:34:23.000 --> 00:34:25.320
<v Speaker 7>with y'all. We'll see you out there. Yeah at the

667
00:34:25.360 --> 00:34:26.440
<v Speaker 7>conferences for sure.

668
00:34:26.480 --> 00:34:27.480
<v Speaker 5>Ye see you the next thing.

669
00:34:28.000 --> 00:34:31.639
<v Speaker 1>And who should appear before us, Richard but Rick Hapworth,

670
00:34:32.280 --> 00:34:33.960
<v Speaker 1>Hi Rick, Hello, What.

671
00:34:33.960 --> 00:34:36.920
<v Speaker 8>A marveless, marvelous introduction that was? That was I want

672
00:34:36.920 --> 00:34:38.119
<v Speaker 8>to go out at the door and come back and

673
00:34:38.119 --> 00:34:40.679
<v Speaker 8>hear it again, quick and dirty.

674
00:34:41.679 --> 00:34:44.719
<v Speaker 1>We understand you have some experience.

675
00:34:44.159 --> 00:34:48.159
<v Speaker 2>With the Y two K bug I might have been around.

676
00:34:49.159 --> 00:34:52.119
<v Speaker 8>I worked for university, so so life was entertaining, right

677
00:34:52.119 --> 00:34:54.440
<v Speaker 8>because it wasn't just like, hey, here are the computers

678
00:34:54.480 --> 00:34:57.239
<v Speaker 8>that you know make our business work or do our

679
00:34:57.280 --> 00:34:58.280
<v Speaker 8>banking transactions.

680
00:34:58.320 --> 00:34:59.119
<v Speaker 5>It was hey, we got.

681
00:34:59.039 --> 00:35:03.320
<v Speaker 8>Chemists and physicists and engineers and you know what they're

682
00:35:03.360 --> 00:35:08.840
<v Speaker 8>like mechanical chemical, chemical engineers, biomedical engineers and the computer

683
00:35:08.920 --> 00:35:11.559
<v Speaker 8>scientists guys and the computing guys. So yeah, it was

684
00:35:11.760 --> 00:35:12.360
<v Speaker 8>it was fun.

685
00:35:13.000 --> 00:35:16.679
<v Speaker 2>So it's not just dealing with the student data. It's

686
00:35:16.840 --> 00:35:19.880
<v Speaker 2>all of the laboratory data. It's huge a rate of

687
00:35:19.880 --> 00:35:20.760
<v Speaker 2>different things.

688
00:35:21.360 --> 00:35:24.960
<v Speaker 8>Yeah, the students were actually kind of easy. I mean

689
00:35:25.000 --> 00:35:29.519
<v Speaker 8>we so I worked for a pretty small university in

690
00:35:29.880 --> 00:35:32.519
<v Speaker 8>the UK, but we were actually pretty switched on. We

691
00:35:32.519 --> 00:35:35.760
<v Speaker 8>were really early adopters of things like the Internet and

692
00:35:35.760 --> 00:35:38.000
<v Speaker 8>the web, we got a web server before anybody else had.

693
00:35:38.559 --> 00:35:41.039
<v Speaker 8>We kept turning up in those sort of web magazines,

694
00:35:41.039 --> 00:35:45.719
<v Speaker 8>you know, that kind of stuff. And we had student

695
00:35:45.800 --> 00:35:49.679
<v Speaker 8>labs for the students. We'd got connectivity from holes. But

696
00:35:49.719 --> 00:35:51.639
<v Speaker 8>at the end of the day, we chose what to

697
00:35:51.679 --> 00:35:54.960
<v Speaker 8>give students, and we controlled the machines and you know,

698
00:35:54.960 --> 00:36:02.280
<v Speaker 8>we disinfected them after they logged out physically and and electronically,

699
00:36:02.320 --> 00:36:07.719
<v Speaker 8>you know. And it was a closed environment, whereas the

700
00:36:07.719 --> 00:36:13.719
<v Speaker 8>the rest of the university academia is a crazy place

701
00:36:13.920 --> 00:36:16.400
<v Speaker 8>because academics have freedom, right and it's like all right

702
00:36:16.639 --> 00:36:19.440
<v Speaker 8>now and I've bought this thing and I'm going to

703
00:36:19.480 --> 00:36:21.840
<v Speaker 8>do some research with it, or We've got this.

704
00:36:21.800 --> 00:36:24.559
<v Speaker 2>New Sure it's there. It's their grant money, right, Yeah,

705
00:36:24.599 --> 00:36:26.599
<v Speaker 2>they're just going to get stuff. Yeah, and we go

706
00:36:26.679 --> 00:36:29.840
<v Speaker 2>in and expect you in it to manage it for them.

707
00:36:29.960 --> 00:36:33.239
<v Speaker 8>Yeah, you know, what does it do? What does it need?

708
00:36:33.639 --> 00:36:34.920
<v Speaker 8>Have you read the man you all, have you read

709
00:36:34.960 --> 00:36:42.119
<v Speaker 8>the system requirements? And just not after midnight? So yeah,

710
00:36:42.119 --> 00:36:44.280
<v Speaker 8>I mean Y two K for us was a combination

711
00:36:44.480 --> 00:36:50.280
<v Speaker 8>of several things, really, right. So we got the administrative

712
00:36:50.360 --> 00:36:52.880
<v Speaker 8>side of the house that was one sort of computing

713
00:36:52.960 --> 00:36:55.360
<v Speaker 8>department and they were the guys who were looking at

714
00:36:55.400 --> 00:36:59.800
<v Speaker 8>our HR systems and our finance systems and our student

715
00:37:00.039 --> 00:37:03.639
<v Speaker 8>coord systems, and that's that's very similar to all everybody

716
00:37:03.639 --> 00:37:04.519
<v Speaker 8>else is white to get.

717
00:37:06.440 --> 00:37:06.639
<v Speaker 2>Yeah.

718
00:37:07.239 --> 00:37:09.519
<v Speaker 8>And then we got the sort of estate side of

719
00:37:09.559 --> 00:37:12.559
<v Speaker 8>the house, which was a bit more challenging because they

720
00:37:12.599 --> 00:37:15.840
<v Speaker 8>tended to have less budget, and it was things like, well,

721
00:37:15.840 --> 00:37:18.079
<v Speaker 8>what happens if that fails, Well, the air conditioning goes

722
00:37:18.079 --> 00:37:21.400
<v Speaker 8>off in all of the buildings at once, and and

723
00:37:21.480 --> 00:37:25.800
<v Speaker 8>you know, it's a combination of bespoke physical hardware card

724
00:37:26.800 --> 00:37:29.320
<v Speaker 8>and I remember once at the time it's like, what's that. Well,

725
00:37:29.320 --> 00:37:33.239
<v Speaker 8>that's that's the control system further heating. That's an eight

726
00:37:33.280 --> 00:37:35.679
<v Speaker 8>bit icer card. I haven't seen one of those for quite.

727
00:37:35.519 --> 00:37:38.159
<v Speaker 2>A while, vintage gear.

728
00:37:39.039 --> 00:37:43.960
<v Speaker 8>Yeah. And we also had the telephony switches, which by

729
00:37:44.000 --> 00:37:46.639
<v Speaker 8>the way, were not digital telephony switches at that point either.

730
00:37:48.159 --> 00:37:49.960
<v Speaker 8>And we were a campus, right, so we got several

731
00:37:49.960 --> 00:37:54.760
<v Speaker 8>of those. And then we got the general academic populace,

732
00:37:54.800 --> 00:37:57.159
<v Speaker 8>which is mostly what I was dealing with. So I

733
00:37:57.199 --> 00:38:01.840
<v Speaker 8>was part of the Academic Computer Center, so provided compute

734
00:38:01.880 --> 00:38:05.000
<v Speaker 8>for the students and compute for all of the academic

735
00:38:05.079 --> 00:38:09.880
<v Speaker 8>departments except computing, who were their own fiefdom and non

736
00:38:09.920 --> 00:38:12.000
<v Speaker 8>shall pass and we'll do what we like. And they

737
00:38:12.000 --> 00:38:13.719
<v Speaker 8>had their own stuff, right, and they managed.

738
00:38:15.239 --> 00:38:15.719
<v Speaker 2>Very much.

739
00:38:16.440 --> 00:38:20.719
<v Speaker 8>Yeah, but but the bit in the middle we were

740
00:38:20.719 --> 00:38:23.320
<v Speaker 8>pretty switched on. So we've got we've got netwear Service

741
00:38:23.519 --> 00:38:26.400
<v Speaker 8>and I still maintain NDS is a better directory than

742
00:38:26.440 --> 00:38:30.480
<v Speaker 8>ad will ever wish it was. And all of our

743
00:38:30.519 --> 00:38:33.519
<v Speaker 8>academic departments had netwear service and they were all netwere

744
00:38:33.679 --> 00:38:38.159
<v Speaker 8>five one big NDS. But then departments had their own compute.

745
00:38:39.320 --> 00:38:44.760
<v Speaker 8>So our electronic imaging department they did computer graphics and

746
00:38:44.760 --> 00:38:47.840
<v Speaker 8>that kind of stuff. They got silicon graphics, really nice

747
00:38:47.840 --> 00:38:50.880
<v Speaker 8>shiny stuff. And it was like people and the organization

748
00:38:50.960 --> 00:38:53.559
<v Speaker 8>knew how they worked. What's that's an indigo? Well it

749
00:38:53.599 --> 00:38:58.480
<v Speaker 8>looks cool, no idea. Kem Inge had a dusty old

750
00:38:58.559 --> 00:39:00.519
<v Speaker 8>deck vax that was set in the back of a

751
00:39:00.599 --> 00:39:02.679
<v Speaker 8>room that somebody had bought, that was still sort of

752
00:39:02.679 --> 00:39:03.719
<v Speaker 8>ticking along, you know.

753
00:39:04.639 --> 00:39:06.800
<v Speaker 2>And it was still running, like I've've seen plenty of

754
00:39:06.800 --> 00:39:10.519
<v Speaker 2>those as paper weights, but it was still running.

755
00:39:10.679 --> 00:39:13.960
<v Speaker 1>Yeah, I'm hearing like the list of hardware, So how

756
00:39:14.079 --> 00:39:18.880
<v Speaker 1>much of the preparation was replaced the hardware and how

757
00:39:18.960 --> 00:39:21.880
<v Speaker 1>much was Oh, we had the source code to this,

758
00:39:22.039 --> 00:39:25.239
<v Speaker 1>let's we got to fix this code or this database.

759
00:39:25.280 --> 00:39:27.159
<v Speaker 1>How much of it was software versus hardware?

760
00:39:27.679 --> 00:39:32.119
<v Speaker 8>Surprisingly little actually was replaced the hardware. So again as

761
00:39:32.119 --> 00:39:34.559
<v Speaker 8>an academic computer center, we were organized. We had a

762
00:39:34.599 --> 00:39:37.960
<v Speaker 8>thing we called rolling replacement, so we replaced twenty five

763
00:39:38.000 --> 00:39:41.559
<v Speaker 8>percent of our computer estate every year. So we didn't

764
00:39:41.599 --> 00:39:44.880
<v Speaker 8>have that much in terms of legacy gear ourselves. Right,

765
00:39:45.039 --> 00:39:48.840
<v Speaker 8>some departments had older compute and we helped them try

766
00:39:48.880 --> 00:39:53.440
<v Speaker 8>and work out budgets and replacement plans for desktop PCs.

767
00:39:54.480 --> 00:39:56.719
<v Speaker 8>A lot of what we were doing was very much

768
00:39:58.000 --> 00:40:02.280
<v Speaker 8>cataloging in a state of applicationations, which was well into

769
00:40:02.320 --> 00:40:08.639
<v Speaker 8>the hundreds, right, with everything from like weird scientific chemical

770
00:40:08.719 --> 00:40:16.039
<v Speaker 8>modeling applications and finite element analysis and CAD and compute

771
00:40:16.119 --> 00:40:18.199
<v Speaker 8>all the way down the word processes an office and

772
00:40:18.239 --> 00:40:21.000
<v Speaker 8>that kind of stuff. Sure, and it's like, well, we've

773
00:40:21.000 --> 00:40:22.880
<v Speaker 8>got a catalog at all, We've got to check with

774
00:40:23.119 --> 00:40:25.760
<v Speaker 8>all of the distributors whether this stuff is y two

775
00:40:25.800 --> 00:40:28.360
<v Speaker 8>K compliant and if it's not, is there going to

776
00:40:28.360 --> 00:40:30.239
<v Speaker 8>be a patch? And if there isn't a patch, well,

777
00:40:31.079 --> 00:40:32.199
<v Speaker 8>what's our contingency?

778
00:40:32.400 --> 00:40:34.800
<v Speaker 2>Yeah, what's the work around? Or does it is it relevant?

779
00:40:34.840 --> 00:40:38.320
<v Speaker 2>Like if you're not analyzing data across from ninety ninety

780
00:40:38.360 --> 00:40:41.679
<v Speaker 2>two thousand. Does it really matter exactly?

781
00:40:41.840 --> 00:40:44.559
<v Speaker 8>You know, if the lab is out partying, does it

782
00:40:44.639 --> 00:40:47.360
<v Speaker 8>matter if the mass spec isn't why two K compliant?

783
00:40:47.360 --> 00:40:50.760
<v Speaker 8>If it switched off? Right, So it was very much

784
00:40:50.760 --> 00:40:54.400
<v Speaker 8>a lot of spreadsheets, right of what have we got?

785
00:40:54.480 --> 00:40:55.440
<v Speaker 8>Does it tick the box?

786
00:40:55.800 --> 00:40:58.920
<v Speaker 2>And then but a software inventory is something you probably

787
00:40:58.920 --> 00:41:01.760
<v Speaker 2>needed anyway. This was an excuse to get one.

788
00:41:01.880 --> 00:41:06.280
<v Speaker 8>Yes, I mean we had again, we knew what software

789
00:41:06.320 --> 00:41:11.199
<v Speaker 8>we had, right because we maintained the student clusters. We've

790
00:41:11.239 --> 00:41:13.480
<v Speaker 8>got this huge list of applications that we had to

791
00:41:13.480 --> 00:41:17.119
<v Speaker 8>install for students to learn on. But the further away

792
00:41:17.400 --> 00:41:22.000
<v Speaker 8>from our own stuff, we got the thicker the fog, right,

793
00:41:22.519 --> 00:41:25.440
<v Speaker 8>and you could kind of walk into any office you like,

794
00:41:25.519 --> 00:41:27.480
<v Speaker 8>in any department and go what have you got? And

795
00:41:27.480 --> 00:41:30.039
<v Speaker 8>you'd learn about three new things and one of them

796
00:41:30.039 --> 00:41:32.000
<v Speaker 8>they only used on a Tuesday, and one of them

797
00:41:32.000 --> 00:41:33.559
<v Speaker 8>they bought. It was still in the box and three

798
00:41:33.639 --> 00:41:37.760
<v Speaker 8>years ago killed Let's make a note and what's important?

799
00:41:38.480 --> 00:41:41.000
<v Speaker 2>Yeah, no kidding. Did you get to a point where

800
00:41:41.039 --> 00:41:43.800
<v Speaker 2>there was applications that you had to fix yourself? Or

801
00:41:44.159 --> 00:41:47.320
<v Speaker 2>I mean academics also tend to write software in certain

802
00:41:47.360 --> 00:41:50.199
<v Speaker 2>spaces too. I've seen this software written by a chemical engineer.

803
00:41:50.599 --> 00:41:52.960
<v Speaker 2>It looked like an engineer wrote software right only.

804
00:41:54.719 --> 00:41:58.960
<v Speaker 8>So so stuff like that we we genuinely did, go well,

805
00:41:58.960 --> 00:42:01.280
<v Speaker 8>it's your problement now. So we had several people in

806
00:42:01.280 --> 00:42:07.039
<v Speaker 8>the computer center who did application support. Right, So we'd

807
00:42:07.079 --> 00:42:09.719
<v Speaker 8>got like a couple of Fortrend specialists and a few

808
00:42:09.719 --> 00:42:12.880
<v Speaker 8>other guys who were into certain languages, and part of

809
00:42:12.920 --> 00:42:16.119
<v Speaker 8>their job was to help both teach it and also

810
00:42:16.199 --> 00:42:18.199
<v Speaker 8>to support departments if they were trying to write their

811
00:42:18.199 --> 00:42:24.519
<v Speaker 8>own stuff. Most in house developed software, though, was like

812
00:42:24.840 --> 00:42:28.679
<v Speaker 8>Fox pro and Access. You know, there's two great pillars

813
00:42:28.679 --> 00:42:34.079
<v Speaker 8>of solid foundational computing. Our admin computer team had written stuff,

814
00:42:34.679 --> 00:42:37.840
<v Speaker 8>but they started with quite a long run up and

815
00:42:37.960 --> 00:42:40.599
<v Speaker 8>examined their stuff very careful and had programs to fix

816
00:42:40.679 --> 00:42:44.280
<v Speaker 8>it as they needed to. Most of the academic computer

817
00:42:44.360 --> 00:42:47.920
<v Speaker 8>centers stuff was you know, we need patches for Windows

818
00:42:47.960 --> 00:42:51.480
<v Speaker 8>ninety eight, ninety seven, eighty five, Office ninety seven, that

819
00:42:51.559 --> 00:42:55.400
<v Speaker 8>kind of stuff. We had some in house written software.

820
00:42:55.440 --> 00:42:58.239
<v Speaker 8>We had a magnificent student printing system that was entirely

821
00:42:58.280 --> 00:42:59.280
<v Speaker 8>written in Perl.

822
00:43:02.360 --> 00:43:02.920
<v Speaker 1>Languages.

823
00:43:03.440 --> 00:43:06.159
<v Speaker 8>Yeah, but I mean, so I did some research before

824
00:43:06.159 --> 00:43:08.039
<v Speaker 8>coming on right, I actually went and looked up things

825
00:43:08.079 --> 00:43:11.320
<v Speaker 8>like pearlam and Pull's statement on y two K is pearls?

826
00:43:11.320 --> 00:43:15.360
<v Speaker 8>Why too compliant? Like a pencil is y two K compliant?

827
00:43:15.599 --> 00:43:17.679
<v Speaker 8>You can write good stuff with pearl, you can write

828
00:43:17.679 --> 00:43:18.960
<v Speaker 8>bad stuff with sure?

829
00:43:19.239 --> 00:43:21.960
<v Speaker 2>Got it? Well? I ran in this all the time

830
00:43:22.000 --> 00:43:23.679
<v Speaker 2>with the projects that I was dealing with, where they

831
00:43:23.800 --> 00:43:26.840
<v Speaker 2>just didn't use the date structure, which was why too compliant.

832
00:43:26.840 --> 00:43:30.800
<v Speaker 2>They were storing dates and strings and they weren't compliant

833
00:43:30.800 --> 00:43:33.119
<v Speaker 2>to anything, and they were almost impossible to validate. So

834
00:43:33.320 --> 00:43:35.639
<v Speaker 2>you know, part of this is just untangling what have

835
00:43:35.760 --> 00:43:37.119
<v Speaker 2>you done with your dates?

836
00:43:37.440 --> 00:43:39.559
<v Speaker 1>Stuff that I was doing was all just using standard

837
00:43:39.599 --> 00:43:42.159
<v Speaker 1>date fields which were y two K compliants. Yeah, I

838
00:43:42.239 --> 00:43:43.280
<v Speaker 1>didn't have too much trouble.

839
00:43:43.679 --> 00:43:46.320
<v Speaker 8>I think a lot of our stuff, honestly, was like that.

840
00:43:46.360 --> 00:43:52.280
<v Speaker 8>We struggled more with departments simply running old stuff because

841
00:43:52.280 --> 00:43:56.559
<v Speaker 8>they'd never been bothered to upgrade, rather than actually stumbling

842
00:43:56.639 --> 00:43:59.079
<v Speaker 8>upon something that genuinely wasn't competitive.

843
00:43:59.119 --> 00:44:01.199
<v Speaker 2>So now there are four versions behind.

844
00:44:01.000 --> 00:44:04.760
<v Speaker 8>Again, once we'd moved away from the yeah, because well

845
00:44:04.760 --> 00:44:06.119
<v Speaker 8>it works, why we need to work gread?

846
00:44:06.639 --> 00:44:06.880
<v Speaker 2>Yeah?

847
00:44:06.880 --> 00:44:08.880
<v Speaker 8>You know, well word style was good enough.

848
00:44:09.760 --> 00:44:12.679
<v Speaker 2>Enough, like January first, two thousand rolls around and all

849
00:44:12.679 --> 00:44:16.360
<v Speaker 2>the software bursts into flames either. Right, it's just if

850
00:44:16.400 --> 00:44:19.639
<v Speaker 2>you have to do something spanning across those the ninety

851
00:44:19.719 --> 00:44:22.360
<v Speaker 2>ninety two thousand, if it doesn't do date Maath properly,

852
00:44:22.480 --> 00:44:23.639
<v Speaker 2>dumb things are going to have.

853
00:44:23.960 --> 00:44:25.320
<v Speaker 1>Yeah, that's the gist of it.

854
00:44:25.679 --> 00:44:29.480
<v Speaker 8>Fundamentally, we checked everything as we approach the Christmas break

855
00:44:30.199 --> 00:44:32.400
<v Speaker 8>because we're a university, should we we shut down for

856
00:44:32.440 --> 00:44:36.079
<v Speaker 8>a week? Yeah, you know, the core services were all

857
00:44:36.159 --> 00:44:40.880
<v Speaker 8>running on some Solaris, Our network servers were fine, most

858
00:44:40.880 --> 00:44:44.280
<v Speaker 8>of the desktop machines would be turned off. Anything people

859
00:44:44.320 --> 00:44:48.320
<v Speaker 8>weren't sure about was turned off, and it was much

860
00:44:48.360 --> 00:44:51.440
<v Speaker 8>more a focus on how do we make the system

861
00:44:52.239 --> 00:44:55.280
<v Speaker 8>safe than necessarily how do we continue doing business over

862
00:44:55.320 --> 00:44:59.599
<v Speaker 8>the year termination? Right, because we're university, so we're closed

863
00:44:58.920 --> 00:45:02.079
<v Speaker 8>to learn first thing on January first.

864
00:45:01.960 --> 00:45:05.639
<v Speaker 2>Which makes me think the week back after the Christmas

865
00:45:05.639 --> 00:45:07.760
<v Speaker 2>break would have been the hairy week because now you're

866
00:45:07.760 --> 00:45:12.280
<v Speaker 2>turning stuff back on again. You don't know what's going

867
00:45:12.320 --> 00:45:14.559
<v Speaker 2>to happen now, or you know, you're not sure, and

868
00:45:14.599 --> 00:45:16.639
<v Speaker 2>it's every department probably got a little bit of it,

869
00:45:16.679 --> 00:45:18.679
<v Speaker 2>so you're just sort of staring at the phone waiting

870
00:45:18.719 --> 00:45:19.559
<v Speaker 2>for it to go off.

871
00:45:20.000 --> 00:45:24.400
<v Speaker 8>Yeah, basically. But again, I think the problem is we

872
00:45:24.440 --> 00:45:27.079
<v Speaker 8>all did such a jolly good job of the planning

873
00:45:27.239 --> 00:45:29.880
<v Speaker 8>and the lists of things we had to be careful with, right,

874
00:45:29.920 --> 00:45:31.719
<v Speaker 8>The Y two K was such a non event for

875
00:45:31.760 --> 00:45:33.920
<v Speaker 8>all of us, and it's well.

876
00:45:34.039 --> 00:45:36.639
<v Speaker 2>You suddenly had a deadline to get all your updates done,

877
00:45:36.760 --> 00:45:39.079
<v Speaker 2>and if you did them, you're probably fine.

878
00:45:39.280 --> 00:45:39.480
<v Speaker 7>Yeah.

879
00:45:39.719 --> 00:45:42.800
<v Speaker 8>Yeah, I mean the cool thing is I was looking

880
00:45:42.840 --> 00:45:44.639
<v Speaker 8>at the way back machine before I came on and

881
00:45:45.039 --> 00:45:47.840
<v Speaker 8>you can still see our Y two K page for departments,

882
00:45:47.880 --> 00:45:50.679
<v Speaker 8>and it's literally just a list of updates. Download this install,

883
00:45:50.679 --> 00:45:51.679
<v Speaker 8>this install, this install.

884
00:45:51.679 --> 00:45:53.079
<v Speaker 2>Listen, you'll be fine, right.

885
00:45:53.800 --> 00:45:58.280
<v Speaker 8>The actual Y two K plans sadly are locked away

886
00:45:58.320 --> 00:46:01.639
<v Speaker 8>between behind authentic K, so lost in the.

887
00:46:01.599 --> 00:46:03.920
<v Speaker 2>Midst of time. Yeah. What's hidden is the sheer amount

888
00:46:03.920 --> 00:46:05.960
<v Speaker 2>of work it took to get that list right.

889
00:46:06.119 --> 00:46:09.559
<v Speaker 8>Yeah, yeah, and the number of trees we killed in

890
00:46:10.039 --> 00:46:12.559
<v Speaker 8>finding the list of software, checking all the hard ware,

891
00:46:13.000 --> 00:46:15.079
<v Speaker 8>making sure all the departments had a plan and they'd

892
00:46:15.079 --> 00:46:16.280
<v Speaker 8>all signed it off, right.

893
00:46:16.199 --> 00:46:19.119
<v Speaker 2>That's right. That's where they knew. They knew what to

894
00:46:19.159 --> 00:46:21.239
<v Speaker 2>turn off, they knew what to update, and they knew

895
00:46:21.239 --> 00:46:24.719
<v Speaker 2>who to call. The week of the first week of January. Yeah,

896
00:46:24.800 --> 00:46:29.280
<v Speaker 2>that's a good plan. Yeah, well done, Rick. It's a

897
00:46:29.320 --> 00:46:31.800
<v Speaker 2>great story, and it's just sort of a reality of

898
00:46:31.920 --> 00:46:32.559
<v Speaker 2>this was a lot.

899
00:46:32.679 --> 00:46:34.800
<v Speaker 1>There was a lot of housekeeping and a bit of firefighting.

900
00:46:35.119 --> 00:46:39.159
<v Speaker 1>H Yeah, good story, good stuff. Thanks for sharing it

901
00:46:39.199 --> 00:46:39.480
<v Speaker 1>with us.

902
00:46:40.039 --> 00:46:41.960
<v Speaker 8>You're very welcome with the pleasure as always.

903
00:46:42.159 --> 00:46:47.119
<v Speaker 1>All right, So that's our show, Richard. Yeah, I'm glad.

904
00:46:47.159 --> 00:46:49.280
<v Speaker 2>We got a few different stories from different folks and

905
00:46:49.320 --> 00:46:52.000
<v Speaker 2>where they were and how they dealt with these issues.

906
00:46:52.039 --> 00:46:54.039
<v Speaker 2>I mean, some of it wasn't that big a deal

907
00:46:54.079 --> 00:46:57.239
<v Speaker 2>to software updates, but sometimes you had applications that needed

908
00:46:57.239 --> 00:46:58.639
<v Speaker 2>to be fixing. You had to go through them line

909
00:46:58.679 --> 00:47:01.480
<v Speaker 2>by line. That's certainly the work I did the first

910
00:47:01.480 --> 00:47:03.960
<v Speaker 2>half of ninety nine was doing line by line fixes,

911
00:47:03.960 --> 00:47:06.000
<v Speaker 2>although we wrote partiers and things to do it as

912
00:47:06.079 --> 00:47:08.239
<v Speaker 2>quickly as possible, because there was a lot of code

913
00:47:08.320 --> 00:47:08.559
<v Speaker 2>of you.

914
00:47:08.960 --> 00:47:11.800
<v Speaker 1>That's right, and you know, the world remembers nothing happening.

915
00:47:12.320 --> 00:47:14.559
<v Speaker 2>But as we did, we did a good job. It

916
00:47:14.719 --> 00:47:19.639
<v Speaker 2>a good job, that's right, became a non event. All right.

917
00:47:19.760 --> 00:47:22.320
<v Speaker 1>Well, I guess that's all we have for today, and

918
00:47:22.400 --> 00:47:24.880
<v Speaker 1>we'll see you next time on dot net.

919
00:47:24.800 --> 00:47:27.039
<v Speaker 2>Rocks for episode two thousand.

920
00:47:27.559 --> 00:47:52.599
<v Speaker 9>Yes dot net Rocks is brought to you by Franklin's

921
00:47:52.679 --> 00:47:56.719
<v Speaker 9>Net and produced by Pop Studios, a full service audio,

922
00:47:56.800 --> 00:47:59.239
<v Speaker 9>video and post production facilities.

923
00:47:58.960 --> 00:48:02.199
<v Speaker 1>Located physically in New London, Connecticut, and of course in

924
00:48:02.280 --> 00:48:06.320
<v Speaker 1>the cloud online at pwop dot com.

925
00:48:06.519 --> 00:48:08.639
<v Speaker 10>Visit our website at d O T N E t

926
00:48:08.880 --> 00:48:12.880
<v Speaker 10>R O c k S dot com for RSS feeds, downloads,

927
00:48:13.039 --> 00:48:16.719
<v Speaker 10>mobile apps, comments, and access to the full archives going

928
00:48:16.760 --> 00:48:20.159
<v Speaker 10>back to show number one, recorded in September two thousand

929
00:48:20.159 --> 00:48:20.440
<v Speaker 10>and two.

930
00:48:21.039 --> 00:48:23.360
<v Speaker 1>And make sure you check out our sponsors. They keep

931
00:48:23.480 --> 00:48:26.639
<v Speaker 1>us in business. Now go write some code. See you

932
00:48:26.679 --> 00:48:27.119
<v Speaker 1>next time.

933
00:48:28.000 --> 00:48:29.800
<v Speaker 8>You got Javans

934
00:48:31.920 --> 00:48:44.079
<v Speaker 2>And