WEBVTT 1 00:00:07.080 --> 00:00:11.000 Hello, everyone, Welcome to an episode of your own I 2 00:00:11.240 --> 00:00:14.560 hope today. I'm Gussie and I'm joined on the panel 3 00:00:14.640 --> 00:00:15.919 by Page. 4 00:00:15.599 --> 00:00:17.480 Hey, everybody and t J. 5 00:00:17.960 --> 00:00:22.120 Everyone awesome, and our guest today is Billian Magida. Hi, 6 00:00:22.160 --> 00:00:25.679 Di dear, Hi, let's talk about maybe you telling us 7 00:00:25.679 --> 00:00:28.920 a bit about yourself, why you're famous, what you do development, 8 00:00:29.000 --> 00:00:30.280 and yeah, that kind of stuff. 9 00:00:30.679 --> 00:00:36.320 Okay, I'm not sure famous. Okay. My name is Dillion 10 00:00:36.479 --> 00:00:40.359 and I'm from Nigeria, a software engineer and a technical writer. 11 00:00:41.079 --> 00:00:45.359 Currently work at this dot and I write on a 12 00:00:45.399 --> 00:00:48.320 lot of publications, a lot of organizations. I write with 13 00:00:48.359 --> 00:00:51.600 free cood, CAUMP, I write with Lord Rocket and a 14 00:00:51.679 --> 00:00:55.240 few other places. And I think that's the basic about me. 15 00:00:57.000 --> 00:00:59.679 So, in terms of your writing, is there any kind 16 00:00:59.719 --> 00:01:03.960 of things or topics you like writing about or enjoy. 17 00:01:03.920 --> 00:01:08.319 Mostar As a software engineer, I write about or I 18 00:01:08.680 --> 00:01:11.799 love writing about everything I learned, but mostly I write 19 00:01:11.799 --> 00:01:14.799 about web development because that's my speciality. And I also 20 00:01:14.879 --> 00:01:17.359 have a major focus on the front end. So you'll 21 00:01:17.359 --> 00:01:21.000 find a lot of articles around front end technologies, frameworks, 22 00:01:21.599 --> 00:01:26.560 practices around frame around front end generally cool. 23 00:01:27.040 --> 00:01:29.799 So one of the articles you wrote about recently was 24 00:01:29.920 --> 00:01:34.400 about building a source Paul gats Bie, and maybe we 25 00:01:34.439 --> 00:01:36.159 could maybe look at that a bit. So in terms 26 00:01:36.200 --> 00:01:38.400 of gats be itself, for people that maybe don't know 27 00:01:38.400 --> 00:01:40.719 about gasp, you can maybe talk about gats to itself 28 00:01:40.719 --> 00:01:42.799 as a platform and what you can do with it. 29 00:01:42.879 --> 00:01:47.799 Okay, gads b is a React framework, is built based 30 00:01:47.840 --> 00:01:52.120 on React. And the beauty of gads B that I 31 00:01:52.280 --> 00:01:56.079 know is that it's a static generator. Two, it's just 32 00:01:56.079 --> 00:01:59.560 for building or use for generating static sites. So you 33 00:01:59.640 --> 00:02:03.200 have your or you have your javascripts, you have every 34 00:02:03.200 --> 00:02:06.640 of your assets, and then they're just compound together to 35 00:02:06.719 --> 00:02:10.000 create those static sites and then busily about gat to 36 00:02:10.039 --> 00:02:14.520 be again is it uses graph Quo, which means within 37 00:02:14.599 --> 00:02:19.120 your pages, you can query notes that I created inside 38 00:02:19.159 --> 00:02:22.560 of your application or from other plugins, so you can 39 00:02:22.639 --> 00:02:25.520 query those notes and then build your application based on 40 00:02:25.599 --> 00:02:26.400 those notes. 41 00:02:26.639 --> 00:02:30.039 So I'm pretty familiar with gatsby. I actually built my 42 00:02:30.080 --> 00:02:33.360 own personal website with it, and one thing that I've 43 00:02:33.360 --> 00:02:36.360 noticed about it is that it really it takes advantage 44 00:02:36.400 --> 00:02:39.639 of the plug in ecosystem that has kind of sprung 45 00:02:39.719 --> 00:02:42.120 up around it. It seems like whatever you might need 46 00:02:42.639 --> 00:02:48.400 in terms of links or Google fonts, or analytics or whatever. 47 00:02:48.680 --> 00:02:51.680 There's probably a gasty plug in for it. But I've never, 48 00:02:52.319 --> 00:02:54.719 certainly never really looked under the hood of the plugins 49 00:02:54.719 --> 00:02:56.680 to see how they're built. So I'd love to hear 50 00:02:56.840 --> 00:03:00.479 how you you know, how you got started, what you 51 00:03:01.039 --> 00:03:03.319 needed that there wasn't a plugin for, and then how 52 00:03:03.360 --> 00:03:06.280 you went about building one and adding it into the ecosystem. 53 00:03:06.759 --> 00:03:09.520 Okay, yeah, I forgot to mention that gadsby has a 54 00:03:09.599 --> 00:03:13.680 very large plug in ecosystem. Almost, if not every everything 55 00:03:13.680 --> 00:03:18.400 you need links images the team. The team at gads 56 00:03:18.400 --> 00:03:21.400 b they are also creators of some of these plugins, 57 00:03:21.759 --> 00:03:25.199 and they optimize the sites in various ways. So for 58 00:03:25.400 --> 00:03:29.680 me before what I had been using plugins right from 59 00:03:29.680 --> 00:03:33.080 when I started, because even when you're starting, you're already 60 00:03:33.080 --> 00:03:36.479 starting based on one or two of the most important 61 00:03:36.840 --> 00:03:40.439 plugins that are necessary for building your site, or one 62 00:03:40.479 --> 00:03:43.680 of which is the gads be transformer too, there are 63 00:03:43.759 --> 00:03:47.560 a few very important ones when starting off. So when 64 00:03:47.599 --> 00:03:51.800 I started, I started installing plugins and I got the 65 00:03:51.800 --> 00:03:54.039 most everything I need. Like, if I needed something, all 66 00:03:54.039 --> 00:03:56.319 I just have to is go online such a gads 67 00:03:56.360 --> 00:03:59.000 bee this, and then there is a plugin for it. 68 00:03:59.400 --> 00:04:02.360 So my first attempt at creating a plug in was 69 00:04:03.159 --> 00:04:06.680 I didn't really need to do something. I just wanted 70 00:04:06.719 --> 00:04:09.960 to explore plugins. I just wanted to create a plugin 71 00:04:10.000 --> 00:04:12.000 of my own. And the first one I created was 72 00:04:12.080 --> 00:04:15.240 for I don't know if you're familiar with Depth Too, blogging 73 00:04:15.319 --> 00:04:20.399 platform for majorly web or regioly software engineers. So on 74 00:04:20.879 --> 00:04:24.920 Depth Too. When writing articles using the markdown, you can 75 00:04:25.439 --> 00:04:29.040 there's something they call liquid tags. So liquid tags are 76 00:04:29.439 --> 00:04:33.519 a beautiful way to embed services on your on your blog, 77 00:04:33.800 --> 00:04:37.639 so you can embed twits, you can embed code pens, 78 00:04:37.839 --> 00:04:40.560 and instead of you know, going onto code pen and 79 00:04:40.560 --> 00:04:44.519 then copying the embedded code, you just use this liquid tag. 80 00:04:44.759 --> 00:04:48.720 Start with a calibrase and with the calibrese then the 81 00:04:48.800 --> 00:04:52.079 code pen and then maybe the link of the code pen, 82 00:04:52.560 --> 00:04:56.560 and then in the built blog it has the embedment 83 00:04:56.720 --> 00:04:59.920 of that code pen. So when I saw that, I 84 00:05:00.000 --> 00:05:03.279 I was building my gats peer application, my own personal blog, 85 00:05:03.319 --> 00:05:06.600 and I wanted to embed all of these services too. 86 00:05:07.040 --> 00:05:11.160 So instead of going online to copy the embed code, 87 00:05:11.600 --> 00:05:15.839 I thought about creating my own liquid bags, but for 88 00:05:16.040 --> 00:05:19.199 gads be applications. So it was while doing that I 89 00:05:19.240 --> 00:05:26.079 discovered how how interesting or how fascinating it was when 90 00:05:26.199 --> 00:05:29.000 during your own pluggins. Yeah, that was my first experience 91 00:05:29.000 --> 00:05:30.120 with creating my own plugging. 92 00:05:30.319 --> 00:05:33.560 Oh, I mean I first came across Gatsby. I think 93 00:05:33.680 --> 00:05:36.600 it's a couple of years ago when I was doing 94 00:05:36.600 --> 00:05:38.560 that typical thing of a developer trying to do a 95 00:05:38.560 --> 00:05:41.360 new blog, and you get more excited about the process 96 00:05:41.439 --> 00:05:44.519 right of doing the development and creating a blog. And 97 00:05:44.560 --> 00:05:46.800 one of the things I struggled with back then was 98 00:05:47.199 --> 00:05:50.959 understanding how it all works. And maybe it's probably changing now. 99 00:05:51.000 --> 00:05:53.879 I'm guessing in terms of new material and new tutorials, 100 00:05:54.319 --> 00:05:58.839 but in terms of getting started, how easy is it now? 101 00:05:58.959 --> 00:06:00.920 Just say, in terms of some he wants to build 102 00:06:00.920 --> 00:06:04.439 a blog right and page as we already, but how 103 00:06:04.480 --> 00:06:06.120 easy do you think it is now in terms of 104 00:06:06.600 --> 00:06:10.079 getting a blog up there and getting started content and 105 00:06:10.120 --> 00:06:10.680 everything else. 106 00:06:10.920 --> 00:06:13.800 Well, with a lot of bloggings created and a lot 107 00:06:13.839 --> 00:06:17.879 of templates created of course by the community, it's very easy. 108 00:06:18.800 --> 00:06:20.959 In fact, if you do not have a design of 109 00:06:21.040 --> 00:06:24.360 your own, you can just go to the Gatsby side 110 00:06:24.439 --> 00:06:27.279 and you can just duplicate the templates, have it's in 111 00:06:27.399 --> 00:06:29.959 your own name, and then you have your blog already. 112 00:06:30.360 --> 00:06:33.040 So it's very very easy. And a lot of templates 113 00:06:33.079 --> 00:06:36.560 are still they're still being created for blogs, for e 114 00:06:36.639 --> 00:06:40.399 commerce websites, for a lot of other use cases. 115 00:06:40.720 --> 00:06:43.639 Yeah, I would. I would definitely say that that is 116 00:06:43.639 --> 00:06:46.680 the case. On the Gatsby website. They even have a 117 00:06:47.160 --> 00:06:52.720 thing that they call Starters, which is hundreds of gas 118 00:06:52.759 --> 00:06:56.800 starter websites that people have built, and they're for everything. 119 00:06:56.879 --> 00:06:59.959 There's ones that work for blogs, there's ones that are 120 00:07:00.160 --> 00:07:03.560 set up for e commerce, there's ones that are The 121 00:07:03.560 --> 00:07:06.439 one that I used was called an Advanced Starter, and 122 00:07:06.519 --> 00:07:09.040 it has a whole bunch of stuff built into it 123 00:07:09.240 --> 00:07:12.120 or already kind of I guess, set up plugins for 124 00:07:12.279 --> 00:07:16.759 SEO and plugins for sharing, and plugins for discuss if 125 00:07:16.800 --> 00:07:20.040 you want to have comments. But what I really liked 126 00:07:20.040 --> 00:07:22.240 about that one in particular was even though it had 127 00:07:22.319 --> 00:07:25.519 all of this kind of configuration set up, it had 128 00:07:25.600 --> 00:07:29.160 no styles, so you were able to then completely take 129 00:07:29.279 --> 00:07:31.759 control of how you wanted it to look. And really 130 00:07:32.199 --> 00:07:34.800 I added a bunch of stuff, I removed a bunch 131 00:07:34.839 --> 00:07:37.959 of plugins that I didn't care about. So there's there's 132 00:07:38.000 --> 00:07:41.279 something for everybody, regardless of what you're looking for. There's 133 00:07:41.279 --> 00:07:43.639 ones that are set up to run on aws. There's 134 00:07:43.720 --> 00:07:47.480 ones that have authentication. There's ones that integrate with different 135 00:07:47.519 --> 00:07:51.600 CMS systems already. There's if you if you can tell 136 00:07:51.879 --> 00:07:55.439 like what you're looking for, or if there's some you know, 137 00:07:55.560 --> 00:07:58.480 buzzwords that you're trying to hit, you can probably find 138 00:07:58.519 --> 00:08:01.439 it as a category under these starters. So it's really 139 00:08:01.879 --> 00:08:05.279 really helpful in that regard. Yeah, the gats B side 140 00:08:05.360 --> 00:08:08.839 is pretty cool, although I know that next is like 141 00:08:08.959 --> 00:08:12.439 really gunning for them in addition to its server side 142 00:08:12.439 --> 00:08:15.720 rendering and its ability to be flexible enough to be 143 00:08:15.759 --> 00:08:19.199 a full application as well. So it'll be interesting to 144 00:08:19.240 --> 00:08:21.800 see how they continue to compete with each other and 145 00:08:21.879 --> 00:08:23.439 improve because of it. 146 00:08:24.199 --> 00:08:26.319 I'm curious too, So the blog post you wrote is 147 00:08:26.319 --> 00:08:30.600 about a source plug in, so is source there referring 148 00:08:30.639 --> 00:08:34.639 to the content itself? It's going to drive like a blogger. 149 00:08:34.639 --> 00:08:37.080 I'm curious what sources in this context? 150 00:08:37.639 --> 00:08:44.000 Okay, source context of SOX plugging is our quality feature. 151 00:08:45.159 --> 00:08:49.320 Oh it technique. It's just a technique for pulling content 152 00:08:50.240 --> 00:08:55.279 from various sources, so you can either pull locally or 153 00:08:55.879 --> 00:09:00.559 pull externally from another website from an EPI. That's just 154 00:09:00.559 --> 00:09:01.720 what the SCE means. 155 00:09:01.759 --> 00:09:04.240 The gotchet so it would be like I want to 156 00:09:04.320 --> 00:09:06.519 use gas By to build my site, but the content 157 00:09:06.559 --> 00:09:10.320 itself is in wherever right, some other platforms some of 158 00:09:10.360 --> 00:09:10.840 the a p I. 159 00:09:11.159 --> 00:09:14.759 Okay, so I'm guessing this is all kind of part 160 00:09:14.799 --> 00:09:21.399 of the jam stack, right. I feel like funtended and 161 00:09:21.399 --> 00:09:25.200 fun tend them. I think so with regards to the 162 00:09:25.240 --> 00:09:28.679 whole kind of ecosystem, I know that page mentioned next 163 00:09:29.759 --> 00:09:32.159 what is it? What are the options out there? And 164 00:09:32.440 --> 00:09:35.679 why does gats before you stand out compared to next 165 00:09:35.720 --> 00:09:37.799 years or other thing? It's got to be used for 166 00:09:38.360 --> 00:09:39.559 this kind of thing. 167 00:09:39.639 --> 00:09:43.679 Oh well, when you look at next years, in my 168 00:09:43.799 --> 00:09:50.080 own experience, next year is more performance or specifically for 169 00:09:50.720 --> 00:09:54.360 server side rengering. Of course it does start excite generation. 170 00:09:54.919 --> 00:09:59.039 But when you look at Gatsby and next year is 171 00:09:59.039 --> 00:10:04.120 in my experience, if you want static static assets at 172 00:10:04.159 --> 00:10:07.639 the end of the day, Gatsby has a lot of 173 00:10:07.759 --> 00:10:11.279 support for that. I mean that is even their their 174 00:10:11.440 --> 00:10:15.080 main their main product. But when you're looking at server 175 00:10:15.240 --> 00:10:18.000 side rendering, then you can go next years. So of 176 00:10:18.039 --> 00:10:21.320 course you hear a lot of arguments about next years 177 00:10:21.360 --> 00:10:25.360 doing all that gats It does. But in GADS with defense, 178 00:10:25.399 --> 00:10:28.480 I will say gads we has a lot of things 179 00:10:28.519 --> 00:10:31.840 that makes them exceptional. Once it comes to static side generator, 180 00:10:32.000 --> 00:10:34.759 one of which is the source plug in, and then 181 00:10:34.879 --> 00:10:39.720 another is the plug plugging ecosystem, you see a lot 182 00:10:39.799 --> 00:10:44.480 of plugging. So if you're doing static sites, in my opinion, 183 00:10:45.399 --> 00:10:48.440 next years doesn't come as closed as Gatsby. But once 184 00:10:48.480 --> 00:10:52.159 you're doing anything server side, then next year stakes doing. 185 00:10:52.320 --> 00:10:55.519 Oh yeah, I'm looking at the gas library right now 186 00:10:55.639 --> 00:10:59.279 and the website it says you've got more than twenty 187 00:10:59.320 --> 00:11:03.480 one hundred product for actually building your different websites. So 188 00:11:03.559 --> 00:11:06.679 clearly a lot of work has gone into the community 189 00:11:07.279 --> 00:11:12.320 to So if somebody wanted to learn how to create 190 00:11:12.320 --> 00:11:15.639 the first plug in and what you give them based 191 00:11:15.639 --> 00:11:17.960 on your own experience and what they've gone through so far. 192 00:11:18.240 --> 00:11:21.120 Well creating a plugging first, It depends on what you 193 00:11:21.240 --> 00:11:25.679 want to do. There are transformer plugins transformed plugging as 194 00:11:25.919 --> 00:11:30.480 the name as name means, it's just you're transforming an asset, 195 00:11:30.600 --> 00:11:34.879 you're transforming data, you're transforming and image. There are also 196 00:11:35.080 --> 00:11:39.120 source plugins, and those are the two common ones. I 197 00:11:39.120 --> 00:11:42.480 don't know if there are any other category. So, and 198 00:11:42.639 --> 00:11:46.960 the guard beside has documentation on this. You can try 199 00:11:47.000 --> 00:11:50.759 some advanced stuff too, but that would heavily depend on 200 00:11:50.799 --> 00:11:54.000 how you understand the way these plugins work. So if 201 00:11:54.000 --> 00:11:57.360 your greatness source plugging, there is a there is. They're 202 00:11:57.440 --> 00:12:00.759 just basic information you need and and the rest is 203 00:12:00.840 --> 00:12:04.159 up to you. There are optional tools you can use. 204 00:12:04.200 --> 00:12:08.519 There are optional methods that the Gatsby to expose this 205 00:12:08.799 --> 00:12:11.519 if you're interested in them. But then at the very 206 00:12:11.559 --> 00:12:15.320 basic level, the documentation provides enough information that you need 207 00:12:15.360 --> 00:12:19.240 in creating any plugging, except you're trying to do something 208 00:12:19.399 --> 00:12:21.879 that they were in prepared for. 209 00:12:22.879 --> 00:12:26.279 So, Dillian, I'm looking at your personal website now, did 210 00:12:26.320 --> 00:12:27.440 you build this with Gatsby? 211 00:12:28.240 --> 00:12:30.519 Yes, that's my very first experience with Gatsby. 212 00:12:30.799 --> 00:12:33.679 Nice. I would have been disappointed if it had been 213 00:12:33.720 --> 00:12:38.840 anything else, I think. So, I see on your about 214 00:12:38.919 --> 00:12:42.799 me page that you're actually the founder of a thing 215 00:12:42.879 --> 00:12:45.120 called the Web for five. Can you tell us a 216 00:12:45.159 --> 00:12:46.320 little bit about what that is. 217 00:12:46.919 --> 00:12:50.679 The word for five was a platform I created specifically 218 00:12:50.720 --> 00:12:55.159 for writing my own articles. And the reason I created 219 00:12:55.240 --> 00:12:58.480 that was delion Miki. That it's called my personal website 220 00:12:59.480 --> 00:13:05.200 wasn't exactly a blog, like. It's my own personal space 221 00:13:05.200 --> 00:13:08.679 for writing stuff. So I can write about personal life 222 00:13:08.720 --> 00:13:12.039 stories and I can also write about articles so I 223 00:13:12.080 --> 00:13:16.519 needed this other space where it to be strictly web 224 00:13:16.639 --> 00:13:21.720 development articles, no personal story. And then also I was 225 00:13:21.799 --> 00:13:27.120 hoping that I would get authors, guest authors that will 226 00:13:27.159 --> 00:13:29.200 join me on that platform. And the reason why it's 227 00:13:29.279 --> 00:13:32.480 named web for five years, I wanted to really demystify 228 00:13:32.600 --> 00:13:38.320 web topics there. Although people commonly misunderstand me. They think 229 00:13:38.399 --> 00:13:42.559 that it's meant for five year olds, but it's that's 230 00:13:42.639 --> 00:13:45.799 not possible. But the main idea was just demystifying it 231 00:13:45.919 --> 00:13:49.639 to this smallest level that anybody could understand. 232 00:13:49.919 --> 00:13:52.879 That's very cool, so kind of like I'm five on Reddit. 233 00:13:53.639 --> 00:13:55.600 Yeah, that's it nice. 234 00:13:55.799 --> 00:13:59.080 I like this actually quite a bit because you're you're 235 00:13:59.080 --> 00:14:01.799 covering I'm just looking. So we put the link to 236 00:14:01.840 --> 00:14:04.639 it in the show notes. But things like document fragment 237 00:14:04.720 --> 00:14:09.440 and the dom parameters and arguments, substring and slice methods 238 00:14:09.480 --> 00:14:11.840 of strings, like these are topics that I think are 239 00:14:12.320 --> 00:14:15.759 super valuable and you don't see covered very often, right, Like, 240 00:14:15.799 --> 00:14:18.120 this isn't a super hip or trendy thing to cover, 241 00:14:18.200 --> 00:14:21.559 but it's actually super useful. So this is kind of 242 00:14:21.600 --> 00:14:24.320 a I'm sort of fascinated by the site of people 243 00:14:24.320 --> 00:14:24.720 looking through. 244 00:14:25.279 --> 00:14:28.039 That was goal. My goal is to touch all those 245 00:14:28.200 --> 00:14:33.200 small topics that you really don't see often and sometimes 246 00:14:33.279 --> 00:14:36.320 they exist, but you're not just outwagh that there is 247 00:14:36.399 --> 00:14:38.759 something like this. It just creating websites. 248 00:14:39.080 --> 00:14:42.000 Yeah, the file input field and depth. I think I 249 00:14:42.039 --> 00:14:46.480 need to bookmark this one. These are like the I 250 00:14:46.519 --> 00:14:49.000 swear like that's one of the great and horrible things 251 00:14:49.000 --> 00:14:50.960 about the web is like there's all these little like 252 00:14:51.039 --> 00:14:53.279 nooks and crannies for things that have been around for 253 00:14:53.320 --> 00:14:57.039 a while, and some of them are just completely shrouded 254 00:14:57.039 --> 00:15:00.759 in mystery that we just try to ignore. But sometimes 255 00:15:00.759 --> 00:15:02.080 you need to know some of this stuff. 256 00:15:02.279 --> 00:15:05.720 Yeah, I mean I definitely second that because we I 257 00:15:05.799 --> 00:15:08.879 think it's the thing where once you've been in coding 258 00:15:08.919 --> 00:15:12.440 for a while, we forget that sometimes that kind of 259 00:15:12.480 --> 00:15:15.559 basic elements and always that will cover it. Or maybe 260 00:15:15.720 --> 00:15:18.919 you might have used it in a project briefly or 261 00:15:19.039 --> 00:15:22.639 don't fully understand how it can be used elsewhere and 262 00:15:22.720 --> 00:15:25.639 the power of a particular feature set or whatever. So 263 00:15:25.720 --> 00:15:28.360 I mean, in terms of you're writing, then how do 264 00:15:28.440 --> 00:15:31.639 you decide what you write and what your process? Do 265 00:15:31.679 --> 00:15:35.639 you do an outline first and then maybe working for 266 00:15:35.679 --> 00:15:37.799 a few weeks, do you have like a calendar that 267 00:15:37.840 --> 00:15:40.759 you have your articles that you're writing about and how 268 00:15:40.799 --> 00:15:42.600 to kind of go about the process of if you're 269 00:15:42.600 --> 00:15:45.879 writing for various blogs and websites. 270 00:15:45.799 --> 00:15:50.120 I have one. I have my personal trailok board where 271 00:15:50.200 --> 00:15:54.679 I dropped my arctical ideas. So this icol inspirations. They 272 00:15:54.720 --> 00:15:58.840 come sometimes when I find when I experience a bog 273 00:15:59.399 --> 00:16:01.600 and then I go on Google and then maybe it 274 00:16:01.639 --> 00:16:04.000 takes me a lot of time in finding the solution. 275 00:16:04.759 --> 00:16:07.600 So when I finally get the solution, I write about 276 00:16:07.639 --> 00:16:11.440 it so that anyone using anyone who experiences the same 277 00:16:11.559 --> 00:16:16.279 now has an article that clearly covers that bog. Then 278 00:16:16.279 --> 00:16:19.919 some other inspirations when I discover some tools I never 279 00:16:20.000 --> 00:16:24.559 knew existed, or some APIs, maybe dumb APIs I never 280 00:16:24.639 --> 00:16:27.679 knew existed. Once I come about them, I try to 281 00:16:27.879 --> 00:16:30.720 just I just try to let the public know that 282 00:16:31.399 --> 00:16:34.480 such tool exists and this is how to use them. 283 00:16:34.679 --> 00:16:37.360 And a very good example was the web share API. 284 00:16:37.559 --> 00:16:40.320 I never knew there was a web share API. Whenever 285 00:16:40.360 --> 00:16:43.039 I wanted to add sharing features to my applications, I 286 00:16:43.159 --> 00:16:46.879 have to go to Twitter and copy the template RL 287 00:16:47.159 --> 00:16:50.559 and go to LinkedIn. But when I discovered the webshare API, 288 00:16:50.759 --> 00:16:55.080 the navigator, how it connects with your mobile applications and 289 00:16:55.159 --> 00:16:59.399 giving you access to share on WhatsApp, on Facebook. I 290 00:16:59.440 --> 00:17:02.200 wrote about it, and I think till now I think 291 00:17:02.200 --> 00:17:05.440 that's my highest viewed article because when I hear it 292 00:17:05.519 --> 00:17:09.599 on Sweeter, people were like, wow, so this existed. So 293 00:17:09.720 --> 00:17:12.440 sometimes when I discover amazing twos like that, I write 294 00:17:12.480 --> 00:17:15.920 about them. And then sometimes I write about articles that 295 00:17:16.000 --> 00:17:19.960 I want to learn. I want to know how they work. 296 00:17:20.440 --> 00:17:23.680 So maybe in my workplace or maybe I'm just going 297 00:17:23.680 --> 00:17:26.960 around the internet and I see, for example, the fragments. 298 00:17:27.000 --> 00:17:30.720 When I saw the document Fragments, I really didn't know 299 00:17:30.759 --> 00:17:33.680 how they worked. So I had it on my board 300 00:17:33.880 --> 00:17:35.640 that I was going to write about it, and then 301 00:17:35.680 --> 00:17:38.559 that caused me to make a lot of research and 302 00:17:38.599 --> 00:17:40.079 then I find a little bit about it. 303 00:17:40.599 --> 00:17:44.119 That's very cool. I'm still clicking around on your website. 304 00:17:44.240 --> 00:17:48.759 You have you have written for a bunch of publications, 305 00:17:49.119 --> 00:17:54.480 like you said, log Rocket, dev Dotto Vonage. So I'm 306 00:17:54.519 --> 00:17:58.680 curious how did you get in with those publications or 307 00:17:58.680 --> 00:18:01.720 free code Camp. Did you submit articles to them? Did 308 00:18:01.759 --> 00:18:05.160 they come to you with it? Like? How how does 309 00:18:05.200 --> 00:18:08.119 that go for anybody who would be interested in potentially 310 00:18:08.200 --> 00:18:10.039 writing for things like this in the future. 311 00:18:10.400 --> 00:18:15.319 Well sometimes I've had one occasion where they came to me, 312 00:18:16.119 --> 00:18:19.440 but for most others, I'm the one applying. And the 313 00:18:19.480 --> 00:18:22.440 reason why I love writing in various places is I 314 00:18:22.599 --> 00:18:26.279 don't just want to have my contents in one place. 315 00:18:27.079 --> 00:18:32.119 I believe frequent Camp has their own audience, log Rocket 316 00:18:32.200 --> 00:18:34.200 has their own audience, so, you know, an attempt to 317 00:18:34.240 --> 00:18:38.960 reach out to everyone's audience. Then I try to spread 318 00:18:39.000 --> 00:18:42.079 my contents around. But for anyone trying to apply some 319 00:18:42.119 --> 00:18:44.240 of them, they have their right for our speech. Freqal 320 00:18:44.319 --> 00:18:48.480 campus years, log Rocket has years, associates, and few other 321 00:18:48.519 --> 00:18:51.720 places I have they have theyears. And sometimes when your 322 00:18:51.759 --> 00:18:54.759 articles want someone to cover your articles somewhere, they reach 323 00:18:54.799 --> 00:18:57.640 out and they're like, okay, so your article here and 324 00:18:57.640 --> 00:18:59.319 I would love you to write for us, and this 325 00:18:59.519 --> 00:19:02.319 is what we have if you're interested. 326 00:19:02.720 --> 00:19:05.960 Awesome. And in terms of your article so far, are 327 00:19:05.960 --> 00:19:08.480 there anyones that are kind of highlights to you beside 328 00:19:08.519 --> 00:19:11.799 the oaring API you've done or log Rocket trapic Cote 329 00:19:11.799 --> 00:19:14.240 Camp And how is that kind of benefited maybe your 330 00:19:14.319 --> 00:19:18.559 your career and let you maybe have more exposure and 331 00:19:18.759 --> 00:19:20.559 learning even more than you already. 332 00:19:20.960 --> 00:19:25.000 My favorite article at this point. The one on the 333 00:19:25.000 --> 00:19:28.079 top of my head is one of the first article 334 00:19:28.079 --> 00:19:31.480 I wrote for log Crockets, and it was understanding cues 335 00:19:31.519 --> 00:19:35.759 in no GS. And the inspiration behind the article was 336 00:19:35.960 --> 00:19:39.759 I learned about queues from a tutorial was watching, and 337 00:19:39.799 --> 00:19:42.119 then when I went on line to find out more information, 338 00:19:42.279 --> 00:19:46.319 I discovered that at that point I couldn't find any article. 339 00:19:46.440 --> 00:19:49.799 Even up to the second such result of Google, I 340 00:19:49.799 --> 00:19:54.079 couldn't find any article that was specifically for no gsq's 341 00:19:54.440 --> 00:19:59.720 apart from the one in the note documentation. So I 342 00:19:59.720 --> 00:20:02.839 wrote about it. And when I wrote about it, I 343 00:20:02.880 --> 00:20:05.920 realized that people didn't even know that People didn't even 344 00:20:06.000 --> 00:20:08.960 know that they were accused like this in no GS 345 00:20:09.319 --> 00:20:12.079 and even up to you now, I still get feedbacks 346 00:20:12.079 --> 00:20:14.599 from friends and they're like, Okay, I went on Google 347 00:20:14.720 --> 00:20:17.519 or searching for no gsq's and your article came out first. 348 00:20:18.359 --> 00:20:21.359 So for me, it gave me a lot of understanding. 349 00:20:21.480 --> 00:20:24.680 It made me understand a lot of how NUGS works, 350 00:20:24.720 --> 00:20:29.920 how it handles asynchronous operations, from reading files to making 351 00:20:29.960 --> 00:20:33.279 API requests. It made me understand more like the in 352 00:20:33.359 --> 00:20:36.400 depth of no GS. And also I believe with that 353 00:20:36.519 --> 00:20:39.079 article it has made a lot of people online know 354 00:20:39.160 --> 00:20:41.079 how NUGS works on that wood. 355 00:20:41.440 --> 00:20:43.480 Okay, so I'm totally guilty. I do not know what 356 00:20:43.640 --> 00:20:48.240 no gsqs are and now I'm very curious. So could 357 00:20:48.319 --> 00:20:52.920 you explain what like no jsqs are and like why 358 00:20:53.039 --> 00:20:56.519 your average developer like, like what knowledge that could help 359 00:20:56.599 --> 00:20:57.599 you do well? 360 00:20:57.720 --> 00:21:01.240 Looking at it from the top le, they may really 361 00:21:01.279 --> 00:21:04.960 not help you because when you go to no years, 362 00:21:05.079 --> 00:21:08.000 you just call your APIs, you just radio files. You 363 00:21:08.160 --> 00:21:12.079 just perform every of these as synchronous operations, and you 364 00:21:12.119 --> 00:21:15.480 really don't care how no year has handled them. All 365 00:21:15.519 --> 00:21:20.319 your concern about is no years eventually handles them. But 366 00:21:20.559 --> 00:21:23.799 the article is relevant when you really want to know 367 00:21:24.000 --> 00:21:27.680 how no JS works, and maybe in some cases where 368 00:21:27.720 --> 00:21:32.480 you're trying to understand why this operation was completed before 369 00:21:32.599 --> 00:21:36.519 this other operation, then the article be of good health 370 00:21:36.759 --> 00:21:41.240 because the relevance of cues is no JS expects you 371 00:21:41.279 --> 00:21:44.880 to do a lot of asynchronousity, and the cues is 372 00:21:45.039 --> 00:21:50.519 just its own way of ensuring that there are no conflicts. 373 00:21:50.759 --> 00:21:53.279 It's its own way of ensuring It's just like a 374 00:21:53.359 --> 00:21:58.480 law or a policy that guides how asynchronous operations are 375 00:21:58.480 --> 00:22:01.680 handled in no years, So you really may not need 376 00:22:01.720 --> 00:22:06.720 it for development, but maybe for interviews or maybe just 377 00:22:07.079 --> 00:22:10.200 understanding how Nutchas walk that school be very relevant. 378 00:22:10.480 --> 00:22:12.880 Yeah, I can see that because I've definitely written, like 379 00:22:13.000 --> 00:22:15.480 usually when I touch nodes stuff, it's like quick, one 380 00:22:15.519 --> 00:22:18.799 off scripts to do something, and so there's definitely been 381 00:22:18.839 --> 00:22:21.160 times where it's like I do not know what's happening here, 382 00:22:21.200 --> 00:22:23.279 but like, as long as my script finishes and does 383 00:22:23.319 --> 00:22:25.440 what it needs to do, it's like great, right, But 384 00:22:25.559 --> 00:22:28.799 I could totally see how once like you're writing things 385 00:22:28.799 --> 00:22:31.519 that need to stick around and be like production ready, Like, 386 00:22:32.319 --> 00:22:33.799 I can see why you might need to know that 387 00:22:34.000 --> 00:22:37.279 rather than just hoping for the best. So I'm curious, Actually, 388 00:22:38.240 --> 00:22:41.119 you mentioned that you balk about things that just come 389 00:22:41.160 --> 00:22:42.839 up and you run across. I'm curious what your day 390 00:22:42.920 --> 00:22:45.119 job is, because you seem to run across some absolutely 391 00:22:45.160 --> 00:22:48.599 fascinating set of topics because I've found it very interesting 392 00:22:48.720 --> 00:22:51.839 just seeing the things you've come up with. So I'm curious, 393 00:22:51.880 --> 00:22:54.079 like what your day job is, what sort of things 394 00:22:54.119 --> 00:22:56.240 you work on, because this is pretty interesting stuff. 395 00:22:56.720 --> 00:23:00.640 But well, before I, before I got working at my 396 00:23:00.640 --> 00:23:05.920 current company, I was a freelancer and I didn't really 397 00:23:05.960 --> 00:23:10.920 have many clients, so it's just past now project. So 398 00:23:10.960 --> 00:23:13.960 then I didn't really have much doing. I could just 399 00:23:14.000 --> 00:23:17.000 get an idea and in a week I would make 400 00:23:17.079 --> 00:23:20.880 my research and I would write. Then when I got 401 00:23:20.880 --> 00:23:26.000