WEBVTT 1 00:00:05.240 --> 00:00:08.439 Hey, Welcome to React Round Up, the podcast where we 2 00:00:08.519 --> 00:00:11.919 keep you updated on all things React related. This show 3 00:00:12.039 --> 00:00:15.400 is sponsored by Raygun and produced by Top and Daves 4 00:00:15.480 --> 00:00:16.120 and onboard. 5 00:00:16.640 --> 00:00:18.600 Top and Doves is where we creat Top and Doves so. 6 00:00:18.640 --> 00:00:21.440 Get top and pay and recognition while working on interesting 7 00:00:21.480 --> 00:00:26.120 problems and making meaningful community contributions. And Onvoid provides remote 8 00:00:26.160 --> 00:00:31.079 design and software development services on the most client friendly 9 00:00:31.160 --> 00:00:34.960 business model. Clients only pay after the tasks are delivered 10 00:00:35.159 --> 00:00:39.200 and update. In today's episode, we will talk a lot 11 00:00:39.240 --> 00:00:43.039 about next JS, and we will also talk about some 12 00:00:43.200 --> 00:00:48.479 career advice for people wanting to start or already starting 13 00:00:48.520 --> 00:00:52.079 but getting the hangout software development later in their careers. 14 00:00:52.600 --> 00:00:55.240 My name is Lucas Paganinia. I'm your host in the podcast. 15 00:00:55.439 --> 00:00:59.520 Joining today's episode is also the hosts Chris. 16 00:00:59.359 --> 00:01:04.239 Ruin, Hello everybody, Peter Orsan. 17 00:01:04.879 --> 00:01:09.719 Hi Eboom, and our very special guest that I just 18 00:01:09.760 --> 00:01:13.400 spent the last ten minutes figuring out how to correctly 19 00:01:13.439 --> 00:01:17.959 pronunciate his full name, Paul rat Slovsky. He is a 20 00:01:18.000 --> 00:01:23.159 software engineer at Strappie and he is also a content creator. 21 00:01:23.400 --> 00:01:27.400 He creates content for people that are trying to switch 22 00:01:27.760 --> 00:01:31.280 into other careers through have development later in life. And 23 00:01:31.319 --> 00:01:33.959 he is also a co host at the not Dule 24 00:01:34.040 --> 00:01:39.760 podcast and he's also done a course on XJS. So, Paul, 25 00:01:40.200 --> 00:01:42.200 thank you so much for being here with us. 26 00:01:42.719 --> 00:01:44.000 No, thank you for having me. 27 00:01:44.040 --> 00:01:46.519 I'm super excited to chat about all the cool things 28 00:01:46.560 --> 00:01:48.480 that we have planted today. So thank you very much 29 00:01:48.480 --> 00:01:49.000 for having me. 30 00:01:49.799 --> 00:01:55.079 Awesome. Awesome. So before we get started, let's. 31 00:01:55.000 --> 00:01:58.760 Just go through some quick definitions. So I said that 32 00:01:58.840 --> 00:02:03.239 you're working at and that is relevant to the course 33 00:02:03.280 --> 00:02:06.519 that you publish on XGS because it was also published 34 00:02:07.280 --> 00:02:10.560 in the YouTube's channel of Strappy, which, by the way, 35 00:02:10.800 --> 00:02:13.479 that's a huge note for everyone listening to this. You 36 00:02:13.520 --> 00:02:16.199 can just go to YouTube and watch the course like 37 00:02:16.319 --> 00:02:22.199 it's all there. And I think we could start by 38 00:02:22.280 --> 00:02:29.159 defining what is strappy and also what is the value 39 00:02:29.199 --> 00:02:33.240 proposition the premise of your course on XGS, because there's 40 00:02:33.240 --> 00:02:36.319 already so much content out there about XGS, so why. 41 00:02:36.120 --> 00:02:40.360 Should people go through the course that you did? 42 00:02:40.960 --> 00:02:44.960 Yeah, No, definitely. So Strappy is a headless CMS. It's 43 00:02:45.000 --> 00:02:47.319 all javscript based, which is awesome. So if you're doing 44 00:02:47.360 --> 00:02:50.360 front end with next, which is also jovscript, makes things easier, 45 00:02:50.439 --> 00:02:53.800 you stay in one language, and the biggest thing for 46 00:02:53.879 --> 00:02:55.680 Strappy is if you're going to have a lot of 47 00:02:55.680 --> 00:02:59.159 content and you need non technical people to manage it, 48 00:02:59.479 --> 00:03:01.639 Strappy allows you to do that out of the box. 49 00:03:01.800 --> 00:03:05.840 There's other features as well, but mainly for content management 50 00:03:06.280 --> 00:03:09.080 for non developers. But you as a developer, you do 51 00:03:09.240 --> 00:03:11.719 have access to that data via the API, so you 52 00:03:11.759 --> 00:03:16.759 could do full CRAWD functionality, create authorization, authentication, you could. 53 00:03:16.879 --> 00:03:19.879 And because it's strapp is highly customizable, like if you 54 00:03:19.960 --> 00:03:23.000 need to add new features too, Strappy you could actually 55 00:03:23.000 --> 00:03:26.360 create your own plug in. And what's awesome because it's 56 00:03:26.400 --> 00:03:29.520 all based on no JS. If you need add additional 57 00:03:29.560 --> 00:03:32.599 like controller services, middleware, some functions, you're able to do that, 58 00:03:32.639 --> 00:03:34.479 but you don't need to. You could actually get started 59 00:03:34.520 --> 00:03:36.039 right out of the box. It takes two minutes to 60 00:03:36.080 --> 00:03:38.360 set up, and you have a working API where a 61 00:03:38.520 --> 00:03:41.599 non developer could manage data. And what I like about 62 00:03:41.639 --> 00:03:44.159 that as a developer, Like I've used to work on 63 00:03:44.199 --> 00:03:46.520 like smaller websites when it's starting out where a lot 64 00:03:46.560 --> 00:03:48.560 of stuff is hardcoded, and then you'll get a call 65 00:03:48.599 --> 00:03:50.879 like hey, can you go and change this data in 66 00:03:50.919 --> 00:03:52.879 my website for me? I'm like, I don't want to 67 00:03:52.879 --> 00:03:54.439 do this as a developer, It's like, I mean, I 68 00:03:54.439 --> 00:03:56.639 don't mind it, but like and so to me, this 69 00:03:56.719 --> 00:04:00.439 idea of having a place for non technically users to 70 00:04:00.479 --> 00:04:02.680 manage their own content themselves and for me as a 71 00:04:02.680 --> 00:04:05.719 developer not have to worry, that's amazing. And the biggest 72 00:04:05.719 --> 00:04:10.240 thing for me is I switch careers into development late 73 00:04:10.280 --> 00:04:14.000 in life and I always like thought of software engineering 74 00:04:14.159 --> 00:04:16.680 is you have a business that has a problem or 75 00:04:16.680 --> 00:04:18.319 they want to create a product. And so to me, 76 00:04:18.360 --> 00:04:20.560 I always thought about what is the fastest way to 77 00:04:20.600 --> 00:04:22.439 get to the product, Like I don't want to spend 78 00:04:22.759 --> 00:04:24.000 months or years in development. 79 00:04:24.120 --> 00:04:25.439 I'm not saying there's anything. 80 00:04:25.160 --> 00:04:27.759 Wrong, but I always thought of like how could I 81 00:04:27.920 --> 00:04:30.560 help this business to solve the problem. And so for me, 82 00:04:31.240 --> 00:04:35.360 like leveraging next CS, leveraging aheadless cms, like strappy, I 83 00:04:35.360 --> 00:04:37.879 feel like you say ten thousand hours of development and 84 00:04:37.920 --> 00:04:40.680 it's like an easy way to get started. So like 85 00:04:41.000 --> 00:04:44.600 when I first got my first dev job, I work 86 00:04:44.639 --> 00:04:46.720 at a company where I learned a lot of things that. 87 00:04:46.720 --> 00:04:47.519 Are not to do. 88 00:04:47.800 --> 00:04:51.120 And what I saw a company that tried to do 89 00:04:51.160 --> 00:04:54.480 everything in house, you know, their own back end, their 90 00:04:54.519 --> 00:04:56.959 own like design system, then, and the team was only 91 00:04:57.040 --> 00:05:00.319 like five people, and they spend years of bild this 92 00:05:00.399 --> 00:05:03.240 product and they never delivered it to clients, and I 93 00:05:03.279 --> 00:05:05.519 was actually wondering, like, how does this company even like 94 00:05:05.800 --> 00:05:09.319 generating income? And so to me, I really like things 95 00:05:09.360 --> 00:05:11.879 that help you build things quickly to get them out 96 00:05:11.920 --> 00:05:13.399 to the clients as fast as possible. 97 00:05:13.680 --> 00:05:15.360 Gotcha makes sense? Makes sense? 98 00:05:15.519 --> 00:05:20.519 So this seems like a very unique CMS because when 99 00:05:20.519 --> 00:05:23.199 I think of CMS, I just think of something where 100 00:05:23.199 --> 00:05:26.920 I can host blog posts and update the content from there. 101 00:05:26.920 --> 00:05:31.360 But that sounds way more flexible and honestly just modern. 102 00:05:31.439 --> 00:05:34.560 I was going through the website as well, and just 103 00:05:34.639 --> 00:05:38.000 by you saying that it's fully customizable and done in node, 104 00:05:38.600 --> 00:05:41.560 that just made it sound very interesting. So I would 105 00:05:41.600 --> 00:05:46.279 definitely check it out on any project that is requiring 106 00:05:46.319 --> 00:05:52.279 a CMS. There are some very interesting products that were 107 00:05:52.319 --> 00:05:55.800 arising around the CMS space a few months ago, and 108 00:05:56.399 --> 00:06:00.199 currently it feels like maybe it's just my set out 109 00:06:00.240 --> 00:06:02.720 and the bubble that I am in, but I haven't 110 00:06:02.800 --> 00:06:09.199 received any hot topics about just companies launching UCMs. 111 00:06:08.720 --> 00:06:09.560 Is and stuff like that. 112 00:06:09.600 --> 00:06:12.160 But I remember that a few months ago there were 113 00:06:12.199 --> 00:06:16.040 a lot of interesting cms is popping up I also 114 00:06:16.079 --> 00:06:18.920 thought it was really interesting that strappi has not just 115 00:06:19.000 --> 00:06:21.000 a rest API but also a graph q il a 116 00:06:21.079 --> 00:06:26.199 p I, so that definitely makes it very interesting for 117 00:06:26.279 --> 00:06:29.160 people that are looking to work with those two different 118 00:06:30.319 --> 00:06:32.240 API data formats. 119 00:06:32.360 --> 00:06:34.759 So yeah, pretty cool, Pretty cool. 120 00:06:35.680 --> 00:06:43.319 Now specifically about next JS, is it what's the connection 121 00:06:43.480 --> 00:06:47.319 between strappy and next JS or is there not? Is 122 00:06:47.439 --> 00:06:49.720 just like Strappy is a headless CMS and you could 123 00:06:49.720 --> 00:06:52.879 be using anything and you just happened to want to 124 00:06:52.920 --> 00:06:54.360 create content about next. 125 00:06:54.480 --> 00:06:56.959 So very good, like interesting and good question by the way, 126 00:06:57.240 --> 00:07:00.519 So all that I so next I I'll be honest 127 00:07:00.519 --> 00:07:03.560 with you. I didn't use next gs like up to twelve. 128 00:07:03.639 --> 00:07:04.959 I tried a few times. I was like, you know what, 129 00:07:04.959 --> 00:07:07.279 there's like other things that I just you know, use 130 00:07:07.360 --> 00:07:09.279 that are nice to me. But when I saw the 131 00:07:09.319 --> 00:07:11.759 differences they made, like next thirteen, Next fourteen and where 132 00:07:11.800 --> 00:07:15.800 next GS was going to me, that was amazing. Like 133 00:07:15.839 --> 00:07:18.439 from you know, the introduction of like reaction or component, 134 00:07:18.519 --> 00:07:22.560 like you know, the new app router, like you could 135 00:07:22.759 --> 00:07:25.480 create route handlers or you could create actions like to me, 136 00:07:25.879 --> 00:07:29.399 that just opened up this whole way of building things quickly. 137 00:07:29.439 --> 00:07:32.399 And that's the part that I like and you know, 138 00:07:32.480 --> 00:07:35.199 when I was thinking of like a course to build, 139 00:07:35.480 --> 00:07:37.680 and after exploring next GS, and it started from the 140 00:07:37.680 --> 00:07:40.279 standpoint like I kind of like it, and now I'm like, god, 141 00:07:40.800 --> 00:07:43.480 damn it, they got me, and it's like really really good. 142 00:07:43.560 --> 00:07:47.560 And so for me, it's again, how could I build 143 00:07:47.560 --> 00:07:49.920 something quickly with the tools that are available and through 144 00:07:49.959 --> 00:07:52.879 their app router like you know, folder allows you to 145 00:07:52.920 --> 00:07:56.920 easily you know, structure your routes. You could do nested 146 00:07:57.000 --> 00:08:00.360 routing like like easy. The fact that now you could 147 00:08:00.480 --> 00:08:05.079 use reacts over components to load your data specifically to 148 00:08:05.160 --> 00:08:07.800 that component and then wherever you move that component, because 149 00:08:07.839 --> 00:08:10.639 that data loading is inside that component, it's still going 150 00:08:10.720 --> 00:08:13.439 to work. And to me, there's a lot less things 151 00:08:13.480 --> 00:08:15.120 that I had to think about it. And to be honest, 152 00:08:15.160 --> 00:08:19.079 when I was starting out, like as a newer developer 153 00:08:19.120 --> 00:08:21.800 exploring all the like thirteen to fourteen features, I was like, oh, 154 00:08:21.839 --> 00:08:23.759 this is stupid, Like I don't understand it. But once 155 00:08:23.800 --> 00:08:26.639 you understand like the tools that they give you, you 156 00:08:26.759 --> 00:08:29.439 realize that they really thought, like you know, we're sell 157 00:08:29.480 --> 00:08:32.000 team and XGS, like they really thought about, you know, 158 00:08:32.039 --> 00:08:34.519 what they want to accomplish and where they're going and 159 00:08:35.559 --> 00:08:39.320 I find myself like really enjoying the developer experience process. 160 00:08:39.399 --> 00:08:42.559 And also they're growing in popularity. That means that I mean, 161 00:08:42.559 --> 00:08:45.480 they're huge. That means that other people enjoy working on 162 00:08:45.639 --> 00:08:48.240 xts and you know, and so I was like, you 163 00:08:48.279 --> 00:08:50.240 know what, this is something that I want to learn 164 00:08:50.279 --> 00:08:53.000 more about because I'm not an expert. I think this 165 00:08:53.039 --> 00:08:55.759 will be a good opportunity to do something that other 166 00:08:55.799 --> 00:08:56.879 people are really enjoying. 167 00:08:57.000 --> 00:08:57.799 And I want to. 168 00:08:57.759 --> 00:08:59.840 See like what a cool like way that we could 169 00:08:59.840 --> 00:09:02.720 come buying it with a headless CMS. And what's interesting 170 00:09:02.720 --> 00:09:04.159 Like a lot of times when people think about had 171 00:09:04.200 --> 00:09:07.000 less MS, they think of like it's a blog post 172 00:09:07.080 --> 00:09:10.200 or I'm managing content, which is perfectly fine. But the 173 00:09:10.200 --> 00:09:13.919 path that I took for this particular project, we used 174 00:09:13.919 --> 00:09:18.000 to you know, strappy to power like an app because it's. 175 00:09:17.879 --> 00:09:19.240 Not just like a blog platform. 176 00:09:19.279 --> 00:09:21.480 So the functionality that you have, you have your landing page, 177 00:09:21.480 --> 00:09:23.080 of course you could go and see, but once you 178 00:09:23.200 --> 00:09:26.639 likeg in, you have the ability to generate summaries of 179 00:09:26.720 --> 00:09:28.240 YouTube videos. So you put a link of a YouTube 180 00:09:28.279 --> 00:09:30.240 video you hit generated, it's going to generate your summary, 181 00:09:30.480 --> 00:09:34.200 and you have like basic authentication. So if you're authenticate 182 00:09:34.240 --> 00:09:36.000 into account, you're only going to see your videos. 183 00:09:36.080 --> 00:09:37.519 You're not going to see somebody else's video. 184 00:09:37.600 --> 00:09:41.120 So we implemented, you know, the full crowd functionality, including 185 00:09:41.240 --> 00:09:43.120 like you know, uploading. 186 00:09:42.679 --> 00:09:44.279 Images and files and stuff like that. 187 00:09:44.320 --> 00:09:46.799 And so to me, I kind of did like if 188 00:09:46.799 --> 00:09:48.639 someone were to build an app, like what features do 189 00:09:48.720 --> 00:09:51.799 they need? And I was like, you know, really happy 190 00:09:51.840 --> 00:09:55.360 that you know, strappy, like it allows you to do that, 191 00:09:55.360 --> 00:09:57.720 it doesn't get into your way and one of the 192 00:09:57.720 --> 00:10:01.559 things that like, so I love next year ass. 193 00:10:01.600 --> 00:10:02.919 I'd like other frameworks as well. 194 00:10:02.919 --> 00:10:06.519 Like I basically like anything that my you know, customer 195 00:10:06.799 --> 00:10:08.759 or boss will tell me to use, I'll use it. 196 00:10:09.120 --> 00:10:10.679 So that's like how I judge things. 197 00:10:10.679 --> 00:10:13.960 But with next ye asks, what I saw a lot 198 00:10:13.960 --> 00:10:16.720 of people do is that they're like, you know, we 199 00:10:16.799 --> 00:10:19.559 need to start a project, Let's use Drizzle or Prisma, 200 00:10:19.679 --> 00:10:22.240 let's manage our own database, let's do all this stuff. 201 00:10:22.240 --> 00:10:24.320 And I'm like, I know it's great and it's cool 202 00:10:24.360 --> 00:10:27.279 and I love it, but what if one day, like 203 00:10:27.480 --> 00:10:31.039 you need to show push that content somewhere else, maybe 204 00:10:31.080 --> 00:10:33.879 on iPhone, maybe maybe your refrigerator has a screen and 205 00:10:33.879 --> 00:10:36.399 he needs to showcase some content, and so I realized, 206 00:10:36.440 --> 00:10:39.440 like building everything and it's not a bad approach, but 207 00:10:39.480 --> 00:10:42.279 building everything just in next she ass as like your 208 00:10:42.320 --> 00:10:43.080 full stack framework. 209 00:10:43.120 --> 00:10:45.399 You can do it. It's amazing. But what I like 210 00:10:45.559 --> 00:10:46.120 is I like. 211 00:10:46.240 --> 00:10:50.639 Decoupling my content delivery platform from the front end. And 212 00:10:50.720 --> 00:10:53.120 so when I work with next year jass and I 213 00:10:53.240 --> 00:10:55.320 just recently realized there's a term for it. 214 00:10:55.320 --> 00:10:57.720 It's called like back then for your front end. 215 00:10:57.720 --> 00:10:59.960 Basically, even though you next year as is your full 216 00:11:00.080 --> 00:11:02.360 that framework, you're still using it as a way to 217 00:11:02.519 --> 00:11:05.759 present your data, but you're like API lived somewhere else 218 00:11:06.360 --> 00:11:09.639 in that case, like Strappy, And for me, I love 219 00:11:09.679 --> 00:11:12.960 the flexibility that now I could have my next chess 220 00:11:13.039 --> 00:11:16.080 project that's consuming my Strappy data. But if I want 221 00:11:16.120 --> 00:11:18.960 to have another source, like an iPhone that has a 222 00:11:18.960 --> 00:11:22.200 different app but similar to the content that we need, 223 00:11:22.960 --> 00:11:25.840 we could hit that same Strappy airdpoint with that mobile app. 224 00:11:25.960 --> 00:11:27.000 Or if again I want to. 225 00:11:26.919 --> 00:11:31.639 Push content like a very ludicrous example refrigerator, you can 226 00:11:31.679 --> 00:11:34.639 do it. And so I've working on Strappy. I've seen 227 00:11:34.639 --> 00:11:38.480 so many use different use cases that people are using 228 00:11:40.440 --> 00:11:44.120 with Strappie outside of like a standard blog like it 229 00:11:44.159 --> 00:11:46.240 blew my mind and so I wanted to create something 230 00:11:46.240 --> 00:11:48.120 that kind of goes slightly beyond that. 231 00:11:48.559 --> 00:11:50.840 Okay, okay, that makes a ton of sense. 232 00:11:51.200 --> 00:11:55.120 And yeah, I think that we as developers we jump 233 00:11:55.200 --> 00:11:58.559 too quickly to something that we're going to have food 234 00:11:58.559 --> 00:12:04.519 control on. Honestly, it actually makes sense in many cases 235 00:12:04.840 --> 00:12:10.639 if you're like actually building a web application, but not always, 236 00:12:10.799 --> 00:12:14.840 you know, and you also have to consider how much 237 00:12:15.000 --> 00:12:20.200 time you're going to add because you want to manage 238 00:12:19.960 --> 00:12:25.879 the database completely yourself, right, So you could still just 239 00:12:26.120 --> 00:12:29.360 start with Strappy or something similar and then you can 240 00:12:29.399 --> 00:12:32.399 switch later when you actually need it. By the way, 241 00:12:32.840 --> 00:12:35.480 how does that look like? What if someone wants to 242 00:12:35.519 --> 00:12:39.720 start with Strappy, for example, and then later on they're 243 00:12:39.759 --> 00:12:45.159 getting enough traffic that they actually want to have more 244 00:12:45.200 --> 00:12:47.480 control over their back end and make sure that it 245 00:12:47.600 --> 00:12:50.480 scales the way that they wanted to scale. How would 246 00:12:50.639 --> 00:12:53.799 a migration of data out of Strappy look like? 247 00:12:55.240 --> 00:12:58.240 Yeah, I mean that's a great question. I'll answer it 248 00:12:58.240 --> 00:12:58.840 in two parts. 249 00:12:58.840 --> 00:13:02.120 The first part, you have most of our clients they're 250 00:13:02.200 --> 00:13:06.120 like and I can't mention them, but they're like enterprise 251 00:13:06.240 --> 00:13:09.279 level our clients that are getting a lot of like, 252 00:13:10.039 --> 00:13:13.639 you know, hits, and it scales well. Because the cool 253 00:13:13.639 --> 00:13:16.440 part about Strappy you could self host it, so it's 254 00:13:16.519 --> 00:13:18.919 literally up to your DevOps team how they decide to 255 00:13:18.960 --> 00:13:20.960 manage that process, which makes it awesome. 256 00:13:21.000 --> 00:13:22.639 We do also have a class solution. 257 00:13:22.720 --> 00:13:26.000 But in terms of the migration process, if you know, 258 00:13:26.159 --> 00:13:28.559 there's many ways of doing it. You could export your 259 00:13:28.639 --> 00:13:31.519 data into like a format that makes sense for you, 260 00:13:31.600 --> 00:13:34.279 like because it's an API driven thing. Like some people, 261 00:13:35.000 --> 00:13:38.039 if let's say you're not well versed in you know, 262 00:13:38.200 --> 00:13:41.600 database backup and that whole like managing scal database and 263 00:13:41.679 --> 00:13:44.000 stuff like that, where you could actually just do a 264 00:13:44.360 --> 00:13:47.200 data migration from you know, like if use postcress, you 265 00:13:47.200 --> 00:13:50.159 could take that postgress and migrat it to wherever you 266 00:13:50.240 --> 00:13:54.279 need to. Or if you're not well versed in that 267 00:13:54.360 --> 00:13:56.679 part of things, because we have an API that you 268 00:13:56.679 --> 00:13:59.080 could hit, you could literally just write a script that 269 00:13:59.120 --> 00:14:02.080 will hit the API of Strappy, pull that data from there, 270 00:14:02.120 --> 00:14:05.200 and then you migrate it to whatever platform that you want. 271 00:14:05.399 --> 00:14:07.919 Like we do things like that. 272 00:14:07.960 --> 00:14:09.759 In the opposite way, if someone like for instance, want 273 00:14:09.799 --> 00:14:12.840 to migrate from wore press, they'll structure, they'll take their data, 274 00:14:12.840 --> 00:14:14.919 they clean it up, and then they'll just iterate through 275 00:14:14.919 --> 00:14:17.120 the data and they'll just make an API call into 276 00:14:17.120 --> 00:14:19.039 Strappy and Strappy will just load that data. 277 00:14:19.879 --> 00:14:21.480 So there's many ways of doing it. 278 00:14:22.120 --> 00:14:24.720 Another thing I was going to say, a lot of 279 00:14:24.759 --> 00:14:27.440 times when I talk about Strappy, people think like it's 280 00:14:27.759 --> 00:14:30.639 strappy or nothing. And so a lot of use cases 281 00:14:30.639 --> 00:14:33.679 that I've seen is Strappy is just like one service 282 00:14:33.879 --> 00:14:36.559 that their application uses. And that's like kind of one 283 00:14:36.559 --> 00:14:38.720 thing I did on a very small scale, like for 284 00:14:38.799 --> 00:14:41.639 the next ys project, although like I'm using Strappy to 285 00:14:41.639 --> 00:14:44.559 handle certain things. We do have a small like AI 286 00:14:44.759 --> 00:14:47.279 portion of it where we use open Ai and a 287 00:14:47.360 --> 00:14:49.679 library called length chain, which is awesome that they have 288 00:14:49.720 --> 00:14:52.639 a typescoop version because a lot of the Python things 289 00:14:52.679 --> 00:14:55.279 are I mean, a lot of like Ai stuff is 290 00:14:55.320 --> 00:14:59.080 done with Python, which is another language to learn for folks. 291 00:14:59.320 --> 00:15:00.440 So it was kind of cool. 292 00:15:00.480 --> 00:15:02.600 And so what I did is like I'm like, here's 293 00:15:02.639 --> 00:15:05.320 a piece that Strappy handles, and here's a piece that 294 00:15:05.399 --> 00:15:08.200 next JS handles would length chain, And what I like 295 00:15:08.240 --> 00:15:10.919 about it is could be a piece of a big puzzle. 296 00:15:11.440 --> 00:15:15.759 And there's like public companies like post hoc that use Strappy. 297 00:15:15.840 --> 00:15:19.360 They have a whole website and their content just because 298 00:15:19.360 --> 00:15:21.639 they had the system that they had before. All their 299 00:15:21.679 --> 00:15:24.639 content is in GIT and they're like, we're not going 300 00:15:24.720 --> 00:15:26.879 to move it to a different like thing. 301 00:15:26.879 --> 00:15:28.480 Because we're fine with Git. We like it. 302 00:15:28.519 --> 00:15:30.960 And so they use Strappy just to manage the users 303 00:15:31.000 --> 00:15:33.399 and their profiles. And so it doesn't have to be 304 00:15:33.519 --> 00:15:35.559 like you have to do everything. It could be like 305 00:15:35.600 --> 00:15:37.559 a piece of the puzzle in your application. And what 306 00:15:37.639 --> 00:15:41.480 I tell people, like, you know, not every solution is 307 00:15:41.559 --> 00:15:43.960 right for you, and not every solution is perfect, and 308 00:15:44.000 --> 00:15:46.720 you just have to find like do your due diligence, 309 00:15:46.840 --> 00:15:48.879 research what's out there and figure out what is the 310 00:15:48.879 --> 00:15:52.960 best solution for your client. And that's kind of to me, like, 311 00:15:53.000 --> 00:15:55.279 even though I will look at Strappy, I don't think 312 00:15:55.320 --> 00:15:58.519 Strappy is the right fit for everybody. But that's for 313 00:15:58.559 --> 00:16:00.759 you to decide based on your customers needs. 314 00:16:00.840 --> 00:16:01.080 Thanks. 315 00:16:01.200 --> 00:16:05.360 Yeah, that that's a very balanced response and any and 316 00:16:05.399 --> 00:16:08.279 it makes a ton of sense. Interesting to know that 317 00:16:08.320 --> 00:16:14.559 its scales so well, yeah, that's it's pretty interesting, all right. 318 00:16:14.759 --> 00:16:19.000 So, well, there's there's still a lot of subjects for 319 00:16:19.120 --> 00:16:19.679 us to cover. 320 00:16:19.919 --> 00:16:22.799 We didn't even went into some of your career advice 321 00:16:22.840 --> 00:16:28.559 for people wanting to switch to software development under after thirties, right, 322 00:16:28.919 --> 00:16:31.720 but before that, I just want to make sure Chris Bitter, 323 00:16:32.080 --> 00:16:34.200 do you guys have any questions thus far? 324 00:16:34.679 --> 00:16:36.759 Okay, yeah I do have one. 325 00:16:36.919 --> 00:16:40.480 So I apportunally stuppy for very long term and it's 326 00:16:40.519 --> 00:16:44.679 actually pretty awesome. But I think I would multiple needs 327 00:16:44.759 --> 00:16:47.960 once before when I worked on it. Yeah, so, but 328 00:16:48.080 --> 00:16:50.960 then I wanted to ask, so maybe you could talk 329 00:16:51.039 --> 00:16:54.759 more about this traffic clouds from future. I did just 330 00:16:54.799 --> 00:16:59.759 provided the cloud future prostraffic does for lectful use us dot. 331 00:17:00.039 --> 00:17:02.879 Maybe you don't want, so how do you deploy me 332 00:17:02.919 --> 00:17:05.720 to your cloud? But must speak like I know that 333 00:17:06.240 --> 00:17:09.799 you can't stay, you can't say stop you, but yeah 334 00:17:10.039 --> 00:17:13.880 for people that have know really technical just to hand 335 00:17:14.319 --> 00:17:17.160 to someone who can't. So maybe you could stop stop 336 00:17:17.200 --> 00:17:19.839 deep on that, right, maybe to just speak on how 337 00:17:20.440 --> 00:17:21.359 topic cloud works. 338 00:17:21.440 --> 00:17:26.880 Yeah, yeah, that's an amazing question because again, like I'm 339 00:17:26.920 --> 00:17:28.839 definitely not going to be a DevOps person and if 340 00:17:28.880 --> 00:17:31.200 I have to struggle with that stuff, like, to me, 341 00:17:31.599 --> 00:17:34.200 they're just time that I could be using somewhere else. 342 00:17:34.279 --> 00:17:36.599 And because like Trapp your self host it, you know 343 00:17:36.799 --> 00:17:38.559 a lot of people like oh perfect, I want to 344 00:17:38.559 --> 00:17:40.119 do all the school stuff. I want to spin up 345 00:17:40.200 --> 00:17:41.720 like that doctor, or I want to use s Cooper Days, 346 00:17:41.799 --> 00:17:43.039 or I want to use I want to do it 347 00:17:43.079 --> 00:17:44.200 like and I'm like, I just don't want to hear 348 00:17:44.240 --> 00:17:46.599 you talk about this stuff because to me, that stuff 349 00:17:46.599 --> 00:17:49.000 that is hard for me, and I just don't want 350 00:17:49.000 --> 00:17:51.160 to worry about it because I just want to work 351 00:17:51.240 --> 00:17:54.359 on creating the business solution for the product that the 352 00:17:54.359 --> 00:17:58.079 business wants. And so now we recently started Trappy Cloud, 353 00:17:58.640 --> 00:18:00.279 and to be honest, you did get I had some 354 00:18:00.359 --> 00:18:03.240 flack about it because you know, you look at platforms 355 00:18:03.240 --> 00:18:05.519 like Heroku before they took away their free tier, and 356 00:18:05.559 --> 00:18:08.519 you look at other you know services, they all start 357 00:18:08.559 --> 00:18:11.240 with a free tier. And that's Strappy. We are, you know, 358 00:18:11.440 --> 00:18:15.039 an open source company, and we give so much. Our 359 00:18:15.160 --> 00:18:17.400 Strappy Community edition is absolutely free. You could do whatever 360 00:18:17.400 --> 00:18:21.200 you want. We have like when people buy the enterprise license, 361 00:18:21.240 --> 00:18:23.400 they're literally just paying for the support. So we don't 362 00:18:23.640 --> 00:18:26.359 like as a company, we want to be profitable, so 363 00:18:26.400 --> 00:18:27.759 we made the decision we're. 364 00:18:27.640 --> 00:18:29.440 Going to start with Strappy. 365 00:18:30.680 --> 00:18:33.559 The higher tier, focusing more on our enterprise users or 366 00:18:33.640 --> 00:18:36.400 like agencies who could afford. So our initial pricing was 367 00:18:36.480 --> 00:18:38.880 ninety nine dollars a month but even with that, like 368 00:18:40.240 --> 00:18:41.920 when you take a look at what it does, you 369 00:18:41.960 --> 00:18:46.000 get database, you get email, you get CDN, you get 370 00:18:46.000 --> 00:18:50.319 file storage. Everything is deployed in one quick step, very 371 00:18:50.359 --> 00:18:52.920 easy to manage. And for me, like we was, I 372 00:18:52.920 --> 00:18:55.279 thought about it. If I'm a DevOps person, like the 373 00:18:55.359 --> 00:18:58.039 more work I have, the better. But as someone who's 374 00:18:58.319 --> 00:19:00.279 looking to build a product, they're like, I just want 375 00:19:00.319 --> 00:19:02.680 to get a solution that I could pay. So for 376 00:19:02.759 --> 00:19:05.599 our developer who's building everything themselves, they're like, I don't 377 00:19:05.599 --> 00:19:07.400 want to pay ninety nine bucks. Why would I, Like, 378 00:19:07.440 --> 00:19:08.920 I just build it myself. 379 00:19:09.039 --> 00:19:10.119 Perfect. That's great. 380 00:19:10.359 --> 00:19:12.119 For a business owner who's like, I don't know, I 381 00:19:12.200 --> 00:19:15.319 just want to have this thing done, they're like ninety 382 00:19:15.400 --> 00:19:16.720 nine dollars a month, that's nothing. 383 00:19:16.720 --> 00:19:18.759 And I kind of found it very interesting. 384 00:19:18.799 --> 00:19:21.720 How like, depending who you talk about, it's either highly 385 00:19:21.759 --> 00:19:25.759 overpriced or highly undervalued. But with that being said, with 386 00:19:25.839 --> 00:19:29.400 all the things that we're doing, because you know, strapping 387 00:19:29.440 --> 00:19:33.480 cloud is the easiest way to deploy you know, your 388 00:19:34.000 --> 00:19:36.799 strappy application, similar to like versail for next it's the 389 00:19:36.839 --> 00:19:38.000 best way to do it. 390 00:19:38.079 --> 00:19:41.160 And so we're started at the higher price range. 391 00:19:41.279 --> 00:19:41.680 Now. 392 00:19:41.960 --> 00:19:42.400 A couple of. 393 00:19:42.400 --> 00:19:45.880 Months ago we introduced our depth plan, which is a 394 00:19:45.960 --> 00:19:48.279 twenty nine dollars a month as we continue to make 395 00:19:48.319 --> 00:19:50.759 progress with the cloud, and our next iteration is we 396 00:19:50.799 --> 00:19:55.240 do want to have that free you know, hobby plan 397 00:19:55.480 --> 00:19:58.079 that developers could just use for our cloud. But we 398 00:19:58.200 --> 00:20:01.079 just took that top down approach by just try to 399 00:20:01.200 --> 00:20:03.400 make some income first so we could continue to develop 400 00:20:03.440 --> 00:20:06.559 these services. And so our goal is to have free 401 00:20:06.759 --> 00:20:09.279