WEBVTT 1 00:00:06.440 --> 00:00:10.359 Hey, everyone, Welcome to another episode of React Roundup. I 2 00:00:10.400 --> 00:00:13.279 am your host today, Paige Needringhouse, and I am joined 3 00:00:13.279 --> 00:00:14.359 by our panelist TJ. 4 00:00:14.519 --> 00:00:15.000 Vantold. 5 00:00:15.199 --> 00:00:20.000 Hey everybody, and our special guest today is Akash Joshi. Akash, 6 00:00:20.280 --> 00:00:23.120 can you say hi to the audience and tell us 7 00:00:23.120 --> 00:00:25.760 a little bit about yourself why you're famous? But we're 8 00:00:25.760 --> 00:00:26.719 going to talk about today. 9 00:00:27.160 --> 00:00:31.239 Hey guys, So my name is Akash, and I think 10 00:00:31.600 --> 00:00:35.840 the thing that I might be famous for is talking 11 00:00:35.840 --> 00:00:38.759 a lot about myself and the things that I do online. 12 00:00:39.640 --> 00:00:44.079 And primarily I work as a React developer, and I 13 00:00:44.159 --> 00:00:47.880 try to simplify the complex things that I have learned 14 00:00:48.119 --> 00:00:50.920 and try to share that knowledge through my blog and 15 00:00:51.039 --> 00:00:55.200 through posts on places like record camp and YouTube. And 16 00:00:55.520 --> 00:00:57.640 that's primarily what I try to do. 17 00:00:57.960 --> 00:00:58.679 That's awesome. 18 00:00:58.840 --> 00:01:02.280 So what kind of complex things are you learning about 19 00:01:02.280 --> 00:01:05.079 that you're trying to help others get better at? 20 00:01:05.480 --> 00:01:09.959 So I think React itself might be a complex thing 21 00:01:10.200 --> 00:01:13.840 because we have a lot of web developers here in India. 22 00:01:14.359 --> 00:01:18.280 Most of my friends work in web development, but they 23 00:01:18.319 --> 00:01:21.920 never seem to go beyond just htmls yes, his, JavaScript 24 00:01:21.920 --> 00:01:26.640 and bootstraf and never go into the more productive parts 25 00:01:26.640 --> 00:01:31.400 of web development. Like being able to build applications at 26 00:01:31.400 --> 00:01:35.280 a much faster speed and in a much more scalable 27 00:01:35.319 --> 00:01:39.480 way using technologies like React. So that's where I try 28 00:01:39.519 --> 00:01:42.640 to position my content, and that's what I'm trying to do. 29 00:01:42.959 --> 00:01:44.640 So I'm curious before we get into some of the 30 00:01:44.840 --> 00:01:48.840 topics themselves, what got you into the teaching aspect of this. 31 00:01:49.159 --> 00:01:51.760 Was it doing running problems you ran into the work 32 00:01:51.760 --> 00:01:53.719 that wanted to help into others, or what made you 33 00:01:53.760 --> 00:01:56.920 want to actually blog and talk about some of these things. 34 00:01:57.560 --> 00:02:02.000 So, actually, I've been writing about things that I've learned, 35 00:02:02.159 --> 00:02:06.359 and I guess I mean, you could call it teaguing, 36 00:02:06.400 --> 00:02:10.120 but it was a way of noting down the things 37 00:02:10.120 --> 00:02:13.919 that I have learned myself. I started. I mean, am 38 00:02:14.000 --> 00:02:16.599 I allowed to name brands on here like hacker Noon 39 00:02:16.840 --> 00:02:17.840 and publications like that? 40 00:02:18.199 --> 00:02:18.360 Yeah? 41 00:02:19.680 --> 00:02:23.159 Yeah, So I kind of started by reading hacker Noon 42 00:02:23.400 --> 00:02:26.639 and it was kind of it used to be the 43 00:02:26.719 --> 00:02:28.960 highlight of the day for me looking at posts that 44 00:02:29.080 --> 00:02:31.759 people have written, and I saw that a lot of 45 00:02:31.759 --> 00:02:34.280 them were people my age who were just learning new 46 00:02:34.280 --> 00:02:37.560 things and writing about them. And that's how I myself 47 00:02:37.599 --> 00:02:42.639 got started. I started with learning note js and then 48 00:02:42.719 --> 00:02:46.479 contributing to a few open source repositories on GitHub, and 49 00:02:46.840 --> 00:02:52.919 as I learned new things while learning notejs, like, for example, 50 00:02:53.159 --> 00:02:56.919 how to publish your own NPM library for example, then 51 00:02:56.960 --> 00:03:00.639 I used to write articles on those things, and that's 52 00:03:00.680 --> 00:03:05.039 also what ended up. I mean, that's how I also 53 00:03:05.080 --> 00:03:08.560 got my first job, because people found out about me 54 00:03:08.599 --> 00:03:12.240 through my articles, And yeah, that's kind of how it's 55 00:03:12.280 --> 00:03:13.560 been progressing so far. 56 00:03:14.120 --> 00:03:15.199 That's fantastic. 57 00:03:15.560 --> 00:03:19.319 I've I didn't start writing until after i'd actually gotten 58 00:03:19.360 --> 00:03:21.719 my first job, so it was a little bit backwards 59 00:03:21.759 --> 00:03:24.439 to the way that you went about it. But I've 60 00:03:24.599 --> 00:03:27.719 definitely found that learning things at work and then writing 61 00:03:27.759 --> 00:03:31.199 about them really helps me, helps it solidify in my mind. 62 00:03:31.520 --> 00:03:35.520 And it also helps me when I've forgotten something like 63 00:03:36.080 --> 00:03:38.159 an article I wrote two or three years ago, I 64 00:03:38.159 --> 00:03:40.479 can go back and search through and find how I 65 00:03:40.759 --> 00:03:45.840 did something. So definitely multiple benefits for it. But like, 66 00:03:46.039 --> 00:03:49.800 what do you remember which articles it was that made 67 00:03:49.879 --> 00:03:52.479 your current or your employer reach out to you. 68 00:03:53.120 --> 00:03:58.199 Those were actually articles about to react. So I used 69 00:03:58.280 --> 00:04:03.000 to reach out to publications like CSS tricks on zero, 70 00:04:03.680 --> 00:04:08.280 and I think publications were more open back a few 71 00:04:08.360 --> 00:04:12.759 years ago to new writers and letting them write for 72 00:04:12.800 --> 00:04:16.199 them basically, So that's how I got started with it. 73 00:04:16.279 --> 00:04:20.000 Like through note js, I ended up learning React while 74 00:04:20.079 --> 00:04:23.519 contributing to an open source organization, and then I tried 75 00:04:23.519 --> 00:04:26.120 to translate some of those skills to an article and 76 00:04:26.399 --> 00:04:31.160 trying to explain how to learn React hooks, which were 77 00:04:31.240 --> 00:04:34.560 the big thing back in twenty eighteen, like the end 78 00:04:34.600 --> 00:04:38.240 of twenty eighteen. I think, so, yeah, that's how it 79 00:04:38.279 --> 00:04:39.600 got started. Cool. 80 00:04:39.680 --> 00:04:41.959 Well, I know one of the articles you had written 81 00:04:42.040 --> 00:04:45.480 is about structuring React projects, So I'm curious maybe you 82 00:04:45.480 --> 00:04:49.680 could walk people through roughly what you covering that in 83 00:04:49.959 --> 00:04:53.600 any advice you have to people, Because it's stretching React 84 00:04:53.600 --> 00:04:55.560 projects is not a small topic, right, There's lots of 85 00:04:55.639 --> 00:04:59.600 opinions around that. I'm curious what advice you have there. 86 00:05:00.240 --> 00:05:04.560 Right, definitely, So structuring React projects is one of the 87 00:05:04.639 --> 00:05:08.720 more recent articles that I've written, and I think it 88 00:05:08.839 --> 00:05:12.199 got more eyeballs on it, specially especially because it's such 89 00:05:12.199 --> 00:05:15.879 a polarizing topic. Everyone kind of has their own opinion 90 00:05:15.920 --> 00:05:19.920 on it, and they're willing to read about someone else's 91 00:05:20.000 --> 00:05:25.720 opinion and how I So, how I got started it 92 00:05:25.839 --> 00:05:30.639 with it was basically in my first job, the React 93 00:05:30.959 --> 00:05:33.399 the React projects that I was building weren't that complex, 94 00:05:33.920 --> 00:05:37.120 so I didn't really get a chance to get to 95 00:05:37.160 --> 00:05:39.560 the depths of React. But in my second job, I 96 00:05:39.720 --> 00:05:44.000 had to build uish which had to scale between various 97 00:05:44.000 --> 00:05:48.759 teams and so kind of while building upon the fundamentals 98 00:05:48.800 --> 00:05:52.160 that next JS has set in for the how a 99 00:05:52.240 --> 00:05:55.920 React project should be structured, I kind of added my 100 00:05:56.199 --> 00:06:00.079 own sort of small twists on top of that, and 101 00:06:00.079 --> 00:06:03.759 that's how I landed up at the project structure that 102 00:06:03.839 --> 00:06:09.399 I'm currently using. So should I walk through that what 103 00:06:09.480 --> 00:06:10.600 the project structure is? 104 00:06:11.079 --> 00:06:14.720 Yeah, definitely for anybody who hasn't read the article, which 105 00:06:14.800 --> 00:06:17.519 we will link to in the show notes, but yeah, 106 00:06:17.560 --> 00:06:19.920 it'd be great to hear what your what your take. 107 00:06:19.759 --> 00:06:20.319 On it it is. 108 00:06:20.639 --> 00:06:24.720 Yeah. So one of the first things is that to 109 00:06:25.199 --> 00:06:29.480 not clutter the root folder of the project. It's helpful 110 00:06:29.600 --> 00:06:36.759 to have all of your files separated into a specific 111 00:06:36.800 --> 00:06:41.680 source folder. And then I mostly talk about how various 112 00:06:41.759 --> 00:06:44.480 components of the project should be structured inside of the 113 00:06:44.519 --> 00:06:50.639 source folder. So the primary aspect of any web project 114 00:06:50.920 --> 00:06:56.439 is the routing. So next Days has a good way 115 00:06:56.720 --> 00:07:00.680 of maintaining routes through the pages folder, and I talk 116 00:07:00.720 --> 00:07:04.639 about that how you can create top level routes inside 117 00:07:04.639 --> 00:07:09.759 of these pages, but I don't recommend having any UI 118 00:07:09.920 --> 00:07:14.079 components or the code itself stored inside of these pages, 119 00:07:14.120 --> 00:07:19.759 but having separate component having a separate component folder, and 120 00:07:19.800 --> 00:07:25.519 then naming these folders according to the page or the 121 00:07:25.560 --> 00:07:28.920 set of pages where these components will be used, and 122 00:07:28.959 --> 00:07:34.680 then storing these components inside these name folder structures. And 123 00:07:34.759 --> 00:07:39.199 then I talk about other things like data adaptors and 124 00:07:39.720 --> 00:07:45.800 context stores. So data adaptors would be adaptors like in 125 00:07:45.839 --> 00:07:51.879 the adapter project adaptor pattern of writing code, where these 126 00:07:51.920 --> 00:07:54.839 would just be functions which you would call, and then 127 00:07:54.920 --> 00:07:58.680 the adapter in its own back end would then make 128 00:07:58.879 --> 00:08:02.279 any API call or any ware socket call, or any 129 00:08:02.360 --> 00:08:06.120 anything like that, and then return the data in whatever 130 00:08:06.360 --> 00:08:11.360 format that the original Collie expects. So I also recommend 131 00:08:11.439 --> 00:08:17.319 splitting those splitting the adapters folder into various folders and 132 00:08:17.360 --> 00:08:21.560 files according to the structure of the pages, and context 133 00:08:21.600 --> 00:08:26.199 stores would be Generally, context stores wouldn't be applicable to 134 00:08:26.319 --> 00:08:32.559 simple UH projects, but for more complex projects where generally 135 00:08:32.679 --> 00:08:37.759 people end up using data management library like React, UH, 136 00:08:39.080 --> 00:08:45.440 react context or reducts, then generally UH these context folders 137 00:08:45.480 --> 00:08:52.279 can hold the context stores for these for the set 138 00:08:52.320 --> 00:08:57.240 of pages and yeah, that's what I recommend there, and 139 00:08:57.320 --> 00:09:00.159 the rest of the article then just talks about how 140 00:09:00.279 --> 00:09:03.960 you can store your styles and public assets. 141 00:09:04.320 --> 00:09:06.399 So I'm curious, just because I haven't done much with 142 00:09:06.559 --> 00:09:09.840 next GS, how much does next enforce Because you said 143 00:09:09.879 --> 00:09:13.279 the pages folder is like a built in next GS thing. 144 00:09:13.840 --> 00:09:17.039 Are there other like special folders with that framework or 145 00:09:17.080 --> 00:09:19.799 is some of that just stuff that you made up 146 00:09:19.840 --> 00:09:21.399 for your recommendations. 147 00:09:21.919 --> 00:09:26.960 So there are two things which next Days enforces, which 148 00:09:27.000 --> 00:09:30.440 is having a pages folder for storing your routes and 149 00:09:30.600 --> 00:09:34.559 having a public folder to store all of the static 150 00:09:34.600 --> 00:09:38.639 asset files. And the rest of the things or the 151 00:09:38.639 --> 00:09:41.399 rest of the folders were something that I enforced myself, 152 00:09:42.120 --> 00:09:45.039 that I made up myself. I guess, yeah, gotcha. 153 00:09:45.159 --> 00:09:49.039 So it sounds like you're because usually I find that 154 00:09:49.360 --> 00:09:53.960 most folder structure there's almost like two different paths people take. 155 00:09:54.080 --> 00:09:58.320 Either you group your stuff by your files, by their 156 00:09:59.000 --> 00:10:03.320 type of file, their components, their adapters there, whatever the 157 00:10:03.360 --> 00:10:06.919 case is, or you group by feature, like you have 158 00:10:06.960 --> 00:10:10.960 a folder that this is my I don't know my navigation, 159 00:10:11.120 --> 00:10:14.559 or this is my widget, this is my menu, And 160 00:10:14.639 --> 00:10:18.799 it sounds like you prefer just grouping by feature, right, 161 00:10:18.919 --> 00:10:21.159 like components, adapters, that sort of thing. 162 00:10:21.639 --> 00:10:26.360 Right, So if you consider a set of files like 163 00:10:26.720 --> 00:10:30.759 catering to a particular feature, then yeah, I agree that 164 00:10:30.879 --> 00:10:33.879 it's kind of similar to grouping by a feature. But 165 00:10:34.080 --> 00:10:38.919 I've heard more. I mean, I've heard the counterargument that 166 00:10:39.399 --> 00:10:43.519 my full destructive actually goes counter to having your having 167 00:10:43.600 --> 00:10:47.559 story having to store your files in terms of features. 168 00:10:47.919 --> 00:10:51.840 So I guess it depends on how you see, how 169 00:10:51.879 --> 00:10:52.960 you look at your application. 170 00:10:53.240 --> 00:10:55.559 I guess yeah, And I think there's no like right 171 00:10:55.639 --> 00:10:59.559 or wrong way, because angular is very specific, just to 172 00:10:59.559 --> 00:11:04.840 give one example of they recommend not having folders like 173 00:11:04.879 --> 00:11:08.879 that because they'll tell you to do things like just 174 00:11:08.879 --> 00:11:12.519 just no name by features. But that, like, I don't 175 00:11:12.519 --> 00:11:14.559 think there's a right or wrong answer, because I've seen 176 00:11:14.679 --> 00:11:17.960 both get messy when you start to deal at scale, 177 00:11:18.080 --> 00:11:21.639 because then if you're grouping only by features, then in 178 00:11:21.679 --> 00:11:24.080 a complex app, it's like, well, which features are within 179 00:11:24.159 --> 00:11:26.799 what features? And like sometimes you'll have nested features and 180 00:11:26.799 --> 00:11:29.799 then you'll need to refactor them out of it. And 181 00:11:30.000 --> 00:11:32.960 I don't think there's a clean answer to this. But 182 00:11:33.000 --> 00:11:36.120 I always find it interesting what people come up with 183 00:11:36.200 --> 00:11:39.320 for best practices. I don't know, page would you do 184 00:11:39.360 --> 00:11:42.159 at the home depot if you have a folder structure 185 00:11:42.240 --> 00:11:45.879 that you've magically solved solved this problem with it all. 186 00:11:46.480 --> 00:11:48.840 I don't think that we have that at all. But 187 00:11:49.000 --> 00:11:51.840 the way that my team typically approaches it is we 188 00:11:52.080 --> 00:11:55.679 have a folder that is purely for the API calls 189 00:11:55.720 --> 00:11:59.440 that we call our service layer. We have one four components, 190 00:11:59.480 --> 00:12:03.840 which are the smaller pieces of a React application, like buttons, inputs, 191 00:12:05.279 --> 00:12:09.240 maybe even something as large as a table. And then 192 00:12:09.320 --> 00:12:13.240 we have containers which are kind of the I guess 193 00:12:13.279 --> 00:12:16.960 the pages quote unquote that a next day as project 194 00:12:17.080 --> 00:12:21.840 might contain, So it's things like our whole navbar or 195 00:12:22.519 --> 00:12:26.200 the main contents of a page. And then we have 196 00:12:26.600 --> 00:12:29.720 helper functions that are just used throughout the project, which 197 00:12:29.720 --> 00:12:32.919 are usually kind of plain JavaScript functions that might be 198 00:12:33.000 --> 00:12:36.879 used to format particular data or kind of transform it. 199 00:12:37.519 --> 00:12:40.279 We have hooks, which are the custom hooks that we 200 00:12:40.399 --> 00:12:45.000 use throughout different components in the application. But you know, 201 00:12:45.240 --> 00:12:48.919 it follows the Java pattern a little bit because most 202 00:12:48.919 --> 00:12:51.600 of our back end services are built using Java, and 203 00:12:51.799 --> 00:12:54.600 Java is very prescriptive and how it wants things done, 204 00:12:54.960 --> 00:12:58.440 so we lean on that a bit. But React is 205 00:12:58.480 --> 00:13:02.240 so unopinionated about it, really, however it works for you, 206 00:13:02.600 --> 00:13:05.600 is probably a pretty decent way to kind of filter 207 00:13:05.639 --> 00:13:07.039 your application. 208 00:13:06.639 --> 00:13:10.080 I think, Yeah, gotcha. I think that's why your article 209 00:13:10.120 --> 00:13:13.480 gets so much attention is because no one's really solved 210 00:13:13.480 --> 00:13:17.039 this and people like hearing other's opinions on the issue. 211 00:13:17.399 --> 00:13:20.440 Oh yeah, it's a great opportunity to just see how 212 00:13:20.480 --> 00:13:22.840 other people are approaching it, and maybe you can get 213 00:13:22.840 --> 00:13:24.639 something good out of it that you can take back 214 00:13:24.639 --> 00:13:25.440 to your own app. 215 00:13:25.720 --> 00:13:26.120 Totally. 216 00:13:26.519 --> 00:13:29.440 So, Akash, I was looking at your website, which I've 217 00:13:29.480 --> 00:13:32.879 also linked to, and I noticed that you're not only 218 00:13:32.960 --> 00:13:35.399 working full time. It looks like you've also got a 219 00:13:35.440 --> 00:13:38.000 couple of side projects, and I'd love to hear a 220 00:13:38.039 --> 00:13:40.240 little bit more about them, because you have a link 221 00:13:40.320 --> 00:13:44.159 to this thing called cash parser and also a link 222 00:13:44.200 --> 00:13:46.039 to product hunt, So can you tell us a little 223 00:13:46.039 --> 00:13:47.519 bit about what you're doing there. 224 00:13:47.960 --> 00:13:53.360 Yeah. So, gas Sponsor is a kind of fintech micro 225 00:13:53.440 --> 00:13:57.039 startup that I am running with a friend of mine. 226 00:13:57.320 --> 00:14:02.440 So he it's basically his being and I provide all 227 00:14:02.480 --> 00:14:05.279 of the front end help that he needs in going 228 00:14:05.320 --> 00:14:12.080 through that. So cast statements are basically consolidated account statements 229 00:14:12.080 --> 00:14:16.519 that get generated for all of the mutual funds that 230 00:14:16.639 --> 00:14:21.039 a person holds. So mutual funds are basically a set 231 00:14:21.080 --> 00:14:25.159 of stocks that people can buy, and a set of 232 00:14:25.200 --> 00:14:28.799 these mutual funds is stored in that cast statement, and 233 00:14:28.840 --> 00:14:33.320 we allow passing of that statement and generating the data 234 00:14:33.399 --> 00:14:37.919 in whatever format that the user needs. So that's where 235 00:14:38.480 --> 00:14:42.600 that's what cash pars is about. And on product hunt, 236 00:14:42.679 --> 00:14:46.639 I generally try to post about some fun side projects 237 00:14:46.679 --> 00:14:49.759 that I have I might have built. Like for example, 238 00:14:49.799 --> 00:14:53.360 I used to have a telegram bot which used to 239 00:14:54.240 --> 00:14:58.879 give notifications whenever a website changed. So I used to 240 00:14:59.159 --> 00:15:03.639 use this spot to track the results page for my university, 241 00:15:04.559 --> 00:15:07.879 and some other people did some other fun projects with it, 242 00:15:08.039 --> 00:15:12.480 like tracking the careers page of a place ef work 243 00:15:12.559 --> 00:15:14.759 that they wanted to work at or something like that, 244 00:15:15.159 --> 00:15:19.039 and so I had to take that brought down because 245 00:15:19.039 --> 00:15:22.240 it was too resource intensive. But I have made its 246 00:15:22.279 --> 00:15:29.279 API open and basically the other projects small small projects 247 00:15:29.320 --> 00:15:32.320 like this that I have found useful for myself, and 248 00:15:32.360 --> 00:15:34.440 then I try to put them on product and to 249 00:15:35.200 --> 00:15:37.279 try to get some other users for it. 250 00:15:38.360 --> 00:15:41.039 Yeah, that's very nice of you to share that kind 251 00:15:41.080 --> 00:15:43.919 of software because that sounds really useful for different. 252 00:15:43.720 --> 00:15:46.840 Things with sites here, where you would you just paying 253 00:15:47.279 --> 00:15:52.240 like a configurable amount like paying a site store. What 254 00:15:52.440 --> 00:15:55.879 was there and like if if it notices like any changes, 255 00:15:56.000 --> 00:15:57.399 then sends a message. 256 00:15:57.960 --> 00:16:00.919 Yeah, yeah, that's exactly what it used to do. 257 00:16:01.440 --> 00:16:02.080 Very cool. 258 00:16:02.879 --> 00:16:06.559 So are you continuing to work on side projects like 259 00:16:06.600 --> 00:16:10.000 this or is there anything else that you're doing, like 260 00:16:10.200 --> 00:16:14.200 I don't know, writing courses or kind of blogging more. 261 00:16:14.360 --> 00:16:17.639 What are you like, what are you most focused. 262 00:16:17.320 --> 00:16:21.200 On right now? Yeah? I think I'm too young to 263 00:16:21.200 --> 00:16:25.080 write a course or you know, ask payment for someone 264 00:16:25.159 --> 00:16:28.720 to teach them something, while there are like more smarter 265 00:16:28.879 --> 00:16:33.679 people who can who freely provide content for things that 266 00:16:33.720 --> 00:16:37.960 people want to learn about. So that's what I also 267 00:16:38.000 --> 00:16:41.759 tried to do earlier. I used to make side projects 268 00:16:41.799 --> 00:16:45.000 for fun, and later on it became that I wanted 269 00:16:45.080 --> 00:16:47.600 to try to monitor some of the work that I 270 00:16:47.639 --> 00:16:50.919 had done earlier and try to build on that. But then, 271 00:16:51.320 --> 00:16:54.399 I mean, when you're trying to monetize something, things start 272 00:16:54.559 --> 00:16:56.919 to become less fun because you have to worry about 273 00:16:56.960 --> 00:17:01.000 things like marketing. There might be search engine optimize, building 274 00:17:01.080 --> 00:17:05.519 landing pages, stuff like that. So then I kind of 275 00:17:06.279 --> 00:17:10.079 slowed that down a little bit, and now I'm creating content. 276 00:17:10.880 --> 00:17:14.319 Content that is that would be fun for me to make, 277 00:17:14.559 --> 00:17:17.480 if it makes sense. So when I feel like it, 278 00:17:17.559 --> 00:17:19.559 I write a blog. When I feel like it, I 279 00:17:19.599 --> 00:17:22.960 try to record a YouTube video. Now, editing a YouTube 280 00:17:23.079 --> 00:17:27.319 video is not fun. Recording can be fun. 281 00:17:27.400 --> 00:17:30.920 Sometimes I can totally relate to that. 282 00:17:30.920 --> 00:17:32.119 That's what I do. 283 00:17:33.839 --> 00:17:34.119 Nice. 284 00:17:34.200 --> 00:17:37.519 I can definitely relate to that, not the whole monetizing thing. 285 00:17:37.599 --> 00:17:40.240 But the second something goes from being just kind of 286 00:17:40.279 --> 00:17:42.720 like a hobby project too, and I must do this 287 00:17:42.839 --> 00:17:46.039 or get this to work, it's it's usually a lot 288 00:17:46.119 --> 00:17:47.400 less fun that way. 289 00:17:47.880 --> 00:17:51.480 Yeah, having lots of users is like a double edged sword. 290 00:17:52.119 --> 00:17:56.160 It's cool. But at the same time, then people have demands, 291 00:17:56.240 --> 00:17:58.279 especially if they're paying money then they have they have 292 00:17:58.319 --> 00:18:00.319 a lot more demands and. 293 00:18:00.359 --> 00:18:04.920 A lot more sway over what you'll actually do for them. Yeah, yeah, 294 00:18:04.960 --> 00:18:08.440 well that's cool. So what kind of day to day 295 00:18:09.039 --> 00:18:11.119 things do you get to use for your work with 296 00:18:11.200 --> 00:18:14.279 your company that you work for, Like what kind of 297 00:18:14.319 --> 00:18:15.640 tech stack and tools? 298 00:18:16.079 --> 00:18:19.400 So it might sound boring to some people that I 299 00:18:19.480 --> 00:18:22.400 get to work with React a lot, but it's actually 300 00:18:22.599 --> 00:18:27.720 really fun for me because JavaScript is how I got started, 301 00:18:28.559 --> 00:18:32.960 and React for me is the best expression of JavaScript 302 00:18:33.640 --> 00:18:38.440 and especially via typescript, where I can kind of automat 303 00:18:38.480 --> 00:18:42.559 aly most of my workflow. And then it's fun to 304 00:18:42.720 --> 00:18:46.079 think about how I can build something with the minimum 305 00:18:46.119 --> 00:18:50.880 amount of lines of code by trying to create the 306 00:18:50.920 --> 00:18:56.400 optimum function which can be reused everywhere, or basically reduce 307 00:18:56.440 --> 00:18:58.319 the amount of work that I would have to do 308 00:18:58.359 --> 00:19:02.519 to build something. So yeah, mostly I do get to 309 00:19:02.559 --> 00:19:07.599 work with reacting typeescript, and I hope to learn rest soon. 310 00:19:08.279 --> 00:19:10.960 I've heard a lot of people who seem to be 311 00:19:11.079 --> 00:19:16.039 jobs script developers kind of gravitating towards Rust. What's kind 312 00:19:16.039 --> 00:19:17.160 of drawing you towards it? 313 00:19:17.720 --> 00:19:25.440 So I especially like the functional programming paradigms inside of JavaScript, 314 00:19:25.559 --> 00:19:28.240 and I try to use them as much as possible. 315 00:19:29.000 --> 00:19:32.960 So when I look at last, I like most university 316 00:19:33.000 --> 00:19:37.279 students have of course learned CNC plus plus and nobody 317 00:19:38.000 --> 00:19:41.480 like after playing with modern programming languages, going back to 318 00:19:41.519 --> 00:19:46.200 that is not fun. But Rust is something different because it, 319 00:19:46.839 --> 00:19:52.200 even though it has some complex programming paradigms like it 320 00:19:52.799 --> 00:19:58.480 quite strictly defines the life cycles of a variable and 321 00:19:58.640 --> 00:20:02.240 you have to deal with things like borrowing memory values 322 00:20:02.279 --> 00:20:07.359 between variables. It's still fun because the kind of strictness 323 00:20:07.440 --> 00:20:12.200 that it applies is eventually what results in better, better 324 00:20:12.240 --> 00:20:15.480 code being written. But of course I don't speak this 325 00:20:15.519 --> 00:20:18.079 from my experience. This is just from things I've read 326 00:20:18.079 --> 00:20:24.279 on link. But more experienced Trust developer would probably be 327 00:20:24.359 --> 00:20:26.240 able to give this answer better. But yeah, that was 328 00:20:26.279 --> 00:20:27.079 my opinion on this. 329 00:20:27.440 --> 00:20:28.160 It's funny page. 330 00:20:28.200 --> 00:20:30.720 You're right, I feel like Rust is the cool thing 331 00:20:30.799 --> 00:20:34.039 for JavaScript developers to do. I feel like we missed 332 00:20:34.079 --> 00:20:37.039 the memo here at some point because I haven't gotten 333 00:20:37.039 --> 00:20:39.839 into Rust at all. But I also think like it's 334 00:20:39.839 --> 00:20:43.839 funny that a lot of JavaScript tooling is now starting. 335 00:20:43.960 --> 00:20:47.920 There's like some Rust based tools that are supposedly faster 336 00:20:48.200 --> 00:20:50.960 that are starting to become more popular. So it's going 337 00:20:51.000 --> 00:20:53.559 to be interesting to see how that changes over time. 338 00:20:53.759 --> 00:20:54.880 Maybe I'll have to learn it too. 339 00:20:55.599 --> 00:20:59.759 I now I hear this kind of stuff pretty regularly, 340 00:21:00.160 --> 00:21:04.319 like Rust Go. But I guess my problem is a 341 00:21:04.359 --> 00:21:09.079 time management one where I use Java and I use 342 00:21:09.680 --> 00:21:13.680 React mostly for my job, and so that's what most 343 00:21:13.720 --> 00:21:17.400 of my time goes towards, is those two programming languages. 344 00:21:18.480 --> 00:21:21.440 I've used Python a little bit. I'd like to learn Go, 345 00:21:21.559 --> 00:21:23.920 I think, because I've heard really good things about it. 346 00:21:24.000 --> 00:21:25.119 But it's there's just so. 347 00:21:25.079 --> 00:21:28.160 Many languages and so little time to learn them and 348 00:21:28.160 --> 00:21:30.160 then apply them, I guess, is the main thing. 349 00:21:30.759 --> 00:21:32.799 Yeah, And I think like, at least for me, I 350 00:21:32.880 --> 00:21:35.920 have to have a reason to do it, right, like 351 00:21:35.960 --> 00:21:38.680 if I have a project in mind, and Akash, like, 352 00:21:38.720 --> 00:21:42.480 it's interesting hearing some of your stories too, because you're 353 00:21:42.880 --> 00:21:44.599 like a lot of these side projects came out of 354 00:21:44.960 --> 00:21:48.599 actual problems you had or things that you wanted to do, 355 00:21:48.720 --> 00:21:51.759 which is always interesting to see because at least for me, 356 00:21:52.000 --> 00:21:53.480 and I don't know about you too, but I can't 357 00:21:53.519 --> 00:21:55.160 just sit down and say, like, well, I'm going to 358 00:21:55.200 --> 00:21:58.480 learn erlink today, right, Like if I do that, like 359 00:21:58.519 --> 00:22:00.799 there's no amount of focus the world that's going to 360 00:22:00.839 --> 00:22:03.960 get me to learn earlang. But if I had like 361 00:22:04.599 --> 00:22:06.680 some problem that I needed to solve in my life 362 00:22:06.759 --> 00:22:08.640 or for my job, and like, okay, sure, like that 363 00:22:08.720 --> 00:22:10.799 gives my brain a reason to sit down and focus 364 00:22:10.839 --> 00:22:11.279 and do it. 365 00:22:11.799 --> 00:22:12.519 Absolutely. 366 00:22:12.720 --> 00:22:16.200 I tried that with Haskell one time because a programmer 367 00:22:16.480 --> 00:22:19.039 who I work with had a senior developer he had 368 00:22:19.079 --> 00:22:20.880 recommended it as a good way to kind of get 369 00:22:20.880 --> 00:22:24.359 your feet wet with functional programming. And I made it 370 00:22:24.400 --> 00:22:28.119 through I don't know, maybe three two or three chapters 371 00:22:28.200 --> 00:22:31.640 of getting started with Haskell book and then just put 372 00:22:31.680 --> 00:22:33.400 it down and never picked it back up again. 373 00:22:33.599 --> 00:22:35.680 So yeah, you definitely have to have. 374 00:22:35.720 --> 00:22:38.599 Something that you're trying to solve, not just trying to 375 00:22:38.680 --> 00:22:40.559 learn for the fun of I think. 376 00:22:41.039 --> 00:22:44.519 Actually, Akasha, I'm curious because you said that you had 377 00:22:44.599 --> 00:22:47.720 kind of liked the functional style of programming, and I'm curious, 378 00:22:48.200 --> 00:22:51.160 is that come from like work experience or school, because 379 00:22:51.319 --> 00:22:54.880 I say this as someone that functional is never totally 380 00:22:54.880 --> 00:22:57.160 clicked from me, and maybe like because like page, I 381 00:22:57.200 --> 00:23:00.319 came from a Java background, and Java is very much 382 00:23:00.440 --> 00:23:02.839 not I mean, there's you can kind of do some 383 00:23:02.880 --> 00:23:05.799 functional things, but it's very much not a functional language really, 384 00:23:05.880 --> 00:23:08.880 so I struggled to get my brain to work that way. 385 00:23:08.880 --> 00:23:12.079 So I'm curious why, like, what made you interested in 386 00:23:12.079 --> 00:23:12.720 that approach. 387 00:23:13.200 --> 00:23:18.319 Yeah. So I didn't pick up functional programming in university 388 00:23:18.559 --> 00:23:23.519 because most of the university classes are based on objectory interprogramming. 389 00:23:24.160 --> 00:23:29.279 But where I initially started picking up functional programming was 390 00:23:29.640 --> 00:23:34.319 again when I was reading Hacker Moon back then, and 391 00:23:34.440 --> 00:23:38.079 there were a lot of articles written about things like 392 00:23:38.559 --> 00:23:42.359 I guess monads, which nobody really understands. But then there 393 00:23:42.359 --> 00:23:49.279 were things about like topics like composibility of functions and immutability. 394 00:23:49.680 --> 00:23:54.079 So immutability and pure functions. Those are the two things 395 00:23:54.079 --> 00:23:57.519 which really got me into functional programming because then I 396 00:23:57.559 --> 00:24:04.240 could write code, which wasn't surprising kind of so in 397 00:24:04.480 --> 00:24:08.240 seeing you end up writing code which you don't understand 398 00:24:08.400 --> 00:24:11.359 what it does, like at least I used to, because 399 00:24:11.759 --> 00:24:16.880 I couldn't try see well, I guess. But with functional programming, 400 00:24:16.960 --> 00:24:21.160 I could write JavaScript, which even if I come back 401 00:24:21.160 --> 00:24:24.720