WEBVTT 00:00.000 --> 00:12.480 All right, everyone, so let me introduce our next speaker, my fellow Devroom, co-organized 00:12.480 --> 00:20.580 and actually, a company's co-founder Tatiana Dada Shiva, who will be talking about some of 00:20.580 --> 00:26.500 the interesting projects between hardware, software, and AI, so take it away, thank you. 00:26.740 --> 00:34.780 So this is actually an AI application talk, which will not technically allow them this 00:34.780 --> 00:41.100 Devroom, so since it's applied to AI Plum, and I guess it works, so if anybody wants 00:41.100 --> 00:45.100 to do, then use the same LiveHard next time, you welcome. 00:45.100 --> 00:49.780 So I haven't wanted to talk about load in the better fountains in different kind of hardware 00:49.780 --> 00:55.860 development, and if you ask, how well, actually, I'd say as low as it gets, because I'm 00:55.860 --> 01:02.420 not even an engineer, so I'm even worse, I'm CEO of hardware company, and if anybody 01:02.420 --> 01:08.580 asks me, can I have a design hardware, now that it doesn't know, so how did I do that? 01:08.580 --> 01:13.620 Well, in this particular case, and for the purpose of this discussion, I'll talk about how 01:13.620 --> 01:19.580 to use AI to be helpful to your company when you know nothing, and what I do know, I do 01:19.580 --> 01:24.780 know how to manage people, I do know how to kind of know when somebody's bullshit in 01:24.780 --> 01:31.020 the company, and I wanted to use it all in the AI, and I absolutely am not here to produce 01:31.020 --> 01:36.260 the best code ever, or be the smartest person in the room, I'm usually just for the result. 01:36.260 --> 01:37.260 So what does it mean? 01:37.260 --> 01:43.220 It means that I use code code, and absolutely shoots which double-nercarnities, but again, 01:43.220 --> 01:48.260 for me, the model doesn't matter, usually don't even pay attention, which one clue chooses, 01:48.260 --> 01:53.900 I'm not writing code myself, so it's not about being a copilot, and again, safety 01:53.900 --> 02:01.180 matters, so especially if you're not in professional engineer, don't allow cloth mess up 02:01.180 --> 02:05.660 your stuff, and it did start it to kind of motivate people in the company to use more 02:05.660 --> 02:14.380 AI, but then, again, I figure out that there are so many ways that how people use AI, 02:14.380 --> 02:20.260 so here are some questions that I suggest people to ask themselves, so I do use it in just 02:20.260 --> 02:25.300 one instance of AI, and since we are, like as we discussed today, in the edge of open 02:25.300 --> 02:30.900 core, I guess you should think twice if you use it on the one. 02:30.900 --> 02:35.180 Do give the AI tasks like a bigger than junior developer can handle? 02:35.180 --> 02:41.180 I know people who ask AI to just create a core and validate it, and do the whole design, 02:41.180 --> 02:44.900 I don't believe in that, you should absolutely not do that. 02:45.460 --> 02:51.060 Again, personal opinion, but pretty strongly hold, and I suggest, like, you think about 02:51.060 --> 02:58.180 these questions, not going to focus on each one of them, but it's always good for lots of things, 02:58.180 --> 03:03.780 but not for everything, so what do they do in my company? 03:03.780 --> 03:12.020 So I think one of the good first examples is we got this novel, I accelerated a card, and then I said 03:12.020 --> 03:16.900 in all, I mean, there was no documentation, and I didn't want to have the source code. 03:16.900 --> 03:23.060 I mentioned years in the company, we are trying to figure out what is there, how to use it, 03:23.060 --> 03:28.580 that is a win-work, and they have been trying to understand it all for a few weeks, and then 03:28.580 --> 03:34.980 another insure of it works, and we've got code in about three hours and made it work, and again, 03:34.980 --> 03:41.940 some ideas of how to use it, is asked to run just about every model you can, and you 03:41.940 --> 03:47.220 can make conclusions as, like, what work, what dawn, what is the difference? 03:47.220 --> 03:52.500 You can bring us that of human being, like, they would think about the structures, and this, 03:52.500 --> 03:59.460 and that, and again, you can slow a lot of things and ask it to compare, to experiment. 04:00.340 --> 04:04.980 It's basically we call it software at a college now, so when you have something you don't understand, 04:04.980 --> 04:10.340 but you want to make it work. So that's one example, some important D files. 04:11.300 --> 04:15.380 Another one, so we're doing a lot of open source efforts, and since again, 04:15.380 --> 04:22.420 all the engineers in the company actually doing useful stuff, and I want an open source code to be nice, 04:22.420 --> 04:28.340 and people be able to use it. So one of the ideas was, let's make it applicable. 04:29.300 --> 04:35.220 So how do we do that? I got the cheapest of PGA as I could, so this, for example, was 04:35.220 --> 04:41.700 a sprinkler, it cost, like, 80 bucks. I got a few others. So my knowledge of PGA actually 04:41.700 --> 04:48.020 is very limited. It's limited to one hour talk. I've heard that the RISC file sent it, 04:48.740 --> 04:55.460 and I've been able to port a couple of cores that are open already, and well documented, 04:55.460 --> 05:02.260 and again, by comparing and contrasting, asking the I to basically figure out how to do it 05:02.260 --> 05:08.420 for the next one that I happen to have. So that's another application. By the way, 05:08.420 --> 05:13.540 I'm not the only one doing all of this. So this is our friend who basically 05:14.900 --> 05:22.100 tweeted recently about exactly the same. So while some people are afraid to use the I, 05:22.100 --> 05:28.980 others are asking them to figure out the path and put easy complicated tasks. So why and how does it work? 05:29.540 --> 05:38.260 Actually, I'll quickly jump to this one. It's basically asking to find the solution, 05:39.060 --> 05:45.940 experimenting a lot, comparing things, and treating everything as a system. So there are lots of 05:45.940 --> 05:51.380 tools that appear actually, I didn't find any open source ones. But there are lots of tools 05:51.380 --> 05:56.740 that allow you to kind of throw documentation with the white papers, whatever you have the 05:56.740 --> 06:04.820 data sheets at the AI system like to and program the system. So if your system is open and 06:04.820 --> 06:10.420 it's a system on the chip, you can do it a similar thing. So again, if you know any open ones, 06:10.420 --> 06:17.540 that's another really interesting way to work with it all. But again, I'm not touching platform 06:17.540 --> 06:22.580 blocks that would be other people talking about it. But if you have enough platform blocks, 06:22.660 --> 06:29.220 yeah, it's a really good way to kind of free combine them, experiment with them, and basically 06:29.220 --> 06:42.580 allow us people who have never done hardware developments that are doing that. Thank you.