WEBVTT 1 00:00:04.679 --> 00:00:08.400 Hey, welcome back to another episode of the Ruby Rogues podcast. 2 00:00:08.720 --> 00:00:11.279 This week, on our panel, we have a Yushwatya. 3 00:00:11.759 --> 00:00:12.480 Hello. Hello. 4 00:00:13.160 --> 00:00:15.720 I'm Charles Maxwood from Top End Devs. Man, it feels 5 00:00:15.759 --> 00:00:17.399 like it's been a while since we've recorded one of 6 00:00:17.440 --> 00:00:17.839 these dozen. 7 00:00:18.960 --> 00:00:23.519 Yeah, it's been a few months. Yeah, at times, just 8 00:00:23.640 --> 00:00:27.879 been flying for me. So it's all gone back quite quickly. 9 00:00:27.920 --> 00:00:28.960 But it's nice to be back. 10 00:00:29.800 --> 00:00:33.280 Yeah, definitely. For those of you who are listening and going, 11 00:00:33.320 --> 00:00:35.920 didn't you release one like last week or the week before, Well, 12 00:00:35.920 --> 00:00:37.439 there were a few things that happened. I'm just going 13 00:00:37.520 --> 00:00:39.640 to fill you all in. I don't know if you 14 00:00:39.679 --> 00:00:41.799 need all the insight baseball, but it's interesting, and then 15 00:00:41.799 --> 00:00:45.799 I'll introduce our guests. I wound up getting a job 16 00:00:45.799 --> 00:00:49.560 at Price Picks at the end of March. I also 17 00:00:49.759 --> 00:00:52.240 hired my daughter to be putting the episodes out and 18 00:00:52.399 --> 00:00:54.920 she didn't and so I fired her. I had to 19 00:00:54.920 --> 00:01:00.000 fire my own kid, and so Jib who's our editor, 20 00:01:00.320 --> 00:01:04.439 took over posting the shows, and so he went and 21 00:01:04.519 --> 00:01:06.599 found all the ones that hadn't been posted and started 22 00:01:06.599 --> 00:01:09.040 posting him again. So the gap that you all, as 23 00:01:09.120 --> 00:01:13.040 listeners saw was probably back in like April. Right, there 24 00:01:13.359 --> 00:01:15.480 was like a month in March or April that you 25 00:01:15.519 --> 00:01:19.480 didn't see episodes. So you're getting episodes that we recorded 26 00:01:19.519 --> 00:01:24.200 a month or two or three ago, and now we're 27 00:01:24.239 --> 00:01:28.000 kind of back at it and recording episodes again. So anyway, 28 00:01:28.040 --> 00:01:31.239 your gap is different from ours. So but it feels 29 00:01:31.239 --> 00:01:32.920 so good to just get back and talk about the 30 00:01:32.959 --> 00:01:36.319 stuff we love. And we've got two terrific guys who 31 00:01:36.359 --> 00:01:38.760 were here who are working on a very interesting project. 32 00:01:39.439 --> 00:01:46.200 We have Adrianne Poli and Mark and Marco Roth. 33 00:01:47.359 --> 00:01:49.239 Hey, thanks for having us. 34 00:01:50.200 --> 00:01:54.560 Yeah, absolutely, and yeah, I think I'm the only one 35 00:01:54.599 --> 00:01:57.680 of you guys that's not in Europe, so thanks for 36 00:01:57.719 --> 00:02:00.000 coming in the evening or afternoon whenever it is there. 37 00:02:00.840 --> 00:02:04.519 Uh yeah, So I reached out because I ran across 38 00:02:04.560 --> 00:02:08.800 a really interesting project. It's it's Ruby video or Ruby 39 00:02:08.879 --> 00:02:12.599 videos dot dev, which one is it. 40 00:02:12.599 --> 00:02:17.599 It started as a Ruby video and uh, like two 41 00:02:17.639 --> 00:02:23.199 months ago we decided to rebrand it for a bigger 42 00:02:23.240 --> 00:02:29.599 picture on the under the Ruby events dot org. The 43 00:02:29.680 --> 00:02:34.039 project has more ambitions, but we can dive a bit 44 00:02:34.080 --> 00:02:38.360 more into the details and that's later on. 45 00:02:39.240 --> 00:02:42.879 Yeah, makes sense. So when you started, I'm kind of 46 00:02:42.919 --> 00:02:49.439 curious what what was the vision I was? 47 00:02:50.159 --> 00:02:55.479 It was several things occurred at the same time. First, 48 00:02:55.520 --> 00:02:59.400 I visited a similar project in the Python world that 49 00:02:59.599 --> 00:03:03.560 is called the t Video or something like this, which 50 00:03:03.599 --> 00:03:09.919 is a website that indexes something like fifteen thousand Ruby 51 00:03:10.919 --> 00:03:14.840 Python videos of conference and so on. And I was 52 00:03:14.879 --> 00:03:19.280 looking at something similar in the Ruby industry and I 53 00:03:19.360 --> 00:03:22.560 couldn't find anything. Of course, you can always go to 54 00:03:23.560 --> 00:03:28.000 YouTube or Google search and search for whatever things you need, 55 00:03:28.000 --> 00:03:31.479 but I couldn't find a single place where you could 56 00:03:31.520 --> 00:03:38.000 search for a specific topics and get all the conference 57 00:03:38.360 --> 00:03:44.080 on that particular topic in the Ruby industry. So at 58 00:03:44.080 --> 00:03:49.360 that time, I also I was interested to test several 59 00:03:49.439 --> 00:03:53.759 things that were coming out that there was come out. 60 00:03:54.479 --> 00:03:58.919 There was this Esclie trends, and I wanted to build something. 61 00:03:58.919 --> 00:04:04.360 So I started to build a small website that started 62 00:04:04.439 --> 00:04:09.800 with I think eight hundred videos, mostly rails cones, Ruby 63 00:04:09.879 --> 00:04:13.560 coones and so on. That was the proof of concept, 64 00:04:13.560 --> 00:04:17.240 the first proof of concept so largely inspired by a 65 00:04:17.240 --> 00:04:22.680 Byton video, and it had a bit of traction at 66 00:04:22.680 --> 00:04:28.639 the beginning. When it was announced. Of course, it was 67 00:04:29.360 --> 00:04:35.639 open source, and very quickly Marco joined the venture and 68 00:04:35.800 --> 00:04:46.600 came Marco was also maintaining Ruby Conference. If you want 69 00:04:46.639 --> 00:04:48.600 to add more details on this, maybe Marco. 70 00:04:49.680 --> 00:04:52.759 Yeah, so I was maintaining Ruby Conferences dot org, which 71 00:04:52.879 --> 00:04:55.279 used to be this simple website where you can add 72 00:04:55.519 --> 00:04:58.079 o where you can see all the confidences are happening 73 00:04:58.079 --> 00:04:58.839 in the Ruby world. 74 00:04:59.240 --> 00:05:02.399 I use all the time. By the way, it's like 75 00:05:02.800 --> 00:05:05.199 what's coming up and where can I submit calls for 76 00:05:05.240 --> 00:05:07.079 proposals and stuff? So yeah, thanks for that. 77 00:05:08.079 --> 00:05:11.079 Yeah, that's that's been like going for a long time. 78 00:05:11.240 --> 00:05:14.120 It's I have been just trying to bring in the 79 00:05:14.240 --> 00:05:16.480 up to date and kind of kept adding these new 80 00:05:16.480 --> 00:05:20.319 events that I saw coming on. But then I realized 81 00:05:20.360 --> 00:05:23.360 that they also had like video links to YouTube playlists 82 00:05:23.360 --> 00:05:27.680 and all these other like topics they had on the website. 83 00:05:28.199 --> 00:05:30.319 And then we decided to add meetups, and then we 84 00:05:30.319 --> 00:05:33.240 were like, yeah, let's maybe redesign this webpage because it 85 00:05:33.240 --> 00:05:36.199 does look dated in a way, so you wanted to 86 00:05:36.279 --> 00:05:40.519 kind of add more features to it. But it kept 87 00:05:40.600 --> 00:05:44.160 kind of like his ideas kept growing and they couldn't 88 00:05:44.240 --> 00:05:46.399 really find a good way to make it happen on 89 00:05:46.439 --> 00:05:50.519 this checker website. And at the same time, then Ruby 90 00:05:50.600 --> 00:05:53.439 video came around and it was like, Oh, actually, this 91 00:05:53.600 --> 00:05:56.079 is very much like what I kind of hadn't visioned 92 00:05:56.120 --> 00:05:59.079 for Ruby Conviences to be. That's why I decided to 93 00:05:59.120 --> 00:06:01.519 kind of join forces with oddly On to kind of 94 00:06:01.720 --> 00:06:05.759 make this one website or kind of contribute to Ruby 95 00:06:05.839 --> 00:06:08.680 Video to make this the thing that I wanted Ruby 96 00:06:08.759 --> 00:06:11.720 Confidence to be. And that's kind of what ties into 97 00:06:11.800 --> 00:06:14.199 this rebranded bed a few months ago, where you want 98 00:06:14.240 --> 00:06:18.160 to bring these two websites together as one. This is 99 00:06:18.160 --> 00:06:20.759 going to be Ruby events dot org and that's in 100 00:06:20.759 --> 00:06:23.439 the future where you will find all the upcoming events, 101 00:06:23.519 --> 00:06:27.040 previous events, and even if you're at the event at 102 00:06:27.040 --> 00:06:29.399 the moment, you can see the schedule and all of that. 103 00:06:29.600 --> 00:06:32.079 So it's kind of just a deep place to go 104 00:06:32.199 --> 00:06:35.480 for anything Ruby events related. 105 00:06:36.279 --> 00:06:39.839 Nice. I usually you have questions because I've got a 106 00:06:39.879 --> 00:06:41.040 ton and I don't want to. 107 00:06:41.480 --> 00:06:43.639 I have a ton of why didn't you continue, I'll 108 00:06:43.720 --> 00:06:44.439 jump in as. 109 00:06:44.319 --> 00:06:48.199 And when okay, sounds good. So I'm kind of curious. 110 00:06:48.199 --> 00:06:51.160 So you decide you want this website, and I think 111 00:06:51.199 --> 00:06:53.639 the closest thing we've had in the past was Confree's 112 00:06:53.720 --> 00:06:57.600 used to host all the videos from all the conferences 113 00:06:57.600 --> 00:06:59.839 that they recorded. But I went and looked, and I 114 00:07:00.079 --> 00:07:03.839 and find them anymore. And I don't know, I don't 115 00:07:03.839 --> 00:07:05.439 know what the story is there, if I'm just not 116 00:07:05.519 --> 00:07:09.120 doing the right Google search or whatever. But anyway, so 117 00:07:10.560 --> 00:07:14.639 you start putting the site together and I mean, how 118 00:07:14.639 --> 00:07:18.519 are you finding the videos? We're just embedding them from YouTube? 119 00:07:18.560 --> 00:07:20.720 And were there any challenges that you're into kind of 120 00:07:20.720 --> 00:07:21.480 pulling this together? 121 00:07:23.600 --> 00:07:28.000 Yeah? For now, we don't host any videos, so we 122 00:07:28.240 --> 00:07:32.720 just index them. So we mostly find them on YouTube 123 00:07:32.720 --> 00:07:38.319 because that's where mostly events are hosting their videos. A 124 00:07:38.360 --> 00:07:43.360 few do host them by themselves, like Brighton. I think 125 00:07:43.399 --> 00:07:51.000 Brighton is an example for something quite recent, but mostly 126 00:07:51.000 --> 00:07:57.959 it's YouTube videos, so we do get the meta data 127 00:07:58.000 --> 00:08:06.240 from YouTube. There is there has been a very big 128 00:08:06.360 --> 00:08:10.680 work and Marco contributed a lot on this to build 129 00:08:11.879 --> 00:08:14.759 all of those yanal file that will describe all the 130 00:08:15.120 --> 00:08:17.959 meta data for all the talks, all the events with 131 00:08:18.120 --> 00:08:21.720 both their links and so on, with the correct speakers, 132 00:08:22.240 --> 00:08:26.519 the correct description. Lots of cleaning of the meta data 133 00:08:26.759 --> 00:08:27.360 has been done. 134 00:08:28.720 --> 00:08:30.800 So do you import it and then clean it up 135 00:08:30.800 --> 00:08:34.440 by hand or do you go find the videos that 136 00:08:34.440 --> 00:08:37.799 you want and then just capture all that information somehow? 137 00:08:37.960 --> 00:08:38.919 Or how does that work. 138 00:08:39.159 --> 00:08:39.399 Yeah. 139 00:08:39.399 --> 00:08:42.639 So we have a few what we call metadata parsers, 140 00:08:43.039 --> 00:08:45.720 and some events have the same structure in the title 141 00:08:45.799 --> 00:08:51.320 of how they arrange their titles, so we can kind 142 00:08:51.360 --> 00:08:54.399 of do some smart logic by splitting on the word 143 00:08:54.480 --> 00:08:58.200 by or by dashes or commas, and then you get 144 00:08:58.679 --> 00:09:01.360 there like ninety percent of the way and then there's 145 00:09:01.440 --> 00:09:03.480 like some left over to do where it just go 146 00:09:03.519 --> 00:09:06.720 in and cleaned up by hand. But I guess this 147 00:09:06.759 --> 00:09:08.639 could also be improved in the future now that we 148 00:09:08.720 --> 00:09:12.159 have LMS and all of that to be more automated. 149 00:09:12.720 --> 00:09:16.679 But for now this has been proven to work out 150 00:09:16.679 --> 00:09:18.720 really well. 151 00:09:18.799 --> 00:09:21.399 Right, And you said that you have it all in 152 00:09:21.480 --> 00:09:26.240 YAMO files. So when there's a new conference or I 153 00:09:26.279 --> 00:09:28.159 was kind of assuming it was built on like rails 154 00:09:28.240 --> 00:09:31.559 or Hanami and had a database behind it. But is 155 00:09:31.600 --> 00:09:34.440 this more along the lines of something like a jackal 156 00:09:34.799 --> 00:09:38.200 or Bridgetown or something where you know, maybe you say, hey, 157 00:09:38.360 --> 00:09:40.639 my data is in these files, and so I'm just 158 00:09:40.720 --> 00:09:42.919 you know, I just build every time I get a 159 00:09:42.960 --> 00:09:43.600 new conference. 160 00:09:44.080 --> 00:09:46.159 Yeah, so for now, it's it is a rails up 161 00:09:46.200 --> 00:09:49.279 and it has a database. Okay, but what we do 162 00:09:49.440 --> 00:09:52.159 is that we go through all the AMMA files and 163 00:09:52.200 --> 00:09:55.879 import them into the database, just so we have a 164 00:09:55.960 --> 00:09:59.559 nicer interface to queer the data and kind of half 165 00:09:59.639 --> 00:10:05.039 speak profiles and event pages that's just easy to quer 166 00:10:05.080 --> 00:10:08.960 you and kind of build the websites around them, so 167 00:10:08.960 --> 00:10:11.679 they are all genamically generated on the service side and 168 00:10:11.679 --> 00:10:16.720 then served using the traditional rails requests response cycle. 169 00:10:18.159 --> 00:10:22.080 Gotcha, And I guess the other question I have is, 170 00:10:22.159 --> 00:10:24.519 you know, are you mostly focused on conferences or are 171 00:10:24.519 --> 00:10:28.440 you looking to do things with like meetups or if 172 00:10:28.480 --> 00:10:31.600 somebody puts up a good tutorial or something like that, 173 00:10:31.720 --> 00:10:34.039 you know, those are all videos that you may or 174 00:10:34.080 --> 00:10:36.480 may not want to pull in. I guess tutorials aren't events, 175 00:10:36.519 --> 00:10:37.639 but meetups are. 176 00:10:38.840 --> 00:10:39.039 Yeah. 177 00:10:39.080 --> 00:10:41.360 That was one of the reasons why I personally also 178 00:10:41.399 --> 00:10:45.159 wanted to move away from Ruby video, because this was 179 00:10:45.279 --> 00:10:49.399 meant to be focused on events, which also includes meetups, 180 00:10:49.440 --> 00:10:52.320 and we have a few meetup groups on there too, 181 00:10:52.799 --> 00:10:56.600 and not all the meetups are recording videos for the 182 00:10:56.919 --> 00:10:59.759 events and talks, which is also the other thing that 183 00:11:00.399 --> 00:11:02.960 I want to get away from Ruby video, because we 184 00:11:03.039 --> 00:11:05.320 want to still index all the talks that are happening at 185 00:11:05.360 --> 00:11:07.960 these meetups, even if they have no recording to it, 186 00:11:09.279 --> 00:11:13.440 So that you can at them as the titles, at descriptions, 187 00:11:13.440 --> 00:11:15.799 at the media data, at some of the slides if 188 00:11:15.840 --> 00:11:19.120 they have them available, or some of the resources like reposts, 189 00:11:19.120 --> 00:11:22.320 that you can still see that this talk and event 190 00:11:22.399 --> 00:11:25.360 took place at this time by the speaker, and this 191 00:11:25.440 --> 00:11:30.440 is all the information we know about it as well. 192 00:11:30.600 --> 00:11:34.840 But that's the thing. Like with tutorials, I think this 193 00:11:35.039 --> 00:11:38.320 is something that's harder to index in that sense that 194 00:11:38.399 --> 00:11:42.120 it keeps like it stays relevant, which I think this 195 00:11:42.200 --> 00:11:44.879 is still really good on YouTube or anywhere else where 196 00:11:44.919 --> 00:11:49.120 you host these tutorials. So I personally don't see at 197 00:11:49.200 --> 00:11:52.559 least in the near term that we kind of host 198 00:11:52.639 --> 00:11:55.519 these tours on on Ruby events as well. 199 00:11:56.120 --> 00:11:58.879 Okay, So I wonder if we could dig into these 200 00:11:59.000 --> 00:12:02.000 technicals a little bit, because you guys have built an 201 00:12:02.039 --> 00:12:07.159 actual production website using sequel Light and there some new 202 00:12:07.200 --> 00:12:11.360 feed reels features like solid que and also I think 203 00:12:11.360 --> 00:12:15.159 it's the first website that I can definitely remember has 204 00:12:15.320 --> 00:12:20.600 used page view transitions. So in terms of all these 205 00:12:20.639 --> 00:12:24.879 technologies in an actual app, what was your experience. 206 00:12:24.559 --> 00:12:28.120 Like, Yeah, as I said, when I started to build, 207 00:12:29.440 --> 00:12:34.879 I love to build things, but I am an engineer, 208 00:12:34.919 --> 00:12:38.519 so I am an engineer builder, so whenever I tried 209 00:12:38.559 --> 00:12:42.639 to build something new, it also has to be a 210 00:12:42.679 --> 00:12:47.759 way for me to discover tests some new technologies. So 211 00:12:48.679 --> 00:12:52.440 real builders will use proven tech and they just focused 212 00:12:52.519 --> 00:12:56.399 on the on the product, the feature, the and so on. 213 00:12:57.919 --> 00:13:01.399 So for me, as I said, when I had this 214 00:13:01.679 --> 00:13:05.759 initial idea of Ruby video, there were several technology that 215 00:13:05.960 --> 00:13:09.039 all came out and I wanted to try, and page 216 00:13:09.120 --> 00:13:12.799 view transition was one of the technology that I really 217 00:13:12.799 --> 00:13:18.320 wanted to try on. They had this demonstration where there 218 00:13:18.360 --> 00:13:21.039 is the same effect when you click on the small 219 00:13:21.600 --> 00:13:25.720 thumbnail of a video, then it's zoom up and you 220 00:13:26.200 --> 00:13:31.120 get this nice transition from the index to the show view, 221 00:13:33.279 --> 00:13:37.320 and I think that's pretty cool. At the same time, 222 00:13:37.600 --> 00:13:40.840 I had this feeling that in the rails industry, you know, 223 00:13:41.000 --> 00:13:46.080 always with the same topics, rail is dying and so on. 224 00:13:46.919 --> 00:13:51.759 A lot of the the impression that rail was old 225 00:13:53.039 --> 00:13:57.279 comes from some website built on rails that are that 226 00:13:57.399 --> 00:14:04.360 have some old look that they are not modern. Uh, 227 00:14:05.399 --> 00:14:07.919 that the back end is great, but the front end 228 00:14:08.000 --> 00:14:13.480 is built by back end developers, and I want it also, uh, 229 00:14:14.600 --> 00:14:18.320 this website to be some kind of flagship and that 230 00:14:18.480 --> 00:14:22.080 demonstrates that we we can build. We can get a 231 00:14:22.200 --> 00:14:27.279 nice uicks uh and UI with rails. Uh. You don't 232 00:14:27.320 --> 00:14:31.960 need to react, you don't need whatever front end framework 233 00:14:32.080 --> 00:14:36.440 to do this. And there are lots of technology availables 234 00:14:36.480 --> 00:14:41.480 nowadays with base you transition with Delawyn and some some 235 00:14:41.639 --> 00:14:44.519 component libraries that you can use to get something that 236 00:14:44.679 --> 00:14:45.440 is nice. 237 00:14:45.879 --> 00:14:49.240 Yeah, it looks great as as quite impressed. We just 238 00:14:49.320 --> 00:14:54.159 are clean and simple designers, which is awesome. Does the 239 00:14:54.440 --> 00:14:58.120 page transition to API hooks into tablet drive? Doesn't it? 240 00:14:59.480 --> 00:15:04.320 When Hm, I started the project, it wasn't available with 241 00:15:04.440 --> 00:15:09.600 Turbo drive, so I use a package I don't recall 242 00:15:09.639 --> 00:15:19.759 the name, yes exactly, that provide the the bridge between 243 00:15:19.799 --> 00:15:25.360 Turbo and Pagroot transition. Since then, uh, Patriot transition has 244 00:15:25.399 --> 00:15:30.759 been built in into Turbo, so now it's uh, it's 245 00:15:30.759 --> 00:15:31.639 a native feature. 246 00:15:32.519 --> 00:15:35.879 Cool. And how was this the first time you'd use 247 00:15:36.000 --> 00:15:38.639 sequel light on a production app or how do you 248 00:15:38.720 --> 00:15:39.360 used it before? 249 00:15:41.919 --> 00:15:44.879 For me, it was the first time. Yes, how did you. 250 00:15:44.840 --> 00:15:48.320 Find that change from I'm guessing postgrass that you used 251 00:15:48.320 --> 00:15:50.480 in the past. Was it was it a big change 252 00:15:50.519 --> 00:15:53.039 in terms of thinking and designing or was it pretty 253 00:15:53.120 --> 00:15:55.159 much seamless. 254 00:15:56.240 --> 00:15:59.799 Mm hmmm. I would say it was seamless in terms 255 00:15:59.799 --> 00:16:09.639 of a developer experience. What is nice is that doing 256 00:16:09.679 --> 00:16:14.480 a backup or if we need to dump some database, 257 00:16:14.519 --> 00:16:17.799 it's just a single fight that you need to to move. 258 00:16:23.519 --> 00:16:30.279 Combined with Camal and a small VPS hosting made the 259 00:16:30.360 --> 00:16:36.440 things amazingly cheap to host. That's that was I mean, 260 00:16:37.039 --> 00:16:43.799 compared to Heroku or whatever past where you always end 261 00:16:43.919 --> 00:16:47.960 up with a minimum of fifty year old per month, 262 00:16:48.320 --> 00:16:52.320 we could divide this almost by ten and get better 263 00:16:52.360 --> 00:16:53.360 performance out of it. 264 00:16:54.600 --> 00:17:00.159 So the performance language, I love that. I love that 265 00:17:00.240 --> 00:17:02.799 because yeah, I've had the same experience with Kamal and 266 00:17:03.600 --> 00:17:07.240 some of those tooling, so. 267 00:17:05.920 --> 00:17:09.440 So it's it's yeah. I mean, I wouldn't say that 268 00:17:10.160 --> 00:17:16.440 it was always perfect and that I sometimes spent more 269 00:17:16.480 --> 00:17:19.920 time that than I should have learning all of those 270 00:17:20.319 --> 00:17:23.119 Camal settings and so on, but that's that's something that 271 00:17:23.160 --> 00:17:27.319 I wanted to do also as part of growing experience, 272 00:17:27.359 --> 00:17:29.400 so that that it was okay for me to spend 273 00:17:29.440 --> 00:17:33.039 some time on this. But I'm not sure how you 274 00:17:33.200 --> 00:17:37.640 feel Marco about it. But for me, the the experience 275 00:17:37.680 --> 00:17:41.839 with as with Circulite, has been amazing. I mean that 276 00:17:42.960 --> 00:17:48.000 this the speed, the the API. There is nothing that 277 00:17:48.200 --> 00:17:51.759 really that I couldn't do up to now that I'm 278 00:17:51.880 --> 00:17:57.039 able to do in post grace or whatever database. 279 00:17:57.640 --> 00:18:00.319 Yeah, it's been similar experience for me. I didn't really 280 00:18:00.359 --> 00:18:03.960 have any problems with adapting from coming from prostgress. Mostly 281 00:18:05.279 --> 00:18:08.519 pretty much everything worked as I expected to work, and 282 00:18:09.920 --> 00:18:12.000 also from the query speed and all of that, it 283 00:18:12.000 --> 00:18:14.640 didn't really make any difference for me on how I 284 00:18:14.680 --> 00:18:18.000 built apps. But I think this is mostly also thanks 285 00:18:18.039 --> 00:18:20.599 to active record that does the heavy lifting for us 286 00:18:20.759 --> 00:18:22.880 in the bag we. 287 00:18:22.839 --> 00:18:25.680 Had for the full tech search to do a bit 288 00:18:28.119 --> 00:18:31.559 a bit more integration. I guess that this will with 289 00:18:32.079 --> 00:18:38.119 Rail's eight point one should be mostly covered with something 290 00:18:38.640 --> 00:18:42.720 official from what I understood, but it's not yet. Really 291 00:18:44.519 --> 00:18:52.480 we don't know exactly the boundaries. But now we have 292 00:18:52.759 --> 00:18:56.319 a full tech search that is performed by esk light 293 00:18:56.400 --> 00:18:58.720 and that works quite nicely. 294 00:18:59.599 --> 00:19:03.880 Did yeah have to change your database schema to be 295 00:19:03.960 --> 00:19:06.160 a sequel file instead of an RB file or is 296 00:19:06.200 --> 00:19:08.920 that something that they've fixed Because I knew until like 297 00:19:09.000 --> 00:19:10.640 a couple of years ago, if you wanted to do 298 00:19:10.680 --> 00:19:13.680 full tech search your sequel light, you couldn't have a 299 00:19:13.680 --> 00:19:17.480 schema dot orb it had to be a structured dot sequel. 300 00:19:17.640 --> 00:19:19.279 Is that something that they've changed now? 301 00:19:19.680 --> 00:19:24.319 I think so, because we are still using the RB schema. 302 00:19:24.799 --> 00:19:26.119 Okay, great, that's good to know. 303 00:19:26.480 --> 00:19:29.200 So have you thought about doing like a semantic search 304 00:19:29.240 --> 00:19:30.240 of some kind on there? 305 00:19:31.319 --> 00:19:39.680 Yes, the the very first version of Ruby video I 306 00:19:39.799 --> 00:19:43.279 used malisearch combined. 307 00:19:43.720 --> 00:19:47.119 That was nice to esq light because. 308 00:19:48.400 --> 00:19:53.279 I think at that time uh full tech search. It 309 00:19:53.359 --> 00:19:58.960 was probably possible with esclight, but either I couldn't find 310 00:19:59.839 --> 00:20:05.319 a up to date tutorial or things that that were 311 00:20:05.359 --> 00:20:08.920 built in Ruby. At that time, I feel like it 312 00:20:09.000 --> 00:20:13.480 was still a bit something new in the Reils world 313 00:20:14.039 --> 00:20:19.319 for building a production website. So I started to use 314 00:20:19.359 --> 00:20:26.680 a mail search and we we did some proof of 315 00:20:26.759 --> 00:20:32.400 concept for doing semantic search and like similar topics, similar 316 00:20:33.279 --> 00:20:40.640 finding similar dogs to one tales by. We created some 317 00:20:40.799 --> 00:20:44.680 embeddings and so on. That's something that we didn't push 318 00:20:44.759 --> 00:20:50.000 to production yet, but I'm really interested to work on 319 00:20:50.039 --> 00:20:55.319 this feature uh in in the upcoming months or so. 320 00:20:56.079 --> 00:20:59.240 That's that's really something where I think we can improve 321 00:21:00.480 --> 00:21:02.960 the overall discoverability of the content. 322 00:21:03.640 --> 00:21:09.680 Yeah. I've played with it some, mostly using vector vector 323 00:21:09.759 --> 00:21:13.240 stuff with either elastic search or postgress and yeah, I 324 00:21:13.279 --> 00:21:16.279 mean it's cool stuff and it works out because then 325 00:21:16.319 --> 00:21:19.880 you can if I don't put in exactly the term 326 00:21:20.440 --> 00:21:23.440 that a full tech search would, you know, miss on, 327 00:21:24.359 --> 00:21:26.079 it can figure out what I'm looking for and kind 328 00:21:26.119 --> 00:21:26.960 of give it to me anyway. 329 00:21:27.079 --> 00:21:31.599 So it's definitely something that we'll want to improve to 330 00:21:31.599 --> 00:21:32.839 get some semantic search. 331 00:21:33.480 --> 00:21:37.680 So what other things are you looking to add to it? 332 00:21:37.680 --> 00:21:43.599 It sounds like you're going to merge the Ruby Conferences 333 00:21:43.640 --> 00:21:47.640 dot org and Ruby events dot org. Do you do 334 00:21:47.640 --> 00:21:49.599 you have other ideas of things that you want to 335 00:21:49.599 --> 00:21:51.880 add to this or bring into it, or do you 336 00:21:51.920 --> 00:21:54.440 have kind of a kind of a limited scope that 337 00:21:54.519 --> 00:21:55.119 keeps it simple. 338 00:21:55.279 --> 00:21:57.799 Yeah, I mean there's a bunch you can do and 339 00:21:57.839 --> 00:21:59.640 a bunch of stuff you want to do. But then again, 340 00:21:59.680 --> 00:22:02.720 it's kind of tricky to build out all these features 341 00:22:02.759 --> 00:22:08.759 and make it work, especially because Ruby conscious that didn't 342 00:22:08.799 --> 00:22:11.440 really have a lot of meta data around any of 343 00:22:11.440 --> 00:22:14.200 the events. It was pretty much the name, the dates 344 00:22:14.200 --> 00:22:17.240 in the location right and now on Ruby Events we 345 00:22:17.319 --> 00:22:21.440 have the speakers, the talks, all the descriptions, so it's 346 00:22:21.440 --> 00:22:23.160 not just a one to one copy that we can 347 00:22:23.200 --> 00:22:26.400 take over and then it's good. So yeah, are looking 348 00:22:26.440 --> 00:22:30.039 on ways to bring over all the events. We have 349 00:22:30.079 --> 00:22:32.960 the events index now, but I have no speakers and 350 00:22:33.000 --> 00:22:35.519 no talks touched to them. So that's what be one 351 00:22:35.519 --> 00:22:38.119 thing to just go back to all these events and 352 00:22:38.160 --> 00:22:42.240 to try to add all these old talks so you 353 00:22:42.319 --> 00:22:45.359 have the data for it. But also then looking at 354 00:22:45.880 --> 00:22:49.400 the future. Having attended a bunch of conscious in the 355 00:22:49.480 --> 00:22:52.559 last few years, I noticed that the people that organized 356 00:22:52.599 --> 00:22:55.880 these events struggle with just the whole workflow as well. 357 00:22:56.440 --> 00:22:58.480 And one of the aspects of that is also the 358 00:22:58.519 --> 00:23:02.640 call for papers and finding the right platforms to host it. 359 00:23:02.640 --> 00:23:05.720 It seems to be quite an issue that's quite expensive 360 00:23:05.759 --> 00:23:08.440 for conference organizers to just be able to host the CFP. 361 00:23:09.559 --> 00:23:12.279 So we were also looking in two ways to make 362 00:23:12.319 --> 00:23:15.079 it easier to have like a full process for conference 363 00:23:15.200 --> 00:23:18.960 organizers to go from announcing the events up until the 364 00:23:19.000 --> 00:23:23.680 point to leasing the videos. To have this full workflow on. 365 00:23:24.880 --> 00:23:28.519 Let's announce the CFP, let's collect the proposals, let's finish 366 00:23:28.599 --> 00:23:32.599 it up. Then let's publish a schedule, let's publish the 367 00:23:32.680 --> 00:23:37.720 actual talk titles, Let's publish the event as I think 368 00:23:37.720 --> 00:23:41.319 that's happening. Then during the event, maybe there's some updates. 369 00:23:41.359 --> 00:23:46.119 Maybe there's just the currently the talk is currently running, 370 00:23:46.920 --> 00:23:49.880 and then after the talk, after the event, you don't 371 00:23:49.920 --> 00:23:55.000 get the recordings attached to the same the same talks. 372 00:23:55.480 --> 00:23:58.160 So just to kind of have this full experience on 373 00:23:59.160 --> 00:24:03.079 for conference organized, but also for attendees, to have this 374 00:24:03.160 --> 00:24:05.920 one interface platform where you can just go to and 375 00:24:06.000 --> 00:24:10.359 find the information you need. Another aspect also was to 376 00:24:12.039 --> 00:24:16.039 add photos official photos from the event, but also from 377 00:24:16.279 --> 00:24:19.839 social media. So if you use the conference hashtag, that 378 00:24:19.880 --> 00:24:22.920 we show these photos right next to the event itself 379 00:24:22.960 --> 00:24:25.440 and give some more impressions of what the event was 380 00:24:25.559 --> 00:24:28.799 like from people that's attend the event over talking about 381 00:24:28.839 --> 00:24:31.599 the event in some way or a number just to 382 00:24:31.680 --> 00:24:35.359 kind of bring the whole community aspect together, especially now 383 00:24:36.000 --> 00:24:39.799 when we have the social media breakup where everybody is 384 00:24:39.880 --> 00:24:42.960 just on some social platform but not everybody is on 385 00:24:43.000 --> 00:24:46.000 the same platform. At least with these rupy events, that 386 00:24:46.000 --> 00:24:49.279 we have one place where we see the stuff that 387 00:24:49.319 --> 00:24:55.720 we want to learn from, at least for the engineering 388 00:24:55.720 --> 00:24:57.359 part of our careers. 389 00:24:58.319 --> 00:25:04.440 Nice with this, like just like running this project, do 390 00:25:04.200 --> 00:25:06.799 you do you guys always see it always as a 391 00:25:06.839 --> 00:25:10.599 passion project? Do you reckon? You might like the sponsorship 392 00:25:10.720 --> 00:25:13.440 or some other kind of revenue model in the future, 393 00:25:13.839 --> 00:25:15.759 because if you're going to do something like come up 394 00:25:15.759 --> 00:25:18.759 with the whole workflow for conferences to run, see I 395 00:25:18.880 --> 00:25:20.640 FeAs and so that seems like quite a lot to 396 00:25:20.680 --> 00:25:21.799 do just for fun. 397 00:25:22.319 --> 00:25:24.240 I mean, I haven't really thought about how you would 398 00:25:24.319 --> 00:25:27.599 monetize it. I'm sure there are ways to do it, 399 00:25:28.119 --> 00:25:32.480 but then again, in the terms of community, it doesn't 400 00:25:32.519 --> 00:25:35.440 really seem to make sense to just monetize the whole 401 00:25:35.480 --> 00:25:39.359