TRANSKRYPCJA 🔗
WEBVTT
00:00.755 --> 00:10.260
[SPEAKER_03]: The original goal of Sai Thaik's two designs has special knives chips for the VK puff generation, but that's when like over another way.
00:10.860 --> 00:22.646
[SPEAKER_03]: We just found out like the GPUs or even FPJs, those hardware is like after share of hardware, they are good enough, they are good enough to carry out the current
00:25.447 --> 00:39.351
[SPEAKER_03]: So, which means we don't actually don't need to spend several, several media in building, like to do the chip tip out, then improve the efficiency of our own chip, we can just deny on them or off the shelf.
00:40.611 --> 00:43.712
[SPEAKER_03]: Manet's Neo-Fan, I'm the founder and CEO of Psychic.
00:47.032 --> 00:48.273
[SPEAKER_02]: This is Code Story.
00:49.572 --> 00:52.256
[SPEAKER_02]: a podcast bringing you interviews with tech visionaries.
00:52.376 --> 00:53.918
[SPEAKER_02]: Six, six months moonlighting goes.
00:53.938 --> 00:58.365
[SPEAKER_02]: It's the last and all of the backgrounds who share what it takes to change an industry.
00:58.485 --> 01:00.047
[SPEAKER_00]: I don't exactly know what to do.
01:00.108 --> 01:01.470
[SPEAKER_02]: It doesn't go as to get right.
01:02.340 --> 01:08.902
[SPEAKER_01]: who built the teams that have their bad company is its team's help each other, which is proud of our team.
01:09.162 --> 01:13.043
[SPEAKER_02]: Keeping scalability top of mind, all that infrastructure was up there.
01:13.063 --> 01:14.483
[SPEAKER_01]: Yes, we've been fighting it as we grew up.
01:14.623 --> 01:15.563
[SPEAKER_02]: Total waste of time.
01:15.983 --> 01:18.204
[SPEAKER_02]: The stories you don't read in the headlines.
01:18.704 --> 01:19.964
[SPEAKER_01]: It's not an easy thing to achieve.
01:19.984 --> 01:26.046
[SPEAKER_02]: To get yourself a deficit of off, try to begin to ride the ups and downs of the start-up line.
01:26.146 --> 01:27.706
[SPEAKER_01]: Need to really want it.
01:27.786 --> 01:29.106
[SPEAKER_02]: Not just about technology.
01:29.146 --> 01:31.267
[SPEAKER_02]: All this and more on code story.
01:32.856 --> 01:43.399
[SPEAKER_02]: I'm your host, Noah Labpart, and today how Leo Fan has built the first full-statt compute network so you can own the growth of compute on-chain.
01:49.674 --> 01:53.857
[SPEAKER_02]: Leo Fan grew up in China, performing his undergrad and masters within the country.
01:54.578 --> 01:57.580
[SPEAKER_02]: Eventually, he came to the States to get his PhD from Cornell.
01:58.380 --> 02:02.984
[SPEAKER_02]: Prior to his current venture, his experience has been an academia and research and computer science.
02:03.684 --> 02:05.145
[SPEAKER_02]: But outside of tech, he's a gamer.
02:05.606 --> 02:12.030
[SPEAKER_02]: In fact, he was pretty good at it, almost entering professional esports during his undergrad days, playing counterstrike and warcraft.
02:12.691 --> 02:18.235
[SPEAKER_02]: Besides that, he enjoys playing tennis and basketball and eating some good Chinese food or tacos.
02:21.348 --> 02:28.314
[SPEAKER_02]: In his engineering days, Leo discovered a very powerful system for crypto, with powerful properties to enable it to be so.
02:29.054 --> 02:39.583
[SPEAKER_02]: Once he figured out that this type of model can scale crypto systems, he wanted to build the first full-statt compute network to own the growth of on-chain compute.
02:42.245 --> 02:44.667
[SPEAKER_02]: This is the creation story of Scyc.
02:50.983 --> 02:56.264
[SPEAKER_03]: Sci-Thake is a combination of two words, the first two, like, C-Y is from Cypher.
02:56.904 --> 02:58.805
[SPEAKER_03]: The Cypher means cryptography.
02:59.645 --> 03:07.507
[SPEAKER_03]: The second part is the S-S-S-S-S coming from an A-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-S-
03:21.130 --> 03:40.122
[SPEAKER_03]: And the reason why I could be with I think is also as I just mentioned like we are like in my engineering days like I found the proof generation for their non-aggressions like to stone like by the way next their non-aggressions is a very powerful cryptocurrency instance so it has two nice properties
03:41.183 --> 04:04.475
[SPEAKER_03]: The first one is their non-H, so which means like for instance I want to transform like 10 they cash to you, but I don't need to like I only need to prove that like my balance in my wallets is like a larger than 10 which can like validate this transformation that I have like enough but coin in my wallet to pay this like transform, but I don't need to tell you like how much I
04:05.555 --> 04:14.517
[SPEAKER_03]: Yes, like very different from coin or Neck Ethereum, Neck for this two coin, like all the things they are like, public in the nature.
04:15.297 --> 04:18.438
[SPEAKER_03]: And the second one is Neck, the succinctness.
04:19.358 --> 04:27.520
[SPEAKER_03]: We know Neck, the poor generation of the case, like, where we cost away and, like, both in terms, and also in the computing resource.
04:28.200 --> 04:33.221
[SPEAKER_03]: But, like, the very fine Neck approved, it's like, much simpler, much faster.
04:33.841 --> 04:56.429
[SPEAKER_03]: You can use your cell phone to verify how they can prove in next and say 15 milliseconds and a cell phone and also the size of them prove it's also quite smooth like runs several At most in like several hundred kilobytes and we can't compress like white theorem block So one in theorem block contains a lot of like transactions.
04:57.009 --> 04:59.030
[SPEAKER_03]: We can't compress this like
04:59.318 --> 05:02.259
[SPEAKER_03]: the whole Ethereum block into just the one they kept proof.
05:03.459 --> 05:22.202
[SPEAKER_03]: Instead of re-executing all the things, all the transactions in that proof to the in that block to verify the validity of the block, we can just verify the they kept proof and say, since like we don't need to trust anyone, like
Load full transcript
we just need to trust the mess behind the they kept proof.
05:22.602 --> 05:26.263
[SPEAKER_03]: If this they kept proof is verified, then we can say that
05:26.983 --> 05:38.090
[SPEAKER_03]: The whole block is valid and then we can pause it so that's why like we can use the fixing as a thing left part of the people to scale up a lot of our blockchain.
05:39.071 --> 05:54.821
[SPEAKER_03]: But the two generations where it's not so that's why like in the beginning we are building some specialness hardware for the poor generation like we are using like we built the best FPJ hardware to have the best performance in the space.
05:55.301 --> 05:57.623
[SPEAKER_03]: Yeah, so that's how the next 5-8 got started.
06:00.524 --> 06:04.006
[SPEAKER_02]: Let's dive into the MVP for Sci-Second.
06:04.026 --> 06:06.928
[SPEAKER_02]: This is going to be interesting because you've got multiple factors here, right?
06:06.948 --> 06:13.532
[SPEAKER_02]: You've got the powerful model for crypto, you've got hardware to build, all the things I'm curious where you started.
06:13.572 --> 06:17.775
[SPEAKER_02]: Tell me about that MVP and what, how long it took to build and what sort of tools you're using to bring it to life.
06:19.714 --> 06:22.396
[SPEAKER_03]: In my opinion, like the MVP means like you.
06:22.856 --> 06:25.498
[SPEAKER_03]: Actually, there are some seem fun garlic products.
06:25.979 --> 06:28.801
[SPEAKER_03]: You're not just showing off your power, your performance.
06:29.201 --> 06:30.302
[SPEAKER_03]: You're actually like Arlene.
06:30.943 --> 06:32.544
[SPEAKER_03]: Some buy Arlene something.
06:32.564 --> 06:34.966
[SPEAKER_03]: I mean like Arlene's unbound iPhone or customer.
06:35.566 --> 06:37.987
[SPEAKER_03]: So, for that sense, I will say we would be a son.
06:38.548 --> 06:41.909
[SPEAKER_03]: We accelerate a poor generation for a lot of black manatees.
06:42.590 --> 06:52.555
[SPEAKER_03]: We took out about more than a half a year to have a GPU performance, to have a GPU version of some like CPU co-generation.
06:52.635 --> 06:56.197
[SPEAKER_03]: So, like with CPU co-generation, it took about two hours.
06:56.977 --> 07:08.262
[SPEAKER_03]: to generate a one-day kit proof, and that's not acceptable, since the UNA block types several seconds or more than a bit like 10 seconds.
07:09.063 --> 07:16.866
[SPEAKER_03]: But yeah, of course, like we want to shrink, we want to reduce the proof generation time for the kit proof as much as possible as a week.
07:17.266 --> 07:24.250
[SPEAKER_03]: Have some nice neck GPU version of the proof generation, I mean, we put it on just the two
07:25.290 --> 07:26.031
[SPEAKER_03]: GP motion.
07:26.051 --> 07:27.213
[SPEAKER_03]: So for here it is next.
07:27.834 --> 07:30.798
[SPEAKER_03]: The GP car we use is 14.9 GP cars.
07:31.298 --> 07:37.327
[SPEAKER_03]: The way it is successful I would use the poor generation car from more than 2 hours to around 15 minutes.
07:38.844 --> 07:55.710
[SPEAKER_03]:
and then we shoot it to our customers and who is very happy and waiting to pay for the server so we provide to them, feels like we are not only selling the machine, we are not not selling the software, we are selling the servers like we.
07:56.290 --> 08:10.020
[SPEAKER_03]: with a like saying like some demanding in this factor we build a blockchain to incentivize people to join the blockchain to contribute their idle GPU power into sites in our.
08:10.461 --> 08:12.622
[SPEAKER_03]: The sites in our case announced a blockchain.
08:13.263 --> 08:24.711
[SPEAKER_03]: To contribute their like the computing part of sites in our work to then we can deploy our GPU software and the hardware to generate the developers to another
08:27.570 --> 08:43.660
[SPEAKER_02]: Tell me about a decision or trade-off yet to make in that, and I can hear some in what you're describing, but maybe a key decision and how you approached the initial problem, or maybe there was acceptance of how you built the product or maybe architectural debt or things like that, or even limitation.
08:43.721 --> 08:47.523
[SPEAKER_02]: Tell me about some of those things that you had to make the hard decisions around, and how you cope with them.
08:49.857 --> 08:56.099
[SPEAKER_03]: the original go of settings to designs and special nice chips for the VK puff generation.
08:56.800 --> 08:59.521
[SPEAKER_03]: But as the wind like move the another way.
09:00.381 --> 09:04.903
[SPEAKER_03]: Yeah, we just found out like the GPUs were even FPG's.
09:05.543 --> 09:10.145
[SPEAKER_03]: Those hardware is like after share of hardware, they are good enough.
09:10.725 --> 09:15.387
[SPEAKER_03]: They are good enough to carry out the current moving demand.
09:16.047 --> 09:34.411
[SPEAKER_03]: So, which means we don't actually, we don't need to spend several, several media building, like to do the chip tip out, then improve the efficiency of our own chip, we can just rely on them, of the shelves, hardware to 35 the demand of our customer.
09:35.211 --> 09:41.752
[SPEAKER_03]: Yeah, and but we, in the past, the problem, more than, I mean, more than a year, we have, like, already
09:42.612 --> 09:50.256
[SPEAKER_03]: Spend a note of like a manpower and also kick up toe in the engineering efforts of neck building the chip.
09:51.036 --> 09:57.459
[SPEAKER_03]: And also making the meantime like also talk to some potential customers who probably will buy the chip CR.
09:58.299 --> 10:08.910
[SPEAKER_03]: Then that's very, since the market is not very clear, and the algorithms, like for the VK proofs, they are not converging, they are not fake yet.
10:09.370 --> 10:15.176
[SPEAKER_03]: So those, like, potential buyers, they are reenactant to pay anything for the chip.
10:15.816 --> 10:21.882
[SPEAKER_03]: So that's, like, the problem, like, these two reasons, the market is not big enough, and also the...
10:22.843 --> 10:30.526
[SPEAKER_03]: the community haven't reached consensus about which they can persist and they are going to use.
10:30.606 --> 10:37.249
[SPEAKER_03]: So that's why when we pass the more engineering effort and build in the chip.
10:37.750 --> 10:40.531
[SPEAKER_03]: Yeah, it's a very hard decision like we need to.
10:41.171 --> 10:47.574
[SPEAKER_03]: There's some team members to go and we also need to shift some of our team members to do some like other things.
10:48.194 --> 10:59.019
[SPEAKER_03]: And it's somehow a little bit also deviates from our original vision about how the sci-fi will be in the next few years.
11:05.385 --> 11:15.456
[SPEAKER_02]: I'm curious about how you're going to progress in mature size 2, where you're going with it, and I think that prepping a box with it, I'm looking for is, how did you build your roadmap?
11:15.656 --> 11:17.078
[SPEAKER_02]: How do you go about deciding that?
11:17.138 --> 11:21.663
[SPEAKER_02]: Okay, this is the next most important thing to build or to address with size 3.
11:23.630 --> 11:29.014
[SPEAKER_03]: We probably close the monitor the market to see what are the trends.
11:29.774 --> 11:37.480
[SPEAKER_03]: Yeah, as you can see with builds, like the setting network to support the demand of or not of near-tooth.
11:38.301 --> 11:42.083
[SPEAKER_03]: But the near-tooth problem is starting on and next this year.
11:42.724 --> 11:47.047
[SPEAKER_03]: The main tools they don't have too much connection for us to do the poor generation.
11:48.594 --> 12:01.924
[SPEAKER_03]: So which means we, that, like, in addition to the link-in-puff generation, we also need to expand our support to do some other competition work loads such as Celeste Wally.
12:02.864 --> 12:09.849
[SPEAKER_03]: Probably it's not a pivot, but we expand our support to also cover the demand in the AI
12:10.970 --> 12:11.891
[SPEAKER_03]: computing as well.
12:12.351 --> 12:19.678
[SPEAKER_03]: We, that unless supported in mind, we also have our own harness engineering ducts, which is quite good.
12:19.879 --> 12:35.193
[SPEAKER_03]: Yes, we use a harness engineering product to write another code and another code right now, the performance is better than what human coders can write and take a witness time to write all this code.
12:36.174 --> 12:55.905
[SPEAKER_03]: Yes, like we just need to monitor the markets and say who is who right now can bring us some real computing demands that within how we can support them, how we can convert them from a potential paying customer to a real paying customer.
12:56.425 --> 12:59.147
[SPEAKER_00]: Yeah, so that's the crux of like how we
13:02.638 --> 13:09.745
[SPEAKER_02]: So I hear you saying we a lot tell me about how you built your team and what you look for in those people to indicate that they're the winning horses to join you.
13:11.486 --> 13:19.314
[SPEAKER_03]: First to badge of like team members joining South Asia and like our friends or friend of our friends who got referred by the common team members.
13:20.134 --> 13:21.516
[SPEAKER_03]: I guess it's
like who wait.
13:21.856 --> 13:26.981
[SPEAKER_03]: I will say like for all the team members they are all better than being like an authentic purpose.
13:27.501 --> 13:52.607
[SPEAKER_03]: the kinsang aspect like we like for each neck product we put into practice or deployed like oh it all starts with like several problems around three or four people yeah we cut we basically divide the groups we divide the team members into groups each group is like working on some exciting problems they try to
13:57.428 --> 14:09.774
[SPEAKER_03]: I also talked to another potential customer to see their demand in how we can adapt to come up with a new product which can satisfy the the demand of the potential customers.
14:10.534 --> 14:16.977
[SPEAKER_03]: Yes, so in that way, like our teens school, like Niger and Niger, so right now we have only been like one and a third
14:21.959 --> 14:25.020
[SPEAKER_03]: working on some like exciting projects.
14:25.460 --> 14:42.065
[SPEAKER_03]: And for almost every day problem, except for Wednesday we have 30 minutes group meeting which like everyone will present some progress of what they are working on and then let them fall down like feedback from like other team members like the
14:42.705 --> 15:00.009
[SPEAKER_03]: If the feedback is not like doing the good meeting, they've first immediately to share the progress they have made and the real essence of the product, and the people will play with the product, and then give them real feedback.
15:00.749 --> 15:05.670
[SPEAKER_03]: So how that's how we are improving our product and also how we
15:06.490 --> 15:12.355
[SPEAKER_03]: How the team members right now are working on this product, they can re-bought to the feedbacks, yeah.
15:12.996 --> 15:24.205
[SPEAKER_03]: I believe these interactions, these internal interactions will be very good for improving the product to find out new things to do.
15:29.012 --> 15:37.544
[SPEAKER_02]: Let's flip into scale ability, and this will be interesting, especially given you approaching this with crypto networks and hardware and all the things to be a full stack, compute network.
15:37.965 --> 15:45.215
[SPEAKER_02]: How did you think about scale in the beginning, and even at this stage, have there been interesting areas we've had to fight scale as you've grown?
15:47.790 --> 15:54.616
[SPEAKER_03]: Skillability is always an issue, like for some product we develop public is hard to scale.
15:55.637 --> 16:06.986
[SPEAKER_03]: Yeah, so in that way we need to find that in that scenarios we need to find new ways to adapt this product to have like more demand, like for instance,
16:07.807 --> 16:20.457
[SPEAKER_03]: Earlier this year, we opened source of the KVM, so the KVM stands for the Energy Virtual Machine, which means like you don't need to write the K-circuit by hand to prevent that people need to.
16:20.978 --> 16:27.463
[SPEAKER_03]: Notice on that new language and then to use a new language to write the K-circuit.
16:27.863 --> 16:32.507
[SPEAKER_03]: But with the KVM, you don't need to do that, you just write your normal.
16:32.907 --> 16:40.750
[SPEAKER_03]: Python, raster program, and then it will be converted to the upcode, which will be runny, and it's like virtual machine.
16:41.310 --> 16:50.714
[SPEAKER_03]: Yeah, so we open source the ZKVM, and it's run as still the one of the best performance ZKVM in the space.
16:51.274 --> 16:57.900
[SPEAKER_03]: But as I just mentioned, like the near-toes, they are demanded declining.
16:58.321 --> 17:02.344
[SPEAKER_03]: So we need to find new ways to use the VAM.
17:03.265 --> 17:12.093
[SPEAKER_03]: Like for instance, if we cannot find an external VAM, we can come up with a new product, which will use this VAM.
17:12.334 --> 17:16.718
[SPEAKER_03]: So for instance, in this scenario, with the VAM is like backpool.
17:17.278 --> 17:25.805
[SPEAKER_03]: So that cool allows people to make transactions without seeing anything, without seeing any private information online.
17:25.825 --> 17:34.672
[SPEAKER_03]: So, on change, we can understand the hash commitment, the liquid proof which hides the details of this transaction and the testing.
17:35.112 --> 17:43.819
[SPEAKER_03]: So, this like that cool will be using this like the KVM or not, and also can create some demand for the computing resources.
17:44.159 --> 17:45.681
[SPEAKER_03]: So that's how we can scale up.
17:46.341 --> 17:50.007
[SPEAKER_03]: how we can scale up the demand for the current product.
17:52.471 --> 17:58.601
[SPEAKER_02]: So as you step out on the balcony, and you look across all that you've built with psysic, what you most proud of.
18:00.398 --> 18:20.227
[SPEAKER_03]: We have the best performance GPU acceleration for the K back then, and then we use this GPU with and after talking to some customers, we find out that they have the demand to use a server instead of just the software that GPU software will build like Siphon Hour.
18:20.747 --> 18:26.390
[SPEAKER_03]: To Siphon Network, we can coordinate, we can set up, we can incentivize, we can reward,
18:27.030 --> 18:39.261
[SPEAKER_03]: The participant of SISIC, so basically SISIC network can connect, connect the people together, and this SISIC network can also be expanding to support AI competition as well.
18:39.782 --> 18:44.526
[SPEAKER_03]: So it's a very versatile product that can be used in your not-stop scenarios.
18:45.427 --> 18:47.988
[SPEAKER_03]: And yeah, so that's one thing, and that's what they keep in.
18:48.369 --> 19:00.775
[SPEAKER_03]: To the big event, with the big event ran out of skill and open source, we basically push, we release a new version every two or three weeks at most, but normalize around two weeks.
19:01.515 --> 19:22.929
[SPEAKER_03]: The Wikipedia right now is still the best performance in the space, and the Wikipedia can be used by a lot of scenarios not only in the blockchain space, but also you can use the Wikipedia in the AI inference as
well, since you are using your using same GPT 6, but like the GPT openly i probably will, they will just use GPT 5.6 to
19:25.270 --> 19:31.813
[SPEAKER_03]: To search for you, then the DK can be used to certify the result to say these results actually come in from.
19:32.373 --> 19:34.795
[SPEAKER_03]: GPT 6, instead of GPT 5.6.
19:35.155 --> 19:47.701
[SPEAKER_03]: So, yeah, so it's just that they can be in what beyond a very potential product for AI inference to certify to make people trust that they are using the model, there is no.
19:48.521 --> 19:52.144
[SPEAKER_03]: No quality model you are using, but you are paying for the high quality model.
19:52.785 --> 19:58.369
[SPEAKER_03]: In that sense, you need some real specialness, however, you really need 86 for that.
19:58.469 --> 20:03.173
[SPEAKER_03]: The current GPU provides speed to know for people to turn on rates.
20:05.695 --> 20:07.157
[SPEAKER_02]: Let's flip the script a little bit, Leo.
20:07.317 --> 20:11.100
[SPEAKER_02]: Tell me about a mistake you made and how you and your team responded to it.
20:13.258 --> 20:36.146
[SPEAKER_03]: We previously, like back public enough earlier of Mexico, we invest a little bit like too much resource like on the capital-wise, in building our own FPGA server, like the FPGA server cost us around 200,000 to 300,000 US dollars to build the FPGA.
20:37.008 --> 20:47.136
[SPEAKER_03]: Yeah, we just don't, at that time we think, probably there will be just one or two customers who will likely use the key game to prove their blocks.
20:48.097 --> 20:52.961
[SPEAKER_03]: But she turned out like there are not a customer who want to do that thing.
20:53.261 --> 20:59.866
[SPEAKER_03]: And the FPG server really cannot support too many power now competition then.
21:00.546 --> 21:02.828
[SPEAKER_03]: And also, it's not how surprising I see it.
21:03.949 --> 21:17.719
[SPEAKER_03]: the GPU acceleration for the K also both very fast in the past several years and which somehow outperformed the FPGA in terms of like performance.
21:18.600 --> 21:27.446
[SPEAKER_03]: Yeah, so that's one thing and then after we reunite the same with stopping the team, our resources into the FPGA, but still like between
21:28.447 --> 21:32.669
[SPEAKER_03]: Experimental theme that count on the FPGA sides, but we are not investing.
21:33.169 --> 21:38.911
[SPEAKER_03]: Our resource is the image that can do FPGA servers like two or four customers.
21:42.733 --> 21:43.633
[SPEAKER_02]: Leo, this will be fun.
21:43.653 --> 21:45.014
[SPEAKER_02]: This is exciting.
21:45.074 --> 21:47.615
[SPEAKER_02]: What you're tackling is a big project.
21:48.115 --> 21:48.755
[SPEAKER_02]: A big endeavor.
21:49.015 --> 21:53.937
[SPEAKER_02]: Tell me what the future looks like for CySik, for what you're building, for where the industry is going, for all the things.
21:55.499 --> 21:59.043
[SPEAKER_03]: the essence of size A keys can purify vision.
21:59.523 --> 22:06.650
[SPEAKER_03]: Computer-file means like people who can contribute their idol computer resources into size and effort.
22:06.950 --> 22:16.860
[SPEAKER_03]: Whether you want to contribute your servers, your laptop, or even your cell phone, you can always run some like software from size A to contribute to the community.
22:17.440 --> 22:40.702
[SPEAKER_03]: And I will say due to the AI competition coming to like the demand or not, we can actually use a network to coordinate all these different hardware devices to realize to have some like real yields for the customers who have some, to our community members who have some idle computing power.
22:41.302 --> 23:01.215
[SPEAKER_03]: So in that sense, I would say the decentralized computing will be like more reliable than centralized building since like in the past several days, like we experience a lot of disruption in the data centers, like for a lot of decentralized players.
23:02.036 --> 23:05.098
[SPEAKER_03]: But decentralized computation consult this issue.
23:06.085 --> 23:07.526
[SPEAKER_02]: OK, Leo, let's switch to you.
23:07.626 --> 23:09.888
[SPEAKER_02]: Who influences the way that you work?
23:09.928 --> 23:12.670
[SPEAKER_02]: A person or many persons are something you look up to and why?
23:14.051 --> 23:18.574
[SPEAKER_03]: People who influenced me on several, on like, why?
23:18.714 --> 23:30.843
[SPEAKER_03]: Like, that's most of the influence, like, happy in my graduate study, either in Chinese Academy of Science or, like, I want at Cornell and, like,
23:31.643 --> 23:41.146
[SPEAKER_03]: Like the most impact I receive on this tool, institutions, people are really working very hard.
23:41.827 --> 23:44.828
[SPEAKER_03]: And they are very resilient to theories.
23:45.568 --> 23:53.211
[SPEAKER_03]: Yes, it's a work, whether you are actually computing, competing with a lot of very smart people.
23:53.851 --> 23:58.894
[SPEAKER_03]: So, theory is like a very common thing like two to me.
23:59.434 --> 24:12.001
[SPEAKER_03]: And you probably have like more than 10 attempts, probably I would be like surprised or like they're happy to see like even probably one or two of the attempts were worth and all the other were just a few.
24:12.341 --> 24:16.324
[SPEAKER_03]: And I'm like totally fine with that things like he might.
24:16.864 --> 24:22.487
[SPEAKER_03]: Probably like previous academia works like for each like paper I wrote,
24:23.117 --> 24:28.421
[SPEAKER_03]: I also try a lot of different ways to attack the problem, but most of the attacks, of course.
24:29.021 --> 24:29.521
[SPEAKER_03]: Don't work?
24:30.242 --> 24:36.186
[SPEAKER_03]: But I'm fine with that, I always say, like, I can come up with some more clever ideas of what I like to.
24:36.586 --> 24:41.029
[SPEAKER_03]: How we can circle around the problem to find another solution.
24:41.290 --> 24:41.510
[SPEAKER_03]: Yeah.
24:42.170 --> 24:53.240
[SPEAKER_03]: So that's that would say my classmates or like my advisor if in my graduate study, I'm very important to me, they influenced me on that.
24:54.381 --> 24:55.602
[SPEAKER_02]: Okay, Leo, last question.
24:55.762 --> 25:00.386
[SPEAKER_02]: So you're getting on a plane, and sitting next to a young entrepreneur who's built the next big thing.
25:00.887 --> 25:01.567
[SPEAKER_02]: They're jazzed about it.
25:01.587 --> 25:04.290
[SPEAKER_02]: They can't be showed off to the world, and can't be showed off to you right there on a plane.
25:04.870 --> 25:06.251
[SPEAKER_02]: What advice do you give that person?
25:06.331 --> 25:08.053
[SPEAKER_02]: Having gone down this road a bit now?
25:10.022 --> 25:18.006
[SPEAKER_03]: I will toast the entrepreneur to say, don't expect too much from your product of, from your first product.
25:18.146 --> 25:20.107
[SPEAKER_03]: You need to iterate it a lot.
25:20.968 --> 25:34.255
[SPEAKER_03]: Yeah, I think right now, with a help from AI, people like all the products they iterate very fast and we need to keep up with a community, keep up with a market to iterate it.
25:34.955 --> 25:40.741
[SPEAKER_03]: you cannot basically expect too much success from your first product.
25:42.002 --> 25:52.852
[SPEAKER_03]: And also, and also, probably the second thing is like, technology is good, but technology doesn't contribute 100% to the success of the product.
25:53.473 --> 25:57.957
[SPEAKER_03]: Your product actually depends on not-of-factors and success, probably the
25:58.615 --> 26:04.340
[SPEAKER_03]: It's an important factor, but it doesn't contribute all to the success of a product.
26:04.380 --> 26:17.232
[SPEAKER_03]: You need to develop some marketing strategy, be the strategy, and how you can't acquire customers, how people are willing to pay for all products.
26:17.432 --> 26:22.837
[SPEAKER_03]: So that's more important than developing the product.
26:23.343 --> 26:29.192
[SPEAKER_02]: That's great advice, Leo, thank you for being on the show today and thank you for telling the creation story of Sysik.
26:29.632 --> 26:31.795
[SPEAKER_03]: Thanks for nots, nice chatting with you, Noah.
26:33.919 --> 26:36.262
[SPEAKER_02]: And this concludes another chapter of Coat Story.
26:44.482 --> 26:47.225
[SPEAKER_02]: code story is hosted and produced by Noah Labhart.
26:47.685 --> 26:52.130
[SPEAKER_02]: Be sure to subscribe on Apple Podcasts, Spotify or the podcasting app at your choice.
26:53.091 --> 26:55.033
[SPEAKER_02]: And when you get a chance, leave us a review.
26:55.534 --> 26:57.576
[SPEAKER_02]: Both things help us out tremendously.
27:00.499 --> 27:01.600
[SPEAKER_02]: And thanks again for listening.