1
00:00:00,000 --> 00:00:02,200
Welcome to another episode of Empower Apps.

2
00:00:02,200 --> 00:00:04,344
I'm your host, Leo Dion.

3
00:00:04,344 --> 00:00:07,406
Today I'm joined by Georg Tuparev.

4
00:00:07,406 --> 00:00:09,888
Georg, thank you so much for coming on the show.

5
00:00:11,670 --> 00:00:13,420
Thank you for the invitation.

6
00:00:14,004 --> 00:00:20,938
you have extensive amount of experience and we're gonna be talking about some exciting
stuff today.

7
00:00:20,939 --> 00:00:25,548
But before we begin I'll let you go ahead and introduce yourself.

8
00:00:26,414 --> 00:00:30,917
Unfortunately I have also an extensive amount of years behind myself.

9
00:00:31,738 --> 00:00:46,365
So yeah I started hacking with computers when I was teenager, started with punch cards and
then programming satellites, telescopes, the then

10
00:00:46,365 --> 00:00:50,389
I went to I I was born in Bulgaria behind the Iron Curtain.

11
00:00:50,389 --> 00:01:01,938
Then I escaped to West Germany where I finished my studies and then during the studies I
also worked at the European Molecular Biology Lab where I start to understand what is a

12
00:01:01,938 --> 00:01:09,964
big computer like big SGI computers and parallel computing and vector processors and so
on.

13
00:01:10,345 --> 00:01:13,888
And then sorry, what?

14
00:01:13,888 --> 00:01:14,278
What?

15
00:01:14,278 --> 00:01:16,674
decade was that when you were starting the

16
00:01:16,674 --> 00:01:22,174
is that is something about say from the early nineties.

17
00:01:22,695 --> 00:01:23,375
I

18
00:01:23,375 --> 00:01:28,718
I bought my first NeXTcube, NeXTstation and nineteen at the end of 1990.

19
00:01:28,876 --> 00:01:29,755
Nights.

20
00:01:30,120 --> 00:01:36,383
So and then I went to work for a American consulting company.

21
00:01:36,952 --> 00:01:48,508
And I I didn't like very much working for a consulting company, so I started my own
consulting company and then we sold it and then this is my second one and here we are.

22
00:01:49,146 --> 00:01:50,156
Awesome.

23
00:01:50,297 --> 00:01:56,351
So we met at ServerSide.swift I can't see my shirt, I'm wearing the shirt today, but the
ServerSide.swift

24
00:01:56,351 --> 00:01:58,482
conference back in 24.

25
00:01:58,636 --> 00:02:02,878
you talked about large scale data, which we'll talk about later.

26
00:02:02,959 --> 00:02:10,703
But kind of let's let's just start talking about you've worked on some pretty big
projects, and a lot of them are

27
00:02:10,703 --> 00:02:13,645
in the science and research space.

28
00:02:14,453 --> 00:02:19,027
Kinda give a few examples of some of the large projects you've worked on.

29
00:02:19,268 --> 00:02:24,050
Yeah, I will just give two past and two current projects.

30
00:02:24,190 --> 00:02:30,114
One of the past projects is called Monet, like the the painter, the French painter.

31
00:02:30,182 --> 00:02:30,594
Okay.

32
00:02:30,594 --> 00:02:37,459
And it was probably the first fully robotic observatory control system in the world.

33
00:02:37,479 --> 00:02:43,662
we had large we controlled a large telescope in US, in South Africa, and Germany.

34
00:02:44,295 --> 00:02:48,856
by the way, all the projects that I'm talking about are using Apple technologies.

35
00:02:48,856 --> 00:02:52,219
So the other one is still ongoing.

36
00:02:52,219 --> 00:03:04,405
It is a very large transaction handling ~ project that sits between the large Dutch
companies, the Dutch government and the Dutch banks.

37
00:03:05,190 --> 00:03:11,453
and basically handles gazillions of transactions and so on, obvious stuff.

38
00:03:11,453 --> 00:03:19,177
Then we were called to help with archiving of the NASA Mars mission images

39
00:03:19,881 --> 00:03:27,766
So there is a huge archive, multiple, building full of our with archive with disks and
archives and so on.

40
00:03:27,846 --> 00:03:32,470
And we had to do a the UI for administrators.

41
00:03:32,470 --> 00:03:43,716
And the one that you mentioned, the that I talked about in the last server-side Swift
conferen conference, and something that we're we started just a few

42
00:03:43,844 --> 00:03:45,065
months ago.

43
00:03:45,065 --> 00:04:04,096
It's called Sky Observer, and it is a portal for astronomers and space scientists where we
keep information about space junk, about astronomical catalogues and observatories.

44
00:04:04,096 --> 00:04:09,319
There will be also a community for astronomers and space researchers and so on.

45
00:04:09,787 --> 00:04:12,731
So these are types of projects that we're we're talking.

46
00:04:12,731 --> 00:04:24,786
We had also projects like in the for the German police, for German education Ministry of
Education, for Henkel the the the the chemical giant Henkel in Germany and so on.

47
00:04:24,947 --> 00:04:26,849
But they're more in the past.

48
00:04:28,385 --> 00:04:30,878
This is I'm just going on Sky Observer.

49
00:04:30,878 --> 00:04:32,109
This is really cool.

50
00:04:32,109 --> 00:04:35,943
this is your this is your cause it says it's it's your company's project, right?

51
00:04:35,943 --> 00:04:37,574
Okay.

52
00:04:37,574 --> 00:04:38,436
baby.

53
00:04:38,436 --> 00:04:39,337
that's beautiful.

54
00:04:39,337 --> 00:04:41,930
Okay, yeah, I'll definitely put a link to that.

55
00:04:41,930 --> 00:04:54,337
it is bet b better and behind the scene there are many things already working but the UI
is very, very primitive and mostly hard kind of car almost c hard coded, just for people

56
00:04:54,337 --> 00:04:56,298
to to get some feedback.

57
00:04:56,701 --> 00:04:57,602
Yeah, very cool.

58
00:04:57,602 --> 00:04:59,843
We'll put a link to that in the show notes.

59
00:04:59,843 --> 00:05:04,697
So based on some of the projects that you've done, what are you you run a very small team?

60
00:05:04,697 --> 00:05:07,019
I don't how many folks are on your team?

61
00:05:07,019 --> 00:05:12,775
maximum at ma maximum about twelve, fifteen people, at the time about

62
00:05:12,775 --> 00:05:13,905
ten people.

63
00:05:14,030 --> 00:05:14,751
Okay.

64
00:05:14,751 --> 00:05:24,467
What are like what are some things that you find helpful when you're taking on these large
projects with such a small team?

65
00:05:25,712 --> 00:05:30,286
Well the first thing is that these type of projects never start complex.

66
00:05:30,307 --> 00:05:33,870
They start small and the complexity comes later.

67
00:05:34,211 --> 00:05:44,622
So for instance the banking project that we are talking about that I mentioned, I mean
started more than twenty years ago and started just as an archive for a bank bank

68
00:05:44,622 --> 00:05:47,024
statement of a Dutch credit card company.

69
00:05:47,428 --> 00:05:56,094
then slowly grown to this huge project that basically connects all the government and bank
and large corporation sites.

70
00:05:56,094 --> 00:05:58,035
And you cannot plant this one.

71
00:05:58,035 --> 00:06:10,482
The other thing is that at least as important as know knowing or understanding the
software development, you have to understand the domain of the project.

72
00:06:10,722 --> 00:06:11,873
Is it an astronomy?

73
00:06:11,873 --> 00:06:16,985
Is it a finance, government, medicine, and so on, healthcare?

74
00:06:17,105 --> 00:06:19,394
And this is a very, very important point.

75
00:06:19,394 --> 00:06:26,340
if you look at our team, I think there is only one person that were that is a software
engineer.

76
00:06:26,581 --> 00:06:34,153
We have physicists, mathematician, engine astronomer, all kinds of people, even a drummer.

77
00:06:34,589 --> 00:06:37,776
but not really not the software engineers.

78
00:06:37,776 --> 00:06:42,605
And this is very, very important skill that we bring together.

79
00:06:45,130 --> 00:06:52,095
When we start such projects, we almost never plan to have the project to be multi-year
project.

80
00:06:52,836 --> 00:06:57,239
We always think that is a half a year, a couple of months, we'll finish.

81
00:06:57,239 --> 00:07:01,162
And then 20 years later we are still doing development.

82
00:07:01,963 --> 00:07:08,387
And the other thing is that during these development times, the technology also evolves.

83
00:07:08,732 --> 00:07:13,514
if you if you're talking about Monet, for instance, where we started about 2005.

84
00:07:13,654 --> 00:07:15,675
We started with Objective-C.

85
00:07:15,675 --> 00:07:20,279
And some of the frameworks then we used WebObjects at the time.

86
00:07:20,279 --> 00:07:23,220
WebObjects we still use for many of the projects.

87
00:07:23,220 --> 00:07:31,126
unfortunately, because there is no better replacement of EOF, not because of the WebObjects itself, the web part of the WebObjects, but EOF.

88
00:07:31,126 --> 00:07:36,939
But now you you started with a technology that is 25 years old.

89
00:07:37,579 --> 00:07:42,057
Actually, Marie Huclaud, I don't know if you know him, he was the CTO of NeXT.

90
00:07:42,057 --> 00:07:43,074
he sent me a

91
00:07:43,074 --> 00:07:49,381
ver he sent me the source code of WebObjects 0.51 to check it.

92
00:07:49,381 --> 00:07:51,242
That was in 95.

93
00:07:51,395 --> 00:07:52,010
Okay.

94
00:07:52,010 --> 00:07:53,070
And still working.

95
00:07:53,070 --> 00:08:00,314
I mean it's a very solid technology, but now we have AI and all these new babies in the
gar kindergarten.

96
00:08:00,314 --> 00:08:04,515
so the technology evolves also within the project.

97
00:08:04,515 --> 00:08:15,659
So you have to be flexible to evolve this per technology and to focus on the such
architecture that can take both evolutions of complexity and evolution of technologies,

98
00:08:15,659 --> 00:08:17,300
and of course hardware.

99
00:08:18,962 --> 00:08:20,822
so sorry, business talk.

100
00:08:20,883 --> 00:08:28,922
how do you like do you do like fixed price or do you do like fixed price with maintenance
or hourly or if you mind me asking?

101
00:08:28,922 --> 00:08:33,737
'Cause especially if these are multi year projects I'm imagining.

102
00:08:33,737 --> 00:08:37,748
You you cannot make a fixed price for a 20 years project, no way.

103
00:08:37,748 --> 00:08:38,620
exactly.

104
00:08:38,620 --> 00:08:52,008
So our preferred stuff is I mean we we got some suggestion for a new functionality and we
give a we give a rough price estimate and this changes also.

105
00:08:52,008 --> 00:08:56,771
It is clear, I mean from the side of the client they add to the scope

106
00:08:57,131 --> 00:09:09,672
because we are using semi XP pro type of development with relatively short cycles, we can
say at the end of the cycle, okay, you have the right to the client have the right to add

107
00:09:09,672 --> 00:09:21,138
to the scope or removed from the scope, and we can say, okay, when you do this one, we can
also evaluate the price, or say it will cost you so much more or so much less.

108
00:09:21,760 --> 00:09:22,451
Right, right.

109
00:09:22,451 --> 00:09:23,973
That makes total sense.

110
00:09:24,014 --> 00:09:26,664
I was you you say fixed price multi year project.

111
00:09:26,664 --> 00:09:32,590
I I I would assume the government would be the only example where you'd have something
fixed price.

112
00:09:32,590 --> 00:09:38,371
yeah, even the government, I mean as I told you we w were yeah.

113
00:09:38,372 --> 00:09:40,553
No no we we we were

114
00:09:40,553 --> 00:09:45,112
we worked with government projects, I mean especially in Germany, police

115
00:09:45,112 --> 00:09:47,183
and Ministry of Education.

116
00:09:47,544 --> 00:09:56,432
And they understood that it is in their interest to to have a s some flexibility in the
projects.

117
00:09:56,466 --> 00:10:05,680
So we di di we decided that we will split it in smaller parts and they will put a maximum
budget for the project.

118
00:10:05,680 --> 00:10:08,762
After that they will say stop, this is good enough.

119
00:10:08,902 --> 00:10:10,583
And this is how we work.

120
00:10:11,583 --> 00:10:14,087
Or the other thing with government.

121
00:10:14,248 --> 00:10:15,200
The other thing with

122
00:10:15,200 --> 00:10:18,997
government is this that from year to year they have different budget.

123
00:10:18,997 --> 00:10:20,399
So if you start in this

124
00:10:20,399 --> 00:10:24,506
yeah, so you can switch to the next year's budget.

125
00:10:25,422 --> 00:10:31,619
Do they insist on any methodologies like waterfall for your work or are they pretty hands
off or?

126
00:10:32,843 --> 00:10:35,665
At the beginning they ask questions normally.

127
00:10:36,223 --> 00:10:45,491
we explain away how we worked and they normally say okay because they don't don't
understand what we are telling them.

128
00:10:46,279 --> 00:10:46,898
then

129
00:10:46,898 --> 00:10:47,788
yeah.

130
00:10:49,642 --> 00:10:53,986
yeah, I was just say gosh, what was her name?

131
00:10:54,908 --> 00:10:59,422
Who's who just recently passed away who did the Apollo code?

132
00:11:00,016 --> 00:11:01,249
yeah, the lady.

133
00:11:01,249 --> 00:11:02,889
~ yeah, yeah.

134
00:11:02,889 --> 00:11:03,475
I've

135
00:11:03,475 --> 00:11:04,888
I'm very bad with names, sorry.

136
00:11:04,888 --> 00:11:06,981
Yeah.

137
00:11:07,784 --> 00:11:08,563
Yeah, yeah.

138
00:11:08,563 --> 00:11:10,893
~ yeah, she recently passed away.

139
00:11:10,893 --> 00:11:12,957
She was like 80 or something.

140
00:11:12,957 --> 00:11:14,447
Yeah.

141
00:11:14,447 --> 00:11:14,968
But I

142
00:11:14,968 --> 00:11:22,404
I was like I could see why they did Waterfall because their programming was all hardware
based, essentially.

143
00:11:22,404 --> 00:11:32,746
So like they had to like build out it wasn't like s they call it software, but I wouldn't
even call it software because it's all built into like the hardware itself, it sounded

144
00:11:32,746 --> 00:11:33,496
like.

145
00:11:33,641 --> 00:11:37,324
but if you I don't know y have you been in Goddard Space Flight Center?

146
00:11:37,324 --> 00:11:42,448
~ okay, if you look at the manuals,

147
00:11:42,448 --> 00:11:45,190
I I've seen the the real manuals from Apollo.

148
00:11:45,190 --> 00:11:52,154
And they you see that even they did not work really waterfall.

149
00:11:52,615 --> 00:11:58,119
They they made each requirement in a waterfall way.

150
00:11:58,787 --> 00:12:03,626
But the requirement after requirements they were quite actually flexible.

151
00:12:04,626 --> 00:12:05,648
And ~

152
00:12:05,648 --> 00:12:08,872
this is why actually we brought people on the moon.

153
00:12:08,872 --> 00:12:12,617
If they were i doing real waterfall, I think we were still

154
00:12:12,925 --> 00:12:18,290
I guess I guess I meant you can't change the code once you send it into space.

155
00:12:18,290 --> 00:12:21,236
Like I'm I'm sure now you c go ahead.

156
00:12:21,236 --> 00:12:22,569
Apollo 13.

157
00:12:22,569 --> 00:12:24,782
They changed the the code on the way.

158
00:12:25,561 --> 00:12:25,982
really?

159
00:12:25,982 --> 00:12:26,823
Okay.

160
00:12:26,823 --> 00:12:30,109
That's how they got away with thr with okay.

161
00:12:30,109 --> 00:12:30,830
it.

162
00:12:30,989 --> 00:12:32,250
Yeah, yeah, yeah.

163
00:12:32,331 --> 00:12:33,772
Yeah, that's fair.

164
00:12:34,333 --> 00:12:35,353
So

165
00:12:36,554 --> 00:12:48,829
yeah, let's talk about with your small team how what kind of tools have you picked up or
used to help like automate a lot of what you're working on?

166
00:12:49,741 --> 00:13:02,250
well besides the obvious stuff like Xcode and Swift and so on for the for the modern
development and unfortunately Eclipse for still for the Java development.

167
00:13:02,891 --> 00:13:09,174
many of the tools we wrote ourselves, for instance, our build system is completely
custom-built.

168
00:13:09,174 --> 00:13:10,715
It's based on Git.

169
00:13:10,769 --> 00:13:15,304
But we started using Git the time when the submodules were crap.

170
00:13:15,304 --> 00:13:17,767
So we decided okay,

171
00:13:17,767 --> 00:13:20,953
yeah, but not so I mean less crap now.

172
00:13:20,953 --> 00:13:21,771
Okay, let's crap.

173
00:13:21,771 --> 00:13:28,859
So yeah, so we we started we we we basically made our custom build system.

174
00:13:29,521 --> 00:13:30,421
And

175
00:13:31,063 --> 00:13:33,982
Custom build system or custom version control?

176
00:13:34,173 --> 00:13:35,454
No, build system.

177
00:13:35,454 --> 00:13:36,615
It's based on

178
00:13:36,615 --> 00:13:43,900
it's based on Git, but we have I mean 100 repositories or something like this.

179
00:13:43,900 --> 00:13:52,385
And our build system basically picks up what you need and the version you need and so on
from for the for different projects.

180
00:13:52,566 --> 00:13:53,586
And also make

181
00:13:53,586 --> 00:13:56,908
also makes the package installation packages everything.

182
00:13:57,229 --> 00:13:57,569
So

183
00:13:57,569 --> 00:14:01,401
it's I know that sounds primitive.

184
00:14:01,977 --> 00:14:08,889
But actually it works very, very well because we can run also the tests there and all
kinds of stuff with this build system.

185
00:14:09,069 --> 00:14:14,041
And it runs all automatically all the night when when you have some changes and so on.

186
00:14:14,041 --> 00:14:15,272
So it's quite flexible.

187
00:14:15,272 --> 00:14:21,115
we we love workflows and workflows are both types.

188
00:14:21,115 --> 00:14:26,357
I mean we have work custom workflows for for things like the build system, of course.

189
00:14:26,465 --> 00:14:30,968
But also most of our projects are workflow-oriented.

190
00:14:30,968 --> 00:14:34,630
And we are thinking a lot about the APIs.

191
00:14:34,751 --> 00:14:38,213
And we're trying to make the APIs as independent as possible.

192
00:14:38,213 --> 00:14:39,684
First of all, I mean, for instance, if you

193
00:14:39,684 --> 00:14:48,260
take if if you take, for instance, the the Dutch project, the banking project, I mean, the
we cannot control the external APIs.

194
00:14:48,541 --> 00:14:52,275
So what we're what we are doing is many years ago we just

195
00:14:52,275 --> 00:14:59,660
Just an example, many years ago we enhanced the plist format, Apple plist format.

196
00:14:59,660 --> 00:15:03,484
we call it PixML, and I have no idea why we called it PixML.

197
00:15:03,484 --> 00:15:14,452
And we have a workflow that basically takes any any type of entry in the system, convert
it converts it into PixML.

198
00:15:14,612 --> 00:15:15,855
We if the

199
00:15:15,855 --> 00:15:20,608
If the information has to be persistent, we store it in a database.

200
00:15:20,989 --> 00:15:26,793
And we have a mapping file that says, okay, this PixML have to go to the database that and
that way.

201
00:15:26,813 --> 00:15:29,140
And then if we have to export it, we get the same way.

202
00:15:29,140 --> 00:15:37,461
I mean, convert from out of the persistent storage to into the PixML and then again to
whatever format we have to proceed.

203
00:15:37,921 --> 00:15:43,245
And we we are doing these workflows basically completely independent.

204
00:15:43,275 --> 00:15:46,309
not one program directly takes from the other and so on.

205
00:15:46,309 --> 00:15:53,366
There is a workflow controller that makes this work after kick kicks different independent
project after each other.

206
00:15:53,366 --> 00:15:58,421
And the reason is this makes also the the entire system extremely debuggable.

207
00:15:58,622 --> 00:15:59,011
You can

208
00:15:59,011 --> 00:16:03,707
run run just one module without having to test the other modules and so on.

209
00:16:04,707 --> 00:16:05,629
That's

210
00:16:07,921 --> 00:16:09,982
Yeah, that's pretty amazing.

211
00:16:10,031 --> 00:16:10,873
~

212
00:16:10,873 --> 00:16:17,983
just an example for this PixML, for instance, the for the Monet project, the Monet is the
the the robotic observatory.

213
00:16:17,983 --> 00:16:21,946
I mean we use the same format, the same PixML for logging.

214
00:16:22,246 --> 00:16:27,791
Like every event, I mean the telescope moved, the dome opened, the camera made shot and so
on.

215
00:16:27,791 --> 00:16:34,549
All the events were we are logging, but also we had a very good debugger where you send we
see

216
00:16:34,549 --> 00:16:40,053
Graphically, something like the old Core Data editor.

217
00:16:40,053 --> 00:16:41,554
We see graphically

218
00:16:41,554 --> 00:16:47,848
how packages come from one application to another where they're bottlenecks and so on.

219
00:16:47,848 --> 00:16:51,290
We can measure the queues and all kinds of stuff graphically.

220
00:16:51,290 --> 00:16:59,465
And this is actually we there was another project, two other projects trying to make the
same stuff, one in Berlin and one in MIT.

221
00:16:59,465 --> 00:17:00,202
And we

222
00:17:00,202 --> 00:17:05,188
We were the first one to finish it because actually they didn't have the graphical
debugger.

223
00:17:05,409 --> 00:17:11,537
And this is a very complex system and it was for them a nightmare to debug the system.

224
00:17:11,537 --> 00:17:12,628
But if you have such

225
00:17:12,628 --> 00:17:19,506
a if you have such a flexible workflow and you see what you're doing, you see immediately
also your problems.

226
00:17:20,114 --> 00:17:21,445
Yeah, yeah.

227
00:17:21,565 --> 00:17:23,006
That's pretty cool.

228
00:17:23,707 --> 00:17:35,639
so I am legally obligated to ask, because it's twenty twenty six, how has AI changed the
tools you use or any of your development process?

229
00:17:36,820 --> 00:17:41,342
we do not use AI for core development.

230
00:17:41,823 --> 00:17:46,425
We use the AI for writing documentation.

231
00:17:46,606 --> 00:17:47,286
Okay.

232
00:17:47,286 --> 00:17:53,310
And when I say documentation, first of all we are documenting our source code for
ourselves.

233
00:17:53,310 --> 00:17:55,901
not not for clients, for ourselves.

234
00:17:55,901 --> 00:18:00,654
So basically when after two years I have to make a fix, I understand what I've done.

235
00:18:00,794 --> 00:18:01,200
Yeah.

236
00:18:01,200 --> 00:18:11,455
And we we discovered that if you make this thing, then the AI can produce also very decent
documentation that is also for the public.

237
00:18:11,455 --> 00:18:14,117
We use AI for simple things.

238
00:18:14,117 --> 00:18:21,960
I mean, if you want to make a button from red, to switch the button from red to green,
obviously AI does a very, very good job.

239
00:18:22,361 --> 00:18:25,360
But for instance, we are working now one of the our

240
00:18:25,360 --> 00:18:34,678
projects is an open source standard for describing observatories that we just announced
last week in a conference in Armenia.

241
00:18:34,919 --> 00:18:43,846
And when I started or when we started working in this project, I mean we we asked the AI
well can you help us?

242
00:18:43,846 --> 00:18:51,730
And produce complete crap because there is no example from where the AI can learn about
it.

243
00:18:52,147 --> 00:18:55,832
You wanna I wanna deep dive into that 'cause I'm really interested.

244
00:18:55,833 --> 00:19:01,931
So what what was special about what you were doing the AI was not trained on it?

245
00:19:02,345 --> 00:19:15,592
As a technology, nothing special, but as a as a idea to have a single system, single
standard that describes any possible observatory, astronomical observatory, it doesn't

246
00:19:15,592 --> 00:19:20,244
matter on Earth, around Earth, on the moon, Mars, and so on.

247
00:19:20,925 --> 00:19:24,586
this was a new idea, basically to use a single standard.

248
00:19:25,207 --> 00:19:30,281
And if you go to say to astronomy portals and so on, there are hundreds of

249
00:19:30,281 --> 00:19:41,179
different API standards, discussions, papers, textbooks and so on, and the AI was not able
to extract a single simple solution.

250
00:19:41,657 --> 00:19:48,971
So you were basically saying, Hey, you you were using this to build this standard.

251
00:19:48,971 --> 00:19:49,711
Is that correct?

252
00:19:49,711 --> 00:19:52,443
You were using AI to build the standard and

253
00:19:52,443 --> 00:19:58,066
you told it here are some observatories and here's

254
00:19:58,066 --> 00:20:03,219
some here's some ways that it's currently described.

255
00:20:03,219 --> 00:20:06,940
Like across the board, and you said, Hey, take these

256
00:20:06,940 --> 00:20:10,215
and build the standard based on what people are currently doing.

257
00:20:10,215 --> 00:20:11,175
Ex exactly.

258
00:20:11,175 --> 00:20:12,145
Also papers

259
00:20:12,145 --> 00:20:18,389
mean describing what is a astronomical photograph formats and all the stuff.

260
00:20:18,468 --> 00:20:18,909
Okay.

261
00:20:18,909 --> 00:20:30,974
So there is a lot of information that you can feed, but if the AI does not have a example
of how to build exact concrete this concrete system, it does not do a good job.

262
00:20:31,254 --> 00:20:35,496
The where the AI helped us is for instance testing.

263
00:20:35,881 --> 00:20:37,337
Yeah, right.

264
00:20:37,337 --> 00:20:38,848
make test examples and so on.

265
00:20:38,848 --> 00:20:40,880
For this one, it's very, very okay.

266
00:20:40,880 --> 00:20:50,529
Another thing that we are trying to avoid in many cases AI is actually by for thinking
about the next generations.

267
00:20:50,529 --> 00:20:59,475
I'm afraid that you have to be able to ask the AI good questions to get good results.

268
00:20:59,705 --> 00:21:01,065
One hundred percent.

269
00:21:01,266 --> 00:21:01,646
Yeah.

270
00:21:01,646 --> 00:21:03,327
We just talked about this,

271
00:21:03,327 --> 00:21:05,654
I just talked about this with Stewart Lynch, just like

272
00:21:05,654 --> 00:21:06,289
Yeah.

273
00:21:06,289 --> 00:21:13,232
and Anthropic even has a p paper on it, like the more you're an expert in a subject, the
more you're gonna get out of it.

274
00:21:13,233 --> 00:21:13,578
Yeah.

275
00:21:13,578 --> 00:21:21,003
will get the students from today experts without they have no experience?

276
00:21:21,944 --> 00:21:22,684
So I

277
00:21:22,684 --> 00:21:32,010
was I was watching just a couple of months ago, I was watching the I forgot his name, the
guy who d developed main developer of the SQLite.

278
00:21:32,317 --> 00:21:33,135
Okay.

279
00:21:33,551 --> 00:21:37,156
And no no sorry, I I'm thinking for Bob Ma

280
00:21:37,156 --> 00:21:39,229
Bob Bob Martin, Uncle Bob.

281
00:21:39,812 --> 00:21:42,399
I was watching an ~ interview with him.

282
00:21:42,399 --> 00:21:43,273
tweet?

283
00:21:43,799 --> 00:21:46,169
No interview on YouTube.

284
00:21:46,169 --> 00:21:47,512
Well there was a tweet he said

285
00:21:47,512 --> 00:21:55,280
and I don't know if this is what you're talking about where he's like I'm not gonna look
at code anymore and I'm just gonna have AI write it and merge it.

286
00:21:55,280 --> 00:21:56,394
Is that what you're talking about?

287
00:21:56,394 --> 00:21:57,775
no, no, no, no.

288
00:21:57,775 --> 00:21:58,956
He was basically talking

289
00:21:58,956 --> 00:22:04,459
how how when he's teaching y he was asked how he teaches young people.

290
00:22:04,700 --> 00:22:09,602
And he his answer was I teach them like I'm teaching Canadians.

291
00:22:10,623 --> 00:22:21,281
So basically I give him a concrete job and ki they have to learn how to do this job and
then the next time it's a little bit more complicated job, but they ha do not have to

292
00:22:21,281 --> 00:22:22,271
touch AI.

293
00:22:22,810 --> 00:22:28,387
then somewhere in the middle of their education they can already start using a little bit
AI and so on.

294
00:22:28,888 --> 00:22:40,343
And I think this is a very good idea if we if we want to have, I mean if the company have
to continue further and have good developers, this is a very important thing.

295
00:22:42,418 --> 00:22:43,750
I have so many thoughts about that.

296
00:22:43,750 --> 00:22:46,664
What if the company doesn't care about good developers?

297
00:22:46,664 --> 00:22:47,826
That's unfortunately

298
00:22:47,826 --> 00:22:51,812
gonna be a big part of it because it's just push, push, push, right?

299
00:22:52,028 --> 00:22:56,085
Can you have a twenty years project without good developers?

300
00:22:58,185 --> 00:23:00,148
yeah, I mean it'll never succeed.

301
00:23:00,148 --> 00:23:01,809
It'll never succeed.

302
00:23:02,191 --> 00:23:03,191
Right?

303
00:23:03,252 --> 00:23:03,833
Right.

304
00:23:03,833 --> 00:23:04,374
Yeah, yeah.

305
00:23:04,374 --> 00:23:06,146
Successful, well that's you know

306
00:23:06,146 --> 00:23:06,557
Yeah.

307
00:23:06,557 --> 00:23:10,001
we don't always want a successful project and software, so

308
00:23:10,278 --> 00:23:10,970
Okay, yes.

309
00:23:10,970 --> 00:23:13,352
if you want to waste money you can of course.

310
00:23:13,352 --> 00:23:15,172
Right, there you go.

311
00:23:15,712 --> 00:23:16,543
what was I gonna say?

312
00:23:16,543 --> 00:23:30,533
Well the other the other thing too is I I I'd love your input on this, but one thing I've
thought of is how there's like levels of abstraction with programming and there's certain

313
00:23:30,533 --> 00:23:33,884
levels of like how close you are to the hardware.

314
00:23:33,905 --> 00:23:38,616
So for instance you have like electrical engineering, right, which is very into the
wiring.

315
00:23:38,616 --> 00:23:40,477
You have computer engineering.

316
00:23:40,477 --> 00:23:41,828
Which builds on top of that.

317
00:23:41,828 --> 00:23:46,420
You have computer science, which is where I'm at, for programmers, right?

318
00:23:46,420 --> 00:23:51,402
And then it almost seems like now, the agentic stuff is a layer on top of that.

319
00:23:51,402 --> 00:23:54,233
you'll always need people to build the code.

320
00:23:55,006 --> 00:24:01,456
And then you'll have people who'll just use agents and depending on your level of
expertise and interest,

321
00:24:01,456 --> 00:24:04,648
it seems like that's the way it's gonna go, is we'll have to have

322
00:24:04,936 --> 00:24:09,175
another degree or something on how to use these injected tools.

323
00:24:09,175 --> 00:24:09,866
But we still need

324
00:24:09,866 --> 00:24:14,924
computer science people for building the original code that doesn't already exist in a
way.

325
00:24:15,185 --> 00:24:22,170
again, it is very important that the people continue learning not only programming but
also their domains.

326
00:24:22,170 --> 00:24:22,951
For instance,

327
00:24:22,951 --> 00:24:36,859
for this for this project that is the the exabyte project, we had to understand how how
the a disk is damaged and how to pre prevent a file to be corrupted.

328
00:24:39,016 --> 00:24:49,209
we had to understand what happens if somebody just kicks the power cable and the the the
in the middle of write operation goes down and so on.

329
00:24:49,209 --> 00:24:51,810
So these are these are things that

330
00:24:52,380 --> 00:24:58,253
It is very important even on the software level to to continue understanding.

331
00:24:58,253 --> 00:24:59,158
But also

332
00:24:59,158 --> 00:25:00,041
percent.

333
00:25:00,534 --> 00:25:07,430
also thinks for instance, many people are making I don't know if if you have you worked
with MongoDB.

334
00:25:07,430 --> 00:25:09,578
I mean MongoDB works for

335
00:25:09,578 --> 00:25:17,962
yeah, MongoDB for 90% of the time works okay, and then it starts replicating or what
whatever, and you can forget it for six hours.

336
00:25:18,342 --> 00:25:20,853
And one and one of our intelligence.

337
00:25:20,853 --> 00:25:35,242
is always we don't have to be the fastest in the but we have to be the most predictable
and how and how and how to explain this type exactly exactly these are th these are yeah

338
00:25:35,242 --> 00:25:35,947
right?

339
00:25:35,947 --> 00:25:43,269
yeah these are these are exactly things that you have the core it is very important the
core to

340
00:25:43,269 --> 00:25:47,628
to really to put your thoughts and your dive into the source code.

341
00:25:47,628 --> 00:25:51,996
And then the periphery, the APIs, the stuff and so on that is not so important.

342
00:25:51,996 --> 00:25:55,081
Then you can let the AI help.

343
00:25:55,937 --> 00:25:56,297
Yeah.

344
00:25:56,297 --> 00:26:07,127
we're not like I am less and less convinced we're ever gonna hit AGI to where you have AI
that understands deep knowledge of astronomy while at the same time being an excellent

345
00:26:07,127 --> 00:26:07,937
Swift developer.

346
00:26:07,937 --> 00:26:10,089
I think it's just really hard to do that.

347
00:26:10,309 --> 00:26:10,560
So

348
00:26:10,560 --> 00:26:18,677
yeah, you need like you almost need to use separate agents and they need to be really well
trained on on the data to to understand what's going on.

349
00:26:18,677 --> 00:26:21,258
Yeah, totally one hundred percent.

350
00:26:21,980 --> 00:26:22,374
~

351
00:26:22,374 --> 00:26:36,059
I I mean an another thing is for instance we're trying I mean the pip my colleagues, we're
not we're trying not to work eight hours a day, although sometimes you have to, but we're

352
00:26:36,059 --> 00:26:37,622
trying to spend at least

353
00:26:37,622 --> 00:26:38,336
hours a day.

354
00:26:38,336 --> 00:26:39,816
Is that what you're trying to say?

355
00:26:39,816 --> 00:26:43,817
Less than eight hours and spend the rest of the time in reading.

356
00:26:43,938 --> 00:26:46,028
For instance,

357
00:26:46,028 --> 00:26:58,542
early in the morning, I'm well, in the morning, not early, when I wake up, the first thing
I do is I just open a Nature journal or Scientific American, read it from the first to the

358
00:26:58,542 --> 00:27:01,463
last pages just to see what's going on in the world.

359
00:27:02,308 --> 00:27:04,051
And d this helps a lot.

360
00:27:04,051 --> 00:27:12,050
This helps more than actually reading the f Swift four point one version and see what are
the differences.

361
00:27:12,050 --> 00:27:13,640
Yeah, right, right, right, right.

362
00:27:13,961 --> 00:27:14,381
Yeah.

363
00:27:14,381 --> 00:27:28,766
that's that's the thing I'm afraid of most with AI is that since there's less financial
incentive to be intelligent and smart because we can outsource it to these tools, that

364
00:27:28,987 --> 00:27:34,108
there's gonna be less of a drive for like education and expertise.

365
00:27:34,609 --> 00:27:37,800
because it's not financially necessary anymore, right?

366
00:27:37,800 --> 00:27:40,189
So it's like, yeah, that's kind of what I'm worried about.

367
00:27:40,189 --> 00:27:41,219
as well.

368
00:27:41,220 --> 00:27:46,905
we've already seen issues with literacy going down and stuff like that.

369
00:27:46,905 --> 00:27:47,266
So

370
00:27:47,266 --> 00:27:49,988
yeah, it's not great in that aspect.

371
00:27:51,291 --> 00:27:56,675
yeah, was there anything else you wanted to mention about AI before we get into Swift
stuff?

372
00:27:56,925 --> 00:28:08,010
Well, I think that I mean it will evolve and it evolves very fast and we have to another
thing that it's very important is I mean we are kind of

373
00:28:08,577 --> 00:28:11,028
We claim at least that we're smart people.

374
00:28:11,028 --> 00:28:15,189
So we should at least understand how AI works.

375
00:28:15,269 --> 00:28:18,160
We should have a basic understanding behind the maths.

376
00:28:18,160 --> 00:28:25,993
I mean you have to know what is a matrix operation, how the Markov chain are working, and
so on.

377
00:28:25,993 --> 00:28:30,382
To understand why to understand the behavior of the AI.

378
00:28:30,701 --> 00:28:37,933
So like we we understand how the computer works, we understand how this memory and CPU and
GPU and all this stuff.

379
00:28:37,933 --> 00:28:47,516
The same is true also for AI and and unfortunately this is because the math is, especially
if you go in deeper in the field, is quite complicated.

380
00:28:47,516 --> 00:28:55,438
very few people actually go that deep and they do not have explanations why something
works or does not work.

381
00:28:56,676 --> 00:28:57,576
Yeah.

382
00:28:57,576 --> 00:29:00,700
Yeah, I think that's totally correct.

383
00:29:00,700 --> 00:29:02,358
Is understanding the technology.

384
00:29:02,358 --> 00:29:06,344
I I think that helps using it the tool as well.

385
00:29:06,524 --> 00:29:07,925
yeah, totally.

386
00:29:08,415 --> 00:29:11,797
okay, let's talk about Swift.

387
00:29:12,078 --> 00:29:20,865
So you mentioned Java and WebObjects, but you also have some server side Swift stuff as
well as client side Swift stuff.

388
00:29:20,865 --> 00:29:22,106
Is that correct?

389
00:29:22,160 --> 00:29:23,042
yes.

390
00:29:23,216 --> 00:29:25,700
So how does that how does that set up work?

391
00:29:26,176 --> 00:29:30,499
First of all, for the server side Swift, we're using SwiftNIO.

392
00:29:30,499 --> 00:29:42,887
And we start building on top of SwiftNIO, we start building some extra functionality that
makes it a little bit more robust and more easy to use for everyone.

393
00:29:42,887 --> 00:29:47,049
And we're going also to make it open source when it's good enough.

394
00:29:47,645 --> 00:30:00,547
it is very different from what is Vapor or Kitura and all these existing projects because
because of our way of thinking that we inherited from the WebObjects.

395
00:30:01,428 --> 00:30:05,777
So we always try to think very deeply about two things.

396
00:30:05,777 --> 00:30:07,278
The first thing is

397
00:30:07,981 --> 00:30:12,465
the monitoring, the predictability that I mentioned before.

398
00:30:12,721 --> 00:30:25,627
So before writing any any line of Swift, we start thinking okay, how many transactions
this has to be, how does it have to be a 24-7 and so on, and all these questions that you

399
00:30:25,627 --> 00:30:27,038
have to answer.

400
00:30:27,038 --> 00:30:31,440
And then you choose the technology or choose how you're going to do.

401
00:30:31,440 --> 00:30:41,623
For instance, if you if if you're working in a batch data, which is quite often in the
industry, batch files, you don't have to

402
00:30:41,623 --> 00:30:46,325
Make the the trouble to have the trouble to use SwiftNIO.

403
00:30:46,325 --> 00:30:56,189
You can do just very simple Swift tool that eats something and produces something in a
classical Unix way, pipeline way.

404
00:30:56,789 --> 00:31:06,493
Of course, if you have to answer HTTP requests, then we use SwiftNIO for these type of
things.

405
00:31:06,905 --> 00:31:13,203
for there are many cases where we have to talk to different interfaces.

406
00:31:13,203 --> 00:31:22,304
We don't have to talk we don't have persistent data but we have to talk to different
interfaces ours or or for third parties

407
00:31:22,669 --> 00:31:25,782
In this case with SwiftNIO is extremely good.

408
00:31:25,782 --> 00:31:30,117
I mean the the application the applications are very sm very small.

409
00:31:30,117 --> 00:31:38,539
For instance for the telescop server we have just launched one news provider service and
the it is

410
00:31:39,062 --> 00:31:43,333
Basically, it's like a real-time blogging system.

411
00:31:43,373 --> 00:31:47,194
And the the memory footprint is about 60 megabytes.

412
00:31:47,415 --> 00:31:52,376
Where if you write the same stuff in the in a Java, it will be probably one gigabyte.

413
00:31:53,356 --> 00:31:58,298
So yeah, and all the stuff with the garbage collection and all the problems there.

414
00:31:58,298 --> 00:32:04,220
So for this type of thing, Swift is extremely good and extremely fast predictable.

415
00:32:05,168 --> 00:32:12,311
What we are missing with Swift unfortunately is the dynamic loading that we had in
Objective-C.

416
00:32:12,311 --> 00:32:13,971
Loadable bundles.

417
00:32:13,987 --> 00:32:15,904
Yeah, so how do you get around that?

418
00:32:16,092 --> 00:32:18,873
Well, with ugly tricks.

419
00:32:19,273 --> 00:32:28,055
Depends on the pro- I mean how first of all we are controlling our stuff, so we don't
really need to have for our own systems to have loadable bundles.

420
00:32:28,185 --> 00:32:28,475
Right.

421
00:32:28,475 --> 00:32:29,956
just compile them.

422
00:32:30,016 --> 00:32:44,092
But I'm I was talking to to engineers at Apple about this problem, and they told me that
they know about it, and they will actually probably allow something like this if you give

423
00:32:44,092 --> 00:32:46,883
them a good reason for.

424
00:32:47,103 --> 00:32:51,786
For instance, we're working on a astronomical image processing application.

425
00:32:52,250 --> 00:33:03,218
And we we understand very well 2D 3D images from telescopes, but we have no idea about
image processing of say gamma ray bursts and I mean

426
00:33:03,218 --> 00:33:04,919
gamma-ray satellites.

427
00:33:04,919 --> 00:33:10,843
So there are a couple of folks at Caltech and MIT that are gurus in this subject.

428
00:33:10,983 --> 00:33:15,761
So for them, will be the best if they wrote write their own plugin.

429
00:33:16,042 --> 00:33:17,562
And Apple say that

430
00:33:17,979 --> 00:33:27,384
In this case they will discuss with us and probably they will give special enhancements
but case by case.

431
00:33:27,384 --> 00:33:28,095
Yeah.

432
00:33:28,095 --> 00:33:31,799
Have you looked at so this is macOS, correct?

433
00:33:33,022 --> 00:33:34,698
Are these apps in macOS?

434
00:33:34,698 --> 00:33:35,846
macOS, yeah.

435
00:33:35,846 --> 00:33:39,331
Have you looked like ExtensionKit or anything like that

436
00:33:39,611 --> 00:33:43,388
Yeah yeah it it solves many of the problems.

437
00:33:44,501 --> 00:33:45,552
not all.

438
00:33:45,762 --> 00:33:46,555
Okay.

439
00:33:48,321 --> 00:33:48,892
Yeah.

440
00:33:48,892 --> 00:33:51,244
Yeah, that totally is something that's that's missing.

441
00:33:51,244 --> 00:33:55,740
It's just being able to create a plugin system or something like that.

442
00:33:55,740 --> 00:33:56,118
Yeah.

443
00:33:56,118 --> 00:33:58,660
~ yeah, I I totally get it.

444
00:33:59,162 --> 00:34:07,449
what do you write in your new so your all your new projects are Swift only, pure Swift?

445
00:34:07,583 --> 00:34:20,905
No, we are using, as I said, for persistent for persistent data, say writing to Postgres
and so on, we are using still WebObjects because of the EOF.

446
00:34:21,100 --> 00:34:21,509
Okay.

447
00:34:21,509 --> 00:34:28,275
~ also we we prototyped from time to time when we have to just understand the pro problem.

448
00:34:28,275 --> 00:34:34,541
We might have also a prototype in Python or we have a lot of shell scripts.

449
00:34:34,601 --> 00:34:42,347
Some of them are already written in Swift, but most of them are still real shell scripts,
old shell script bash scripts.

450
00:34:42,597 --> 00:34:45,582
Remind again why are you using WebObjects?

451
00:34:46,340 --> 00:34:49,982
EOF, this is the processor of the Core Data.

452
00:34:50,413 --> 00:34:51,227
Okay.

453
00:34:52,124 --> 00:34:57,987
And it is works with any database with any I mean it's extremely sizable.

454
00:34:58,100 --> 00:35:03,409
I mean our database is you you the first time that we've seen how a

455
00:35:03,409 --> 00:35:08,743
long integer got suddenly negative in a database by the the prime key.

456
00:35:08,743 --> 00:35:17,570
It was already 15 years ago, so we really use huge databases that Core Data and so on
cannot manage.

457
00:35:18,004 --> 00:35:18,384
Got it.

458
00:35:18,384 --> 00:35:19,185
Okay.

459
00:35:19,185 --> 00:35:20,085
Okay.

460
00:35:21,347 --> 00:35:26,597
so what parts of your code do you share between the server and the client?

461
00:35:28,451 --> 00:35:32,833
for instance I'll give you an example for instance for this exabyte.

462
00:35:32,973 --> 00:35:37,136
For exabyte we started writing some examples.

463
00:35:37,516 --> 00:35:39,838
for instance photo archive.

464
00:35:39,838 --> 00:35:42,039
It's first for us, but also

465
00:35:42,039 --> 00:35:45,561
we want to use it also for our astronomy imaging.

466
00:35:45,622 --> 00:35:49,104
So the the access to the files

467
00:35:49,697 --> 00:35:56,421
Basically the library that accesses the files on the server and the client site is the
same, virtually the same.

468
00:35:56,537 --> 00:35:57,335
Mm.

469
00:35:57,342 --> 00:36:05,687
Because the models, the models, I mean the model part of the data is very sim either the
same or very similar.

470
00:36:06,617 --> 00:36:12,161
well, since you brought it up, let's talk a little bit about the exabyte stuff.

471
00:36:12,392 --> 00:36:13,473
you did a really great talk.

472
00:36:13,473 --> 00:36:16,231
That's where we met at ServerSide.swift a couple of years ago.

473
00:36:16,231 --> 00:36:18,707
I'll post a link to the YouTube video.

474
00:36:19,068 --> 00:36:24,952
But the primary purpose of that top talk is explaining large storage.

475
00:36:24,952 --> 00:36:29,526
Now what what are we when we're talking about large storage, what exactly are we talking
about?

476
00:36:29,920 --> 00:36:43,375
well we never we never had the the financing for such a large storage to be developed, but
we made basically prototypes and expi ex experiments that should in theory and we're quite

477
00:36:43,375 --> 00:36:51,049
convinced actually in practice too will scale scale up until say fifty hundred exabyte.

478
00:36:52,210 --> 00:36:54,796
So really large yeah, yeah.

479
00:36:54,796 --> 00:36:55,609
exabytes.

480
00:36:55,609 --> 00:36:57,947
How many terabytes is that?

481
00:36:57,947 --> 00:36:59,621
fifty or hundred.

482
00:37:00,827 --> 00:37:02,392
Yeah, one exabyte

483
00:37:02,392 --> 00:37:05,078
so one exabyte is thousand terabytes.

484
00:37:06,515 --> 00:37:07,199
Wow.

485
00:37:07,199 --> 00:37:08,140
Okay.

486
00:37:08,484 --> 00:37:10,350
And these are all photos.

487
00:37:11,016 --> 00:37:19,828
no, it could be for many for instance the these type of projects they have to sell solve
in say NASA in CERN in government and so on.

488
00:37:19,828 --> 00:37:25,554
There are many places, I mean obviously Apple have to solve also these type of projects
and so on.

489
00:37:25,876 --> 00:37:31,939
the the the other things that we were thinking at the time because we we start developing
this one.

490
00:37:31,939 --> 00:37:35,836
We we started this is the third version of our data archive.

491
00:37:35,836 --> 00:37:39,962
I mean the first version we started already 25 years ago.

492
00:37:40,083 --> 00:37:46,505
And then we are using currently we are using the second version and now we are slowly
migrating to the third version.

493
00:37:46,505 --> 00:37:51,527
And each time it gets 10 times or 100 times larger and faster.

494
00:37:51,947 --> 00:37:52,927
~

495
00:37:53,068 --> 00:37:53,858
so

496
00:37:53,858 --> 00:38:02,601
The the the reason that we started this is actually we would like we w we would like to
collect the information about space junk.

497
00:38:02,669 --> 00:38:11,660
And there are observatories that are somewhere in say in Namibia or somewhere in the
mountain mountains of Chile or so on and so on, where they don't have a lot good

498
00:38:11,660 --> 00:38:13,572
connection, internet connection.

499
00:38:13,572 --> 00:38:24,601
So even we designed and tested small basically hardware pack that will c harbor about half
or one exabyte of data that we can just put

500
00:38:24,978 --> 00:38:34,083
close to the observatory and then we thought okay probably they will not have also
continuous power supply because of weather and so on and so on.

501
00:38:34,083 --> 00:38:34,843
So we

502
00:38:34,843 --> 00:38:47,612
have we have to feed this in this with electricity also with solar panels and batteries so
it has to be extremely well done for power supply and

503
00:38:47,612 --> 00:38:49,840
so basically this means also that we

504
00:38:49,840 --> 00:39:01,046
we the disk that we are not using it's turned turned off the computer that is not used is
turned off and then turned on and so on and so on so just to yeah yeah yeah

505
00:39:01,519 --> 00:39:13,831
So and of course when you think about now for these gigantic data centers where ever
everything works at the same time and no one thinks about the power supply, actually these

506
00:39:13,831 --> 00:39:17,854
type of thoughts are actually very could be very useful for them too.

507
00:39:18,127 --> 00:39:19,207
Yeah, right.

508
00:39:19,287 --> 00:39:24,980
one of the other things you mentioned was like data transfer.

509
00:39:24,980 --> 00:39:30,301
So it's a real is it like some satellite system that's really slow or

510
00:39:30,301 --> 00:39:32,083
It's too s anything is too slow.

511
00:39:32,083 --> 00:39:33,536
I mean, for instance

512
00:39:33,536 --> 00:39:41,622
w for one of the telescopes that we were modeling, it is from a Fren Austrian company,
Assel, they have like a four four

513
00:39:41,622 --> 00:39:50,964
60 centimeter telescopes and on the same mount and make at the same time for 25 six
megabyte images and each

514
00:39:50,964 --> 00:39:57,225
image takes three seconds so you you can imagine what output this this machine gives so
there is

515
00:39:57,225 --> 00:40:01,907
no there is no no cable that can transfer so much data.

516
00:40:01,907 --> 00:40:05,111
So what we were thinking so so

517
00:40:05,111 --> 00:40:06,873
sneaker what do they call it?

518
00:40:06,873 --> 00:40:08,685
Sneaker transfer.

519
00:40:08,685 --> 00:40:09,726
Gosh, what is that called?

520
00:40:09,726 --> 00:40:13,158
Is essentially how you're transferring data.

521
00:40:13,158 --> 00:40:13,746
Is that

522
00:40:13,746 --> 00:40:19,460
basic basically w when when we thought when w when the the storage is full we replace it.

523
00:40:19,460 --> 00:40:27,136
We bring the storage back home and transfer the store the that data at home and then put a
new storage there.

524
00:40:27,298 --> 00:40:28,108
Yes.

525
00:40:28,509 --> 00:40:29,329
Okay.

526
00:40:29,329 --> 00:40:34,022
Sneaker net, where it's like physically physically you have to take the hard drive.

527
00:40:34,022 --> 00:40:35,553
Is there

528
00:40:35,553 --> 00:40:40,015
I this okay, this is like a stupid question, but I'm gonna answer ask it anyways.

529
00:40:40,156 --> 00:40:50,682
Is there like an API for something like that where you can be like here, we need to
transfer this hard drive and it just basically like s sends a message to somebody to pick

530
00:40:50,682 --> 00:40:51,372
it up?

531
00:40:52,254 --> 00:41:01,118
Well there the we have a monitoring KPIs obviously and we can see okay when it's eighty
percent full we have to start planning the transfer.

532
00:41:02,768 --> 00:41:04,852
Okay, that's how it works.

533
00:41:04,852 --> 00:41:05,658
Yeah.

534
00:41:05,768 --> 00:41:06,688
Okay.

535
00:41:07,433 --> 00:41:07,973
Yeah.

536
00:41:07,973 --> 00:41:08,453
APIs.

537
00:41:08,453 --> 00:41:14,989
for instance there are already established APIs for the for the UPS systems for all kinds
of stuff.

538
00:41:14,989 --> 00:41:17,582
There are many, many already existing APIs.

539
00:41:18,021 --> 00:41:18,782
Got it.

540
00:41:18,782 --> 00:41:19,742
Okay.

541
00:41:19,802 --> 00:41:21,184
wow, we talked a lot a lot.

542
00:41:21,184 --> 00:41:21,854
This was great.

543
00:41:21,854 --> 00:41:24,977
Was there anything else you want to talk about before we close out?

544
00:41:25,578 --> 00:41:40,979
Yeah, I mean at the moment because we're finishing several large projects and we were we
kind of would like also to work again with other clients and because we have expertise in

545
00:41:40,979 --> 00:41:46,262
that we never tapped on for instance in the in healthcare in in

546
00:41:47,222 --> 00:42:00,134
satellite say remote sensing, agriculture and so on, we're at the moment looking also for
new new partners and clients so that we can learn something and they can have a solid

547
00:42:00,134 --> 00:42:01,295
system too.

548
00:42:01,794 --> 00:42:09,415
So you I I gave you I will give give you a URL to our website where yeah, yeah.

549
00:42:09,415 --> 00:42:09,846
So

550
00:42:09,846 --> 00:42:10,216
cool.

551
00:42:10,216 --> 00:42:15,882
and and pe and people just can drop me an email and so on and if they have questions

552
00:42:16,204 --> 00:42:16,815
Yeah.

553
00:42:16,815 --> 00:42:18,417
Georg, thank you so much for coming on.

554
00:42:18,417 --> 00:42:20,238
This was fantastic.

555
00:42:20,840 --> 00:42:24,374
you can check out his website, tuparev dot com.

556
00:42:24,374 --> 00:42:26,867
and we'll have links to all your socials and stuff.

557
00:42:26,867 --> 00:42:28,068
but this was really great.

558
00:42:28,068 --> 00:42:29,289
I enjoyed this.

559
00:42:29,356 --> 00:42:31,160
thank you for the invitation.

560
00:42:31,697 --> 00:42:35,281
People can find me online at brightdigit.com.

561
00:42:35,281 --> 00:42:40,064
if you're not, consider joining our Patreon to get early access to episodes like this.

562
00:42:40,064 --> 00:42:48,312
and if you enjoyed this episode, please like and subscribe on YouTube or give us a review
on whatever podcast player you're using.

563
00:42:48,312 --> 00:42:51,374
Thank you so much, and I look forward to talking to you again.

564
00:42:51,374 --> 00:42:52,535
Bye everybody.