Trascrizione completa di S8 E2 | Nx Import and Experts and Monorepo Worlds Oh My! | Isaac Mann & Mike Hartington

specifically designed for mono reposts, and it scales up. 76 00:04:13.240 --> 00:04:16.079 The features that NX has scale scale up as your 77 00:04:16.160 --> 00:04:18.800 organization side scales up and as your your code based 78 00:04:18.800 --> 00:04:24.000 scales up, and it provides you with tools that that 79 00:04:24.160 --> 00:04:27.759 all work together to improve your developer experience and make 80 00:04:27.800 --> 00:04:30.639 sure that you can that you can you can work 81 00:04:30.639 --> 00:04:33.439 well together in a large repot story. 82 00:04:34.000 --> 00:04:35.800 Yeah, and then like there's. 83 00:04:35.560 --> 00:04:39.600 The add on piece of that with paid NX cloud functionality, 84 00:04:39.600 --> 00:04:42.560 that's that's all focused on improving your your c I 85 00:04:42.680 --> 00:04:46.839 experience and making sure that that's that's fast and and 86 00:04:47.000 --> 00:04:49.959 has you know, good good throughput and is able to 87 00:04:50.480 --> 00:04:52.680 have have lots of people work like lots of lots 88 00:04:52.680 --> 00:04:55.720 of prs going through there quickly. 89 00:04:56.360 --> 00:04:56.720 Yeah. 90 00:04:56.879 --> 00:04:59.319 Yeah, I think what surprised me about NX when I 91 00:04:59.399 --> 00:05:01.959 was first you know, before I worked at Cisco, I 92 00:05:02.160 --> 00:05:05.399 actually hadn't worked with it. It just hadn't come up 93 00:05:05.439 --> 00:05:08.519 at a job and I never thought to say, oh, 94 00:05:08.560 --> 00:05:10.759 I'll just new up an NX project on my own. 95 00:05:11.160 --> 00:05:13.360 But it's actually really easy to just do that. 96 00:05:14.600 --> 00:05:18.800 I think it's hard to simulate the problems that people 97 00:05:18.879 --> 00:05:24.800 run into with enterprise applications. So but I do know, 98 00:05:25.120 --> 00:05:28.800 you know now I'm making this like a from my perspective. 99 00:05:29.399 --> 00:05:32.120 The NX team has been very helpful to my team 100 00:05:32.560 --> 00:05:39.120 solving some of our big enterprise application problems. So so yeah, 101 00:05:39.160 --> 00:05:41.079 it's a really great tool. 102 00:05:41.279 --> 00:05:45.240 What version are we on now for n nineteen seven? 103 00:05:46.000 --> 00:05:50.279 Just release Monday, I think on September ninth. 104 00:05:50.800 --> 00:05:54.680 So Normal, So NX, I guess you just rebranded east 105 00:05:54.839 --> 00:05:57.480 like what a year ago or so, like entirely like 106 00:05:57.839 --> 00:06:01.680 drop the normal name tag. So Normal was around back 107 00:06:01.680 --> 00:06:03.839 in like twenty seventeen or so, So some people may 108 00:06:03.839 --> 00:06:05.720 not know that they're the same company. 109 00:06:06.439 --> 00:06:09.839 Yeah, yeah, so Narwal and NX. 110 00:06:10.120 --> 00:06:13.319 The tool has always been named NX, but Narwal's was 111 00:06:13.319 --> 00:06:18.120 the name of the company because we were selling consulting 112 00:06:18.160 --> 00:06:22.160 services as the Narwal Company, and in like a year 113 00:06:22.199 --> 00:06:24.600 and a half ago, we shifted over from being focused 114 00:06:24.600 --> 00:06:29.079 on on being profitable through selling consulting to being a 115 00:06:29.079 --> 00:06:34.160 product focused company and getting our funding from through selling 116 00:06:34.279 --> 00:06:39.920 enterprise solutions from NX cloud and so with when when 117 00:06:39.920 --> 00:06:42.519 we did that shift, and especially like people in the 118 00:06:42.560 --> 00:06:45.079 anchor of a community knew of us as Narwal and 119 00:06:45.120 --> 00:06:48.839 that was like pretty well understood. But in other communities 120 00:06:48.879 --> 00:06:53.160 like react, in other places, the people would be familiar 121 00:06:53.199 --> 00:06:56.079 with NX but had no idea who Narwal was. And 122 00:06:56.120 --> 00:06:58.120 so we said, okay, we'll just make this easier for everybody. 123 00:06:58.120 --> 00:07:02.240 We'll just call ours company NX as well, and just 124 00:07:02.360 --> 00:07:03.120 move forward that way. 125 00:07:03.439 --> 00:07:05.680 Yeah. I think some of the original bundles our packages 126 00:07:05.720 --> 00:07:09.240 were at Norwal right in our w role. Yeah. 127 00:07:09.480 --> 00:07:09.639 Yeah. 128 00:07:09.680 --> 00:07:13.079 Actually I did a talk in May and I was 129 00:07:13.240 --> 00:07:16.720 going through and updating my slides and I realized that 130 00:07:16.879 --> 00:07:18.480 all of my imports were wrong. 131 00:07:25.800 --> 00:07:26.000 Yeah. 132 00:07:26.079 --> 00:07:27.720 Yeah, I don't think we have a migrade script for 133 00:07:27.800 --> 00:07:29.399 your apartment slides. 134 00:07:29.480 --> 00:07:33.000 But I know that's see this is I feel like 135 00:07:33.000 --> 00:07:35.720 like NX is really letting me down in this department. 136 00:07:36.839 --> 00:07:40.040 But I do have to say, okay, so one of 137 00:07:40.079 --> 00:07:44.000 the in the like, I guess it's not like it 138 00:07:44.040 --> 00:07:47.480 doesn't feel super recent because you're like just blowing through releases, right, 139 00:07:47.600 --> 00:07:50.279 Like we always talk about how fast. 140 00:07:50.000 --> 00:07:51.800 The Angular team releases features. 141 00:07:51.800 --> 00:07:55.759 But I have to say NX is going faster somehow, so, 142 00:07:56.680 --> 00:08:01.199 which is truly impressive. But one of the you know, 143 00:08:01.399 --> 00:08:04.480 in May, when I was writing this side, it was 144 00:08:04.560 --> 00:08:08.600 a talk about custom generators and plug it local plugins, 145 00:08:09.079 --> 00:08:12.759 and I was really anxious about Project Crystal, And do 146 00:08:12.759 --> 00:08:14.720 you want to talk a little bit about what Project 147 00:08:14.759 --> 00:08:15.759 Crystal is? 148 00:08:17.399 --> 00:08:17.680 Sure? 149 00:08:18.000 --> 00:08:19.439 I feel like I've been talking a lot, Mike, you 150 00:08:19.439 -->

00:08:23.839 want to Oh yeah. 151 00:08:22.120 --> 00:08:25.199 Yeah, sure, Well we're gonna have to assume as it 152 00:08:25.240 --> 00:08:30.879 can correct me wherever I misspeak Project Crystal. The general 153 00:08:30.920 --> 00:08:34.039 idea of it is, there are all these tools out 154 00:08:34.080 --> 00:08:39.360 there where all of the configuration set up work is 155 00:08:39.399 --> 00:08:43.600 done inside that tool with a specific file right beat 156 00:08:43.639 --> 00:08:48.440 for example, storybook just all of these have their own 157 00:08:48.480 --> 00:08:53.480 individual configus versus having to tell not only the tool 158 00:08:53.519 --> 00:08:58.480 but then an ex itself how that configure works. We 159 00:08:58.519 --> 00:09:03.159 can make some premature up like optimistic kind of settings 160 00:09:03.200 --> 00:09:05.639 based on that, can fig and just say we'll read 161 00:09:05.679 --> 00:09:08.879 in whatever is inside of your just can pig pull 162 00:09:08.960 --> 00:09:13.720 that in and then let our tools utilize that information 163 00:09:14.200 --> 00:09:15.960 or severy to declare it twice. 164 00:09:17.360 --> 00:09:17.600 I do. 165 00:09:18.720 --> 00:09:19.879 Yeah, I think it's great. 166 00:09:20.240 --> 00:09:23.960 I think the like the whole like one of the 167 00:09:24.360 --> 00:09:27.559 big impacts of this kind of shift is that it 168 00:09:27.600 --> 00:09:30.279 makes it really easy for people who have an existing 169 00:09:30.320 --> 00:09:33.480 setup to just add NX and NX you don't have 170 00:09:33.519 --> 00:09:36.440 to configure NX at all. NX sees your configuration that's 171 00:09:36.480 --> 00:09:40.600 already there, and just like ADS cashing on top or 172 00:09:40.600 --> 00:09:43.720 ads like the NX knowledge about your your project graph 173 00:09:43.759 --> 00:09:46.639 on top, which which just makes it really nice. 174 00:09:46.960 --> 00:09:49.320 Yeah. Yeah, because I think configuration is one of those 175 00:09:49.320 --> 00:09:54.559 things that is it's so frustrating for I mean just 176 00:09:54.600 --> 00:09:57.600 trying to set up just in a like I recently 177 00:09:57.639 --> 00:09:59.399 just trying to set up just in a view application 178 00:09:59.559 --> 00:10:04.159 and I I actually just stopped because I I just 179 00:10:04.360 --> 00:10:06.960 was like, it's just it's not worth it. I'll just 180 00:10:07.039 --> 00:10:09.000 keep doing the like I'll just keep doing because I, 181 00:10:09.039 --> 00:10:10.919 you know, built it with the tests. So I was like, okay, 182 00:10:10.960 --> 00:10:13.879 well maybe I can. It's like the jest and yeah, 183 00:10:14.519 --> 00:10:19.279 it's dumb, right, Like configuration, it's like it's picky, it's persnicity, 184 00:10:19.519 --> 00:10:22.440 like oh you forgot to set this one thing or 185 00:10:22.480 --> 00:10:25.080 this file didn't you didn't magically name that file the 186 00:10:25.159 --> 00:10:26.399 right thing or. 187 00:10:26.679 --> 00:10:31.200 Right You have like twenty six different Boollian flags and 188 00:10:31.279 --> 00:10:33.320 you have to test all possible permutations. 189 00:10:33.360 --> 00:10:35.279 To see which what's correct. 190 00:10:35.519 --> 00:10:37.639 Exactly and everything? 191 00:10:37.840 --> 00:10:39.720 Why did you do that right? 192 00:10:40.039 --> 00:10:43.320 And every moment you spend on configuration feels like wasted 193 00:10:43.360 --> 00:10:46.960 time because you're not like advancing a feature like getting 194 00:10:47.120 --> 00:10:52.039 like the You can't you can't like justify it to 195 00:10:52.240 --> 00:10:54.799 other people saying I provide a value to the company, 196 00:10:54.799 --> 00:10:56.120 because it's like I, I have no idea if this 197 00:10:56.159 --> 00:10:56.759 is valuable or not. 198 00:10:57.200 --> 00:10:59.320 I spent two days trying to configure this thing. I 199 00:10:59.320 --> 00:11:02.799 think it's work, but we'll find out right, And. 200 00:11:02.879 --> 00:11:05.159 Then then it's like it's like a three line pr 201 00:11:05.320 --> 00:11:08.039 for for like five days of work, like okay, well 202 00:11:08.279 --> 00:11:10.600 but they were the right three lines, but you. 203 00:11:10.559 --> 00:11:16.039 Should see all the other lines I tried. Yeah, absolutely, 204 00:11:16.120 --> 00:11:18.840 And you know, from my experience it worked really well 205 00:11:18.879 --> 00:11:20.960 with I had a very like sort of a small 206 00:11:20.960 --> 00:11:21.440 demo app. 207 00:11:21.480 --> 00:11:24.679 It worked very well. What has the experience been for 208 00:11:24.919 --> 00:11:26.080 like enterprise. 209 00:11:25.759 --> 00:11:28.360 Users like using Project Crystal? 210 00:11:28.840 --> 00:11:31.120 Yeah? Yeah, like what's that like? Upgrading? 211 00:11:31.159 --> 00:11:34.320 What version was that? I? I can't even was it? 212 00:11:34.799 --> 00:11:34.919 Uh? 213 00:11:35.120 --> 00:11:35.480 Nineteen? 214 00:11:35.519 --> 00:11:35.720 Oh? 215 00:11:36.120 --> 00:11:37.960 Was the August eighteen? I think? 216 00:11:38.279 --> 00:11:38.440 Yeah? 217 00:11:38.480 --> 00:11:43.879 I was like I think eighteen introduced, eighteen introduced Project Crystal, 218 00:11:43.919 --> 00:11:46.600 and then nineteen like expanded on it. 219 00:11:47.960 --> 00:11:50.399 So for for a few months now, we've had. 220 00:11:51.639 --> 00:11:55.799 Convert to inferred generators, which let you, on a plugin 221 00:11:55.840 --> 00:12:00.159 by plugin basis, convert like an existing If you have 222 00:12:00.200 --> 00:12:04.120 an existing task that's that kind of has the default configuration, 223 00:12:04.639 --> 00:12:08.080 you can you can switch it over to using inferred tasks, 224 00:12:09.039 --> 00:12:11.240 which is the whole Project Crystal set up. 225 00:12:12.240 --> 00:12:17.000 And just I guess this week we'll we're releasing. 226 00:12:16.559 --> 00:12:20.600 A a new generator

that will like run all of 227 00:12:20.639 --> 00:12:23.600 those together, so you can, like acrostio ho code base, 228 00:12:23.679 --> 00:12:25.440 you can do you can run all the plug ins, 229 00:12:26.080 --> 00:12:28.960 convert all the plug ins tasks over to inferred tasks 230 00:12:29.039 --> 00:12:31.720 in in one full swoop. So it just kind of 231 00:12:31.720 --> 00:12:35.240 makes improves the the onboarding process there a little bit. 232 00:12:36.320 --> 00:12:41.120 And so generally speaking, if if people are like, if 233 00:12:41.360 --> 00:12:45.039 your tasks are working and they're you're you're happy with it, 234 00:12:45.200 --> 00:12:48.080 then then people just kind of stick with what they've 235 00:12:48.120 --> 00:12:49.519 got and that's that's totally fine. 236 00:12:50.519 --> 00:12:51.399 So the the. 237 00:12:51.480 --> 00:12:55.919 Converting from from like explicitly defined tasks to using inferred 238 00:12:56.000 --> 00:12:59.799 tasks is really an optional thing. It's it's a you know, 239 00:12:59.799 --> 00:13:02.320 it's it reduces the amount of configuration that you have. 240 00:13:02.519 --> 00:13:04.759 It goes from having kind of two sources of truth 241 00:13:04.799 --> 00:13:05.759 to one source of truth. 242 00:13:06.159 --> 00:13:07.000 But if it's not. 243 00:13:07.000 --> 00:13:09.840 Broken then it does that you don't need to like 244 00:13:10.240 --> 00:13:13.120 try to change it. That the main benefit. 245 00:13:13.759 --> 00:13:16.399 It's feeling like the standalone component story in Angular, where 246 00:13:16.440 --> 00:13:19.000 it's like mode will still work. They are a little 247 00:13:19.000 --> 00:13:21.440 more complex if they're not broken, you don't have to 248 00:13:21.440 --> 00:13:23.960 make it your top priority to go deal with it, right. 249 00:13:24.039 --> 00:13:28.200 Yeah, but it's just easier for anyone who's starting stuff 250 00:13:28.200 --> 00:13:31.080 from scratch to say, okay, well we'll just have all 251 00:13:31.080 --> 00:13:33.320 the configuration will stay in the jests can fig or 252 00:13:33.320 --> 00:13:36.960 in the vetcan fig and NX will just figure it 253 00:13:36.960 --> 00:13:37.480 out from there. 254 00:13:37.919 --> 00:13:38.600 Yeah. Nice. 255 00:13:38.879 --> 00:13:43.240 Nice, And I want to say my experience with it 256 00:13:43.279 --> 00:13:45.399 with like our local plugins, we really didn't have to 257 00:13:45.399 --> 00:13:48.080 do anything and it just kind of worked. Like there 258 00:13:48.080 --> 00:13:50.559 were some minor change. There's always some minor changes I 259 00:13:50.559 --> 00:13:52.960 think we make every time we end up bumping versions, 260 00:13:53.039 --> 00:13:57.679 but nothing like we didn't have to do like full 261 00:13:57.759 --> 00:14:00.639 rewrite start from scratch situations. 262 00:14:00.039 --> 00:14:02.159 So that was great. 263 00:14:01.679 --> 00:14:03.840 N I don't think we've started doing that stuff at

264 00:14:03.840 --> 00:14:10.840 Bill yet. I believe for on eighteen though, So yeah, yeah. 265 00:14:10.679 --> 00:14:12.080 It's week possible now for you. 266 00:14:12.720 --> 00:14:16.600 Yeah, Yeah, we definitely try to keep We try to 267 00:14:16.720 --> 00:14:20.559 keep up on our NX version because we actually use 268 00:14:20.759 --> 00:14:24.159 NX to manage migrating our Angular version. 269 00:14:24.840 --> 00:14:27.639 So oh a love. We are in nineteen to five. 270 00:14:27.799 --> 00:14:30.279 So yeah, I'm just not in the know. We have 271 00:14:30.320 --> 00:14:31.480 a whole platform. 272 00:14:31.480 --> 00:14:33.679 Angular eighteen, I know, isn't it weird? 273 00:14:33.720 --> 00:14:35.440 Like I know, we have a whole team like one 274 00:14:35.519 --> 00:14:38.360 of you know, we have a whole team that handles 275 00:14:38.399 --> 00:14:40.519 a lot of the NX stuff for us, which is 276 00:14:40.519 --> 00:14:46.240 great because it is configuration and really, like as much 277 00:14:46.240 --> 00:14:47.879 as you don't want the buss factor to be high 278 00:14:47.879 --> 00:14:51.759 on that, you do want. 279 00:14:51.159 --> 00:14:52.919 Like imbody dedicated to that. 280 00:14:53.039 --> 00:14:54.039 Then yeah, I. 281 00:14:53.960 --> 00:14:56.879 Really don't want to deal with trying to onboard like 282 00:14:57.320 --> 00:14:58.480 literally everyone. 283 00:14:58.120 --> 00:14:59.720 On my team to understand how can figure. 284 00:14:59.840 --> 00:15:02.639 Like it'd be cool if they could understand that what 285 00:15:02.720 --> 00:15:04.039 it looks like if it's broken, But. 286 00:15:06.039 --> 00:15:07.720 I don't know if I need everyone writing it. 287 00:15:07.759 --> 00:15:11.960 So same way with generators, And yeah, I do not 288 00:15:12.039 --> 00:15:14.480 want to say like I went to n X Con 289 00:15:14.919 --> 00:15:17.159 was that two years ago when they were saying executors 290 00:15:17.159 --> 00:15:22.080 and I've been calling executors all this time. I don't 291 00:15:22.120 --> 00:15:22.279 know what. 292 00:15:23.440 --> 00:15:24.320 I don't matter. 293 00:15:28.159 --> 00:15:29.639 A task there. 294 00:15:29.399 --> 00:15:33.720 Are but they're executors about it. 295 00:15:35.200 --> 00:15:38.240 I'm just gonna I'm just gonna think of like Pokemon 296 00:15:38.360 --> 00:15:41.440 now because that just sounds like one of the pokemons 297 00:15:41.440 --> 00:15:45.519 and I'm like executor. 298 00:15:43.960 --> 00:15:49.519 Or whatever with something with Jesus. 299 00:15:52.200 --> 00:15:52.960 Executor. 300 00:15:56.039 --> 00:15:57.600 Let's just been that. We'll just be the rest of 301 00:15:57.639 --> 00:16:02.759 the con like the podcast. Uh riffing on executor. 302 00:16:03.279 --> 00:16:09.799 Yeah, it's like ex X egg cute execu cute eggs 303 00:16:09.879 --> 00:16:10.679 egg cute. 304 00:16:11.039 --> 00:16:12.320 Oh that's adorable. 305 00:16:14.440 --> 00:16:15.639 An exegu tour. 306 00:16:16.200 --> 00:16:19.919 He's a He's an egg pineapple tree egg tour makes 307 00:16:19.960 --> 00:16:20.720 total sense. 308 00:16:22.519 --> 00:16:24.039 The lore is deep in there. 309 00:16:24.320 --> 00:16:27.960 It is. One of the things that I remember from 310 00:16:28.080 --> 00:16:30.720 NX comp last year was you guys talking about the 311 00:16:30.840 --> 00:16:33.480 n X workflows. Is that still like going? Is that 312 00:16:33.639 --> 00:16:35.840 did that release yet? I mean that was a pretty 313 00:16:35.919 --> 00:16:37.879 cool groundbreaking thing. 314 00:16:38.559 --> 00:16:42.519 Yeah, NX Workflows is still like in the pipeline in 315 00:16:42.519 --> 00:16:46.440 the future that So just to summarize what that is 316 00:16:47.240 --> 00:16:47.960 for people don't know. 317 00:16:48.039 --> 00:16:48.840 So we we. 318 00:16:48.879 --> 00:16:56.480 Have NX Cloud is a platform for kind of orchestrating 319 00:16:56.519 --> 00:17:00.960 your your c I tasks and automatically realalyzing them for 320 00:17:01.000 --> 00:17:04.920 you across multiple agent machines. And so we provide the 321 00:17:04.960 --> 00:17:08.440 agent machines that you can run the tasks on and 322 00:17:08.720 --> 00:17:12.319 but you still you're still launching your CI process through 323 00:17:12.400 --> 00:17:14.880 your own CI provider that whether it be Circle CI 324 00:17:15.000 --> 00:17:18.440 or gettub actions or whatever you're using. And so NX 325 00:17:19.039 --> 00:17:23.039 Workflows is in the future, we're planning to have the 326 00:17:23.079 --> 00:17:25.559 ability for you to not even use Circle CI instead 327 00:17:25.559 --> 00:17:28.759 of circles CI, you'd use NX Workflows to just to 328 00:17:29.119 --> 00:17:35.599 completely use the NX platform. That's that's not in the 329 00:17:35.599 --> 00:17:40.720 immediate future, but right now we're working on expanding NX 330 00:17:40.759 --> 00:17:43.920 agents and some some features around that. 331 00:17:44.799 --> 00:17:45.079 Nice. 332 00:17:45.119 --> 00:17:48.000 So let's talk a little bit about So you just 333 00:17:48.000 --> 00:17:51.720 said version nineteen seven, Yeah, it was released. 334 00:17:52.440 --> 00:17:55.160 What what what goodies do we get in nineteen seven? 335 00:17:56.240 --> 00:17:58.519 I'm right, So let's see. Let me look at my 336 00:17:58.599 --> 00:17:59.279 list here. 337 00:18:00.359 --> 00:18:06.400 So, uh, there's kind of three big things, two new 338 00:18:07.440 --> 00:18:12.039 NX commands, and uh in an NX cloud feature. So 339 00:18:12.319 --> 00:18:16.960 let's start with NX import. So the the goal of 340 00:18:17.000 --> 00:18:19.960 this command is to make it easier to bring new 341 00:18:20.000 --> 00:18:24.000 code into your repository. That that's one of one of 342 00:18:24.000 --> 00:18:27.200 the most difficult pieces of that is to try to 343 00:18:27.240 --> 00:18:30.920 preserve your get history from the from the other repository 344

00:18:30.920 --> 00:18:33.240 when you're when you're pulling things over and so that's 345 00:18:33.240 --> 00:18:35.319 that's what this command does. Instead of like we we 346 00:18:35.400 --> 00:18:38.240 have a recipe that like kind of walks you through 347 00:18:38.279 --> 00:18:40.559 how to do that, but this is just taking it 348 00:18:40.599 --> 00:18:42.359 and you don't even have to follow the recipe. You 349 00:18:42.400 --> 00:18:44.599 can just run the command and it will preserve your 350 00:18:44.599 --> 00:18:47.880 get history as you you bring the code over. And 351 00:18:47.960 --> 00:18:50.440 so you just provide it with a remote r L 352 00:18:51.000 --> 00:18:54.119 and like the path from the original the source directory 353 00:18:54.160 --> 00:18:56.680 and the path in the destination directory that you're currently in, 354 00:18:56.960 --> 00:18:59.680 and say, hey, take this, take this code, copy it 355 00:18:59.720 --> 00:19:01.519 out of the and paste it in this new place 356 00:19:01.839 --> 00:19:05.680 and make sure the good history is preserved. And then 357 00:19:05.759 --> 00:19:08.640 you have to manage like you're like after the fact, 358 00:19:08.680 --> 00:19:13.119 you have to manage like dependencies and any like uh 359 00:19:13.680 --> 00:19:17.799 like if if the imported code has like root cantig 360 00:19:17.839 --> 00:19:20.480 files that that were not copied over, you have to 361 00:19:20.519 --> 00:19:23.440 figure out how to do that yourself. But it just 362 00:19:23.480 --> 00:19:26.720 manages the good history piece for you, which which makes 363 00:19:26.720 --> 00:19:27.319 it a lot easier. 364 00:19:27.400 --> 00:19:27.599 Yeah. 365 00:19:27.680 --> 00:19:30.160 Yeah, that's nice because it's definitely stinks when you pull 366 00:19:30.200 --> 00:19:32.799 in like legacy code and then get blame as all 367 00:19:32.880 --> 00:19:35.559 you and you're like, no, I didn't I didn't write that, 368 00:19:36.319 --> 00:19:39.559 and do all of this, but right, like, I know 369 00:19:39.640 --> 00:19:42.559 I'm busy, but I'm not that busy. 370 00:19:42.720 --> 00:19:44.200 Yeah. 371 00:19:44.279 --> 00:19:46.839 So the one of the recommend things to do with 372 00:19:46.880 --> 00:19:49.960 that is too, if you're not using MPM workspaces in 373 00:19:50.000 --> 00:19:53.519 your like in the destination repository, to turn that on 374 00:19:53.599 --> 00:19:57.519 at least initially, like temporarily potentially, so that you can say, hey, 375 00:19:58.000 --> 00:20:00.960 these are all the dependencies of the project I'm importing, 376 00:20:01.279 --> 00:20:04.400 and you keep them separate for in the initial phase 377 00:20:04.680 --> 00:20:07.119 and make sure it's imported together. And then later in 378 00:20:07.160 --> 00:20:09.759 a follow up PR you could you could merge those 379 00:20:09.799 --> 00:20:13.359 dependencies into the like the root package, Jason, just so 380 00:20:13.359 --> 00:20:14.559 that you don't have to do that all at the 381 00:20:14.599 --> 00:20:15.079 same time. 382 00:20:16.400 --> 00:20:20.119 Nice And if you're trying to do this and it's frustrating, 383 00:20:20.559 --> 00:20:25.920 h NX has a great discord space, right like sure, yeah, yeah, definitely, 384 00:20:25.960 --> 00:20:28.279 there are probably people there who've been through this process 385 00:20:28.319 --> 00:20:29.880 and can help you out a little bit. 386 00:20:30.680 --> 00:20:31.960 Uh So that's one feature. 387 00:20:33.400 --> 00:20:35.880 We also have nx sync, which is a new command, 388 00:20:36.960 --> 00:20:40.960 So NX sync I guess the best way to describe 389 00:20:40.960 --> 00:20:44.079 this is the NX has a project graph that it 390 00:20:44.119 --> 00:20:47.839 creates based on your your filesystem or reads your filesystem, 391 00:20:47.880 --> 00:20:51.759 and all the imports and audit generates the project graph 392 00:20:51.880 --> 00:20:53.839 of how the all the projects depend on each other, 393 00:20:54.160 --> 00:20:56.359 So it goes from your filesystem to create a project 394 00:20:56.359 --> 00:21:00.519 graph NX sync. The main use case for SYNC is 395 00:21:00.559 --> 00:21:03.480 to be able to take your project graph and update 396 00:21:03.519 --> 00:21:06.680 your file system, so kind of going back the other direction. 397 00:21:07.440 --> 00:21:12.480 So this this unlocks the ability to UH. There's some 398 00:21:12.720 --> 00:21:16.279 like so what one specific one specific way this. 399 00:21:16.279 --> 00:21:19.359 Is being used is we're working on a Typescript project 400 00:21:19.440 --> 00:21:23.960 reference UH feature where you the recommended way from the 401 00:21:23.960 --> 00:21:28.160 Typescript team of managing Mono repo setup is to have 402 00:21:28.720 --> 00:21:30.880 your each of your ts can figs and your projects 403 00:21:31.920 --> 00:21:35.599 defined in that ts can fig file all of the 404 00:21:35.640 --> 00:21:40.400 dependencies of that project, so in code defining what all 405 00:21:40.680 --> 00:21:43.200 those dependencies are, and then Typescript will take care of, 406 00:21:43.559 --> 00:21:45.680 you know, building them in order, kind of like what NX. 407 00:21:45.480 --> 00:21:48.519 Does, but you have to actually explicitly define those things. 408 00:21:48.519 --> 00:21:52.680 So as you like change your imports, you have to 409 00:21:52.680 --> 00:21:54.799 remember to go back and do that, whereas with with 410 00:21:54.960 --> 00:21:57.599 NX sync, we can automatically do that for you and 411 00:21:57.680 --> 00:22:00.000 you continue to use NX the way you normally would 412 00:22:00.799 --> 00:22:05.200 and use the recommended Typescript way of handling project references, 413 00:22:06.200 --> 00:22:09.079 but just like, don't do all the extra work that 414 00:22:09.079 --> 00:22:11.319 that the typescript team is is trying to make you do. 415 00:22:12.000 -->

00:22:15.000 So just say no, that extra work is my mom. 416 00:22:15.160 --> 00:22:18.000 Yes, yeah, but but you can you can do all 417 00:22:18.039 --> 00:22:19.440 sorts of things with with n x sync. 418 00:22:19.480 --> 00:22:20.799 It's not just that kind of feature. 419 00:22:21.359 --> 00:22:24.480 So you know, plugin authors you can think about, hey, 420 00:22:24.559 --> 00:22:28.319 what what could I do with a with a command 421 00:22:28.359 --> 00:22:32.839 that that updates the basically it's like that depends on functionality. 422 00:22:33.039 --> 00:22:35.799 But instead of running another task before you run this task, 423 00:22:36.000 --> 00:22:39.160 you can run a generator before this task, and so 424 00:22:40.240 --> 00:22:42.799 you know, people people come up with I've come up 425 00:22:42.799 --> 00:22:44.359 with lots of scenarios were like, it would be nice 426 00:22:44.359 --> 00:22:46.119 if I could just run a generator first instead of 427 00:22:46.160 --> 00:22:50.720 an executor, because executors don't don't really update code, they're 428 00:22:50.720 --> 00:22:52.920 not supposed to, and so people like try to do 429 00:22:53.000 --> 00:22:55.640 hacks to get around that. But now you can actually 430 00:22:56.000 --> 00:22:59.000 run a generator first and then do your executor, and 431 00:22:59.160 --> 00:23:00.920 you know, there's lots of lots different things that that 432 00:23:00.960 --> 00:23:01.680 can come out of this. 433 00:23:02.480 --> 00:23:05.880 So the difference between an executor and a generator sort 434 00:23:05.920 --> 00:23:09.960 of like bottom like very dumb definition is the generator 435 00:23:10.480 --> 00:23:15.400 can write, delete, edit, update like it can do essentially 436 00:23:15.519 --> 00:23:18.519 crud on your on your actual files. 437 00:23:18.799 --> 00:23:21.039 Yeah, on your actual files. An executor is like everything 438 00:23:21.079 --> 00:23:24.000 else or you know, a task is like anything that's 439 00:23:24.079 --> 00:23:27.240 like you know, build output or linting or whatever, everything 440 00:23:27.240 --> 00:23:28.680 else you would do on your on your code. 441 00:23:29.160 --> 00:23:29.519 Nice. 442 00:23:30.079 --> 00:23:33.279 Yeah, So then I guess third third thing we have 443 00:23:34.599 --> 00:23:37.400 uh in the NX cloud, we have personal access tokens 444 00:23:38.359 --> 00:23:43.279 and the NX logan command. So pre nineteen eight or 445 00:23:43.319 --> 00:23:48.000 pre nineteen seven, I guess there, you have one access 446 00:23:48.039 --> 00:23:52.039 token to connect your NX repo to your to NX cloud. 447 00:23:53.480 --> 00:23:58.640 And generally speaking, that's that's fine because even if somebody 448 00:23:58.759 --> 00:24:00.640 copied out that access token and they would have to 449 00:24:00.680 --> 00:24:03.519 have the hash like shah. 450 00:24:03.279 --> 00:24:04.759 Of your current. 451 00:24:05.960 --> 00:24:09.440 Source code in order to do any sort of cash manipulation. 452 00:24:10.440 --> 00:24:13.599 But you know, people want more more security than that, 453 00:24:13.799 --> 00:24:16.680 So we're opening up the ability to have a personal 454 00:24:16.720 --> 00:24:18.519 access token for each individual user. 455 00:24:19.039 --> 00:24:22.279 And then then. 456 00:24:22.160 --> 00:24:24.920 You can limit the like the public access to to 457 00:24:25.880 --> 00:24:28.359 like no access basically or read only if you want to. 458 00:24:28.759 --> 00:24:32.200 And then individual developers can have their own log in 459 00:24:32.559 --> 00:24:35.960 and then that can be like disabled when they lead 460 00:24:36.000 --> 00:24:36.960 the team or whatever. 461 00:24:37.559 --> 00:24:39.519 Being able to kind of parse those out is it 462 00:24:39.559 --> 00:24:45.279 feels like an important feature? Yeah, security wise, and yeah yeah, 463 00:24:45.279 --> 00:24:46.440 definitely yeah. 464 00:24:46.279 --> 00:24:50.160 And and urt like assurance that hey, it doesn't really matter, 465 00:24:50.200 --> 00:24:54.200 you're not really insecure people. People don't buy that as much, 466 00:24:54.240 --> 00:24:55.920 So this is just an easier sell of like, okay, 467 00:24:55.960 --> 00:24:59.039 find you get your own separate log ins and and 468 00:24:59.119 --> 00:24:59.880 yeah you'll be happy. 469 00:25:00.039 --> 00:25:04.359 Yeah yeah, yeah, nice, very cool. All right. 470 00:25:04.599 --> 00:25:08.599 So one of the okay, so those are the three 471 00:25:08.759 --> 00:25:10.839 main things that came out with nineteen seven. 472 00:25:11.880 --> 00:25:14.200 Yeah, and nineteen seven and eight yeah. 473 00:25:14.799 --> 00:25:16.400 Nice nice, Yeah all right. 474 00:25:16.759 --> 00:25:19.440 So one of the things that we also kind of 475 00:25:19.440 --> 00:25:21.799 wanted to talk about a little bit here. And I 476 00:25:21.839 --> 00:25:26.799 am I am very lucky to not only is NX Champions, 477 00:25:26.960 --> 00:25:28.799 I am in an ex champion, but I also get 478 00:25:28.799 --> 00:25:31.079 to work with one. So I also work with Adrian Baron, 479 00:25:31.079 --> 00:25:36.920 who's another NX champion. I want to talk like, let's 480 00:25:36.960 --> 00:25:39.000 talk a little bit about what that program is that 481 00:25:39.119 --> 00:25:40.880 started relatively recently in the. 482 00:25:40.920 --> 00:25:44.000 Last like year, year and a half year or so. 483 00:25:44.319 --> 00:25:44.519 Yeah. 484 00:25:44.799 --> 00:25:48.559 Yeah, so yeah, so tell us a little. 485 00:25:48.359 --> 00:25:50.359 Bit about that program, what it means. 486 00:25:50.799 --> 00:25:53.880 And yeah, the NX Champion. 487 00:25:53.960 --> 00:25:58.880 So NX Champions are you know, people that are publicly 488 00:25:59.160 --> 00:26:01.839 talking about in it in some ways. So they're they're 489 00:26:01.920 --> 00:26:04.799 you know, blog posts, they're social president on social media, 490 00:26:05.880

--> 00:26:08.799 or they're you know, advocating foreign X in different ways, 491 00:26:08.920 --> 00:26:11.200 and we just want to you know, encourage that and 492 00:26:11.200 --> 00:26:13.640 and support people who are already doing that and whatever 493 00:26:13.720 --> 00:26:17.359 whatever way we can give them like early access to 494 00:26:17.400 --> 00:26:19.599 different things, have you know, provide a space for them 495 00:26:19.599 --> 00:26:21.480 to talk with each other and us about you know, 496 00:26:21.519 --> 00:26:24.480 concerns they might have, and just make it, you know, 497 00:26:25.240 --> 00:26:28.519 make it easier for for NX too to connect with 498 00:26:28.559 --> 00:26:31.240 the community that that these NX champions have access to 499 00:26:31.359 --> 00:26:34.440 that that we don't necessarily have a direct access to NKS. 500 00:26:34.559 --> 00:26:37.519 Yeah, like I know, oh gosh, I'm trying to remember, 501 00:26:37.839 --> 00:26:41.200 I get the So there's a significant overlap between like 502 00:26:41.240 --> 00:26:46.079 angular gdes and NX champions. In my brain, all the 503 00:26:46.079 --> 00:26:50.200 meetings kind of move together. But like I know from 504 00:26:50.200 --> 00:26:52.960 the meetings that you know what, we get a lot 505 00:26:53.000 --> 00:26:59.480 of good questions problem solving. What does NX get I 506 00:26:59.480 --> 00:27:02.680 mean aside from like having people out teaching, what does 507 00:27:02.799 --> 00:27:05.880 NX get from the NX champions? 508 00:27:06.440 --> 00:27:09.839 Oh yeah, I mean we also get like like real 509 00:27:09.880 --> 00:27:13.839 world feedback. So one of the things that that we 510 00:27:13.960 --> 00:27:16.519 kind of we lost some when we switched from being 511 00:27:16.519 --> 00:27:19.079 a consulting focused company to being a product focused company 512 00:27:19.119 --> 00:27:22.160 is that we're our employees are not directly working on 513 00:27:23.000 --> 00:27:28.119 client repos all the time, whereas an X champions typically are, 514 00:27:28.759 --> 00:27:32.920 and so they get some of that real world experience of, hey, 515 00:27:32.920 --> 00:27:35.079 this is what it actually feels like to use n 516 00:27:35.279 --> 00:27:38.160 X in a repo, and so they, you know, give 517 00:27:38.240 --> 00:27:40.400 us feedback like this, we keep trying to do this 518 00:27:40.440 --> 00:27:40.920 and we can't. 519 00:27:40.960 --> 00:27:42.359 We can't do it the way we want to do it. 520 00:27:42.799 --> 00:27:44.480 And so that that helps us a lot to be 521 00:27:44.519 --> 00:27:47.160 able to you know, modify things, make it easier for 522 00:27:47.160 --> 00:27:48.799 for people who are actually using the product. 523 00:27:49.599 --> 00:27:53.480 Yeah, I mean I joined my first sync with with 524 00:27:53.519 --> 00:27:58.319 the with the program and getting like as it was 525 00:27:58.319 --> 00:28:00.240 showing off a bunch of the new features

that we 526 00:28:00.240 --> 00:28:02.440 already just talked about. But it was really great to 527 00:28:02.519 --> 00:28:05.720 like people are actually coming up with like real world 528 00:28:05.799 --> 00:28:08.200 problems and like, once you develop a feature kind of 529 00:28:08.200 --> 00:28:12.599 in a silo internally almost you kind of don't understand 530 00:28:13.559 --> 00:28:17.119 the bigger implications of like what a feature could do, 531 00:28:17.480 --> 00:28:21.160 What are you missing? What are some things that just 532 00:28:21.200 --> 00:28:25.079 could be smoothed out in terms of user experience? So 533 00:28:25.720 --> 00:28:28.559 they're they are willing to give that feedback and willing 534 00:28:28.599 --> 00:28:33.240 to give their two cents and it's really a great program. 535 00:28:33.680 --> 00:28:36.160 Yeah, and you know to that point like say no, 536 00:28:36.319 --> 00:28:40.880 you're moving, Does NX still do consulting? You have some 537 00:28:41.000 --> 00:28:46.759 like lingering clients that way, are your clients still or yeah? 538 00:28:46.799 --> 00:28:51.160 So so we have enterprise program, so you can sign 539 00:28:51.240 --> 00:28:53.759 up for for enterprise through NX Cloud. And what that 540 00:28:53.759 --> 00:28:55.559 that program does is so you get you know, full 541 00:28:55.599 --> 00:28:57.640 access to all of our all of our products, but 542 00:28:57.680 --> 00:29:00.960 you also get you know, some some insulting hours where 543 00:29:01.000 --> 00:29:04.400 we help you, you know, configure NX and you. 544 00:29:04.359 --> 00:29:07.000 Know troubleshoot you know, slow downs and c I and stuff. 545 00:29:08.160 --> 00:29:10.960 But there there are some like companies that still want 546 00:29:11.200 --> 00:29:16.039 to have like people who are knowledgeable in n X 547 00:29:16.319 --> 00:29:20.720 but help with feature work or people who are able 548 00:29:20.759 --> 00:29:25.640 to like dedicate like full time work helping them you know, uh, 549 00:29:25.839 --> 00:29:29.039 spin up something new or whatever. Whereas you know, the 550 00:29:29.240 --> 00:29:33.759 enterprise program you have people like checking in on you 551 00:29:33.920 --> 00:29:37.920 or doing zoom calls with with the developers that do 552 00:29:38.000 --> 00:29:39.799 actually have full access to the code and what we're 553 00:29:39.839 --> 00:29:42.519 just kind of like you know, seeing it from you know, 554 00:29:42.680 --> 00:29:45.400 seeing it like debugging over zoom basically. 555 00:29:45.559 --> 00:29:49.000 Yeah, which that can be that's a whole skill and 556 00:29:49.160 --> 00:29:50.480 of itself actually right. 557 00:29:50.640 --> 00:29:52.720 Yeah. 558 00:29:52.920 --> 00:29:56.559 But so in order to like help with that process, 559 00:29:56.599 --> 00:30:02.359 we have some some certified partner program that partner companies 560 00:30:02.359 --> 00:30:06.839 that that we can refer those those companies too. And 561 00:30:07.559 --> 00:30:10.960 as part of that like process, we we launched a 562 00:30:10.960 --> 00:30:14.880 new program called NX Experts, whereas for for every for 563 00:30:14.960 --> 00:30:18.039 a company to be included as a as a partner 564 00:30:18.079 --> 00:30:21.920 that we can we can pass off uh people were 565 00:30:21.920 --> 00:30:26.839 interested in enterprise consulting X consulting two. The it's required 566 00:30:26.839 --> 00:30:29.599 that a partner partner company has at least two n 567 00:30:29.759 --> 00:30:33.440 X experts on their on their staff. And so NX 568 00:30:33.480 --> 00:30:36.160 experts they go through an interview process just to make 569 00:30:36.200 --> 00:30:38.880 sure that they know they know how to use n 570 00:30:39.039 --> 00:30:41.759 X and they're they're able to you know, guide clients 571 00:30:41.799 --> 00:30:45.680 through you know, problems that you know, troubleshooting things with 572 00:30:45.680 --> 00:30:48.079 with an X is make sure that you know, when 573 00:30:48.119 --> 00:30:50.119 when we recommend that these people know what they're talking about, 574 00:30:50.119 --> 00:30:51.039 they know what they're talking about. 575 00:30:51.359 --> 00:30:51.680 Nice. 576 00:30:51.680 --> 00:30:57.960 So, like between the like the enterprise program, the some 577 00:30:58.000 --> 00:30:59.759 of the consulting that you're still doing, the n X 578 00:31:00.039 --> 00:31:03.279 Experts and the NX Champions. NX is getting a lot 579 00:31:03.319 --> 00:31:11.240 of community feedback based on real, actual enterprise applications enterprise problems, 580 00:31:13.000 --> 00:31:15.160 and so I think that's a really important. 581 00:31:14.839 --> 00:31:16.400 It'd be really hard to build. 582 00:31:16.119 --> 00:31:20.400 A tool like NX without being tightly tied into the 583 00:31:20.400 --> 00:31:24.039 communities that use NX. I just don't even know how 584 00:31:24.039 --> 00:31:28.160 you could begin to develop it without that close communication. 585 00:31:29.039 --> 00:31:34.039 So the X Experts program, it's kind of reminding me 586 00:31:34.279 --> 00:31:37.599 of like the AWS certifications right where there's are there 587 00:31:38.480 --> 00:31:41.440 like currently it's I assume it's just one level like 588 00:31:41.720 --> 00:31:48.160 you're you either are or you aren't. But I think 589 00:31:48.200 --> 00:31:52.759 that it's an interesting It does give like peace of 590 00:31:52.799 --> 00:31:55.519 mind to have people on you know. I know that 591 00:31:55.839 --> 00:32:00.160 a consultancy I worked for we had several AWS certified developers, 592 00:32:00.200 --> 00:32:03.079 right so they could say we are an AWS certified 593 00:32:03.079 --> 00:32:05.559 shop because we have this many people. 594 00:32:05.240 --> 00:32:06.680 That are certified in AWS. 595 00:32:06.799 --> 00:32:09.599 And so that sounds like that's what the NX Experts 596 00:32:09.640

--> 00:32:13.640 program is giving you. So if a person feels like 597 00:32:13.759 --> 00:32:19.000 they are an NX expert and would like to go 598 00:32:19.119 --> 00:32:23.039 through the process to be declared one is there, what 599 00:32:23.160 --> 00:32:24.559 is the process to get involved with that? 600 00:32:26.279 --> 00:32:27.240 Let me see. 601 00:32:27.440 --> 00:32:33.240 So typically it goes through the company. 602 00:32:33.559 --> 00:32:37.240 Like the consultancy or yeah, the company itself will will 603 00:32:37.240 --> 00:32:40.400 reach out to us and say so that the company says, hey, 604 00:32:40.480 --> 00:32:42.960 we would like to be a partner program with. 605 00:32:42.480 --> 00:32:46.519 With NX, and and so they'll reach out to Joe 606 00:32:46.599 --> 00:32:49.039 at Naral dot Ao is probably the best person in 607 00:32:49.119 --> 00:32:53.759 contact and then the company will say, hey, these are 608 00:32:53.759 --> 00:32:56.880 the people that we want to you know, to apply 609 00:32:57.000 --> 00:33:01.279 and go through the interview process. Champions are also welcome 610 00:33:01.319 --> 00:33:04.920 to NX. Champions are also welcome to to be to 611 00:33:05.000 --> 00:33:07.039 go through the interview process and become experts as well. 612 00:33:07.960 --> 00:33:12.400 Although it's the the difference, Like NX champions already have 613 00:33:12.440 --> 00:33:15.519 full access to to NX, and all they get with 614 00:33:15.559 --> 00:33:17.640 the n X Expert program is that they get another 615 00:33:17.880 --> 00:33:19.119 another sticker to put up on. 616 00:33:19.079 --> 00:33:22.359 Their We like stickers, isik. 617 00:33:22.200 --> 00:33:29.440 Yeah right, Okay, don't get me wrong, but you know, 618 00:33:29.480 --> 00:33:32.839 I could see where if you were, you know, working, 619 00:33:33.160 --> 00:33:35.720 if you know, it's a good thing to have. 620 00:33:35.839 --> 00:33:38.559 I mean, I have people reach out to me specifically 621 00:33:38.559 --> 00:33:39.200 because I'm. 622 00:33:39.039 --> 00:33:40.000 An NX champion. 623 00:33:40.359 --> 00:33:42.279 I think it's also nice that there is a distinction 624 00:33:42.400 --> 00:33:46.000 between champion and expert. I feel like that's something about 625 00:33:46.000 --> 00:33:48.839 like the Google Developer Expert program that doesn't it's not 626 00:33:48.920 --> 00:33:52.599 always clear that like just because you're a GDE doesn't 627 00:33:52.640 --> 00:33:56.240 necessarily mean that you know everything about the thing. You're 628 00:33:56.279 --> 00:33:59.559 a GDAN, it means that you're out in the community 629 00:33:59.680 --> 00:34:00.880 talking about it. 630 00:34:02.079 --> 00:34:07.720 So yeah, yeah, I think, I mean, just the way 631 00:34:07.720 --> 00:34:11.480 it works out, the ex champions are like they're they're 632 00:34:11.519 --> 00:34:12.800 all at the level that they could. 633 00:34:12.639 --> 00:34:14.320 Be in ex experts to there. 634 00:34:14.480 --> 00:34:17.360 Yeah, yeah exactly, And and I think for the most 635 00:34:17.360 --> 00:34:19.760 you know, like I feel like I obviously don't know 636 00:34:19.880 --> 00:34:24.480 all of the Google has many developer expert flavors. 637 00:34:24.000 --> 00:34:24.800 Not just Angular. 638 00:34:24.880 --> 00:34:29.800 I know that's shocking to hear, but you know, like 639 00:34:29.880 --> 00:34:33.880 I feel like the community itself is going to pull 640 00:34:34.039 --> 00:34:36.559 away people that don't know what they're talking about at all, 641 00:34:36.679 --> 00:34:37.480 if that makes sense. 642 00:34:37.559 --> 00:34:39.920 Sure, Yeah, people are going to read blog posts that 643 00:34:40.000 --> 00:34:41.679 have in accuracies and that kind of stuff. 644 00:34:41.719 --> 00:34:44.440 Yeah, exactly, exactly, And so yeah, it is sort of 645 00:34:44.519 --> 00:34:47.800 a somewhat self policing program, but I think it is 646 00:34:47.840 --> 00:34:51.960 just important to the acknowledgment that the community gets for 647 00:34:52.480 --> 00:34:56.159 contributions to that I think is really important. And it 648 00:34:56.199 --> 00:35:00.760 does help, you know, because for example, I know, I 649 00:35:00.800 --> 00:35:06.480 think you know Q uh, Mike, we all do public speaking. 650 00:35:06.519 --> 00:35:08.519 We've all taken the time to write a talk and 651 00:35:08.559 --> 00:35:13.199 put it out there, and it's not paid. Sometimes if 652 00:35:13.199 --> 00:35:17.039 we're lucky, we get our airfare covered, maybe a hotel room, 653 00:35:17.519 --> 00:35:19.800 but it's not like we're also getting like the big 654 00:35:19.840 --> 00:35:21.079 dollar bills on top of that. 655 00:35:22.440 --> 00:35:26.159 Usually, I mean sometimes that happens, but. 656 00:35:25.840 --> 00:35:30.519 You get you get the satisfaction of people like saying 657 00:35:30.800 --> 00:35:32.360 that that they like you, and you have you have 658 00:35:32.400 --> 00:35:34.760 a big number of follower account and you feel good 659 00:35:34.800 --> 00:35:35.880 about yourself because. 660 00:35:35.719 --> 00:35:38.239 It's exactly exactly. 661 00:35:38.400 --> 00:35:41.639 And I do get those airplane tickets to the like 662 00:35:41.679 --> 00:35:45.280 I do get to go to the conferences, which is like, honestly, 663 00:35:45.599 --> 00:35:48.760 like aside from all the like the feel good like 664 00:35:48.800 --> 00:35:50.960 I helped people part of it, Like it is nice 665 00:35:51.000 --> 00:35:51.760 to be able to. 666 00:35:51.599 --> 00:35:53.599 Be engaged with the community that way. 667 00:35:54.800 --> 00:35:58.119 But it's nice to have programs like the NX Champions 668 00:35:58.239 --> 00:36:02.039 NX Experts, because then it's a badge I can wear 669 00:36:02.480 --> 00:36:07.159 that like employers can see other It also helps me 670 00:36:07.320 --> 00:36:14.639 get opportunities in other places as well. So nice. 671

00:36:15.280 --> 00:36:18.119 You can get the badge more than for the exposure 672 00:36:19.000 --> 00:36:20.440 exactly exactly. 673 00:36:22.719 --> 00:36:25.159 Yeah, and I get a cool little thing I can 674 00:36:25.199 --> 00:36:27.440 put on my like on my slide, It's like my 675 00:36:27.480 --> 00:36:30.519 slide's getting like who I am slide? 676 00:36:30.519 --> 00:36:32.519 It's like, yeah this, I got this. 677 00:36:32.840 --> 00:36:34.920 You have two pages on your about me slide at 678 00:36:34.920 --> 00:36:35.239 the end. 679 00:36:35.239 --> 00:36:40.519 Now right, the how you can reach me on social 680 00:36:40.559 --> 00:36:43.440 media one is getting a lot lower since I've got 681 00:36:43.519 --> 00:36:45.719 locked out of my Twitter account, can't get back in. 682 00:36:45.920 --> 00:36:49.840 So. 683 00:36:49.960 --> 00:36:52.119 I gave up. I tried a few times. I'm like, whatever, 684 00:36:52.159 --> 00:36:52.880 it's not worth it. 685 00:36:53.800 --> 00:36:55.000 The blue sky or something else. 686 00:36:55.079 --> 00:36:56.840 I know, yeah, I do have that, you know. 687 00:36:56.880 --> 00:36:59.119 It's like I've tried all the things, and honestly, I've 688 00:36:59.119 --> 00:37:01.199 turned into the old I'm on LinkedIn. I'm an old 689 00:37:01.239 --> 00:37:04.840 lady on LinkedIn hanging out complaining about work. Now, I 690 00:37:04.840 --> 00:37:09.679 don't complain about work, not on Linkedinn. 691 00:37:10.000 --> 00:37:10.280 That's it. 692 00:37:10.599 --> 00:37:13.079 You gotta gotta scratch that bit from the past. 693 00:37:14.519 --> 00:37:16.239 Like I'm gonna take this the threads if I'm going 694 00:37:16.280 --> 00:37:21.920 to be snarky. But yeah, So on the topic of community, 695 00:37:22.239 --> 00:37:28.039 on the topic of conferences, specifically, there is a conference 696 00:37:28.039 --> 00:37:32.000 coming up in October that yes, y'all might know a 697 00:37:32.039 --> 00:37:33.519 little bit about. 698 00:37:33.880 --> 00:37:35.480 What do you think? 699 00:37:35.800 --> 00:37:42.000 Yeah, uh yeah, we're putting on an event. Yeah, it's 700 00:37:42.039 --> 00:37:44.960 going to be I think past events that we've had 701 00:37:45.000 --> 00:37:49.280 have been very much focused on NX specifically and everything 702 00:37:49.320 --> 00:37:52.400 going on in our world, but mono repose as a 703 00:37:52.440 --> 00:37:57.199 concept kind of goes past what NX you know, passed 704 00:37:57.320 --> 00:37:59.880 off or like, there are other tools, need system and 705 00:38:00.199 --> 00:38:06.119 other aspects that people want to learn about that aren't 706 00:38:06.239 --> 00:38:11.199 specifically tied to just what we're doing. So monopool World is, 707 00:38:11.360 --> 00:38:14.519 you know, hence the name is bringing in people from 708 00:38:14.559 --> 00:38:18.360 all over the mono repo ecosystem kind of sharing their 709 00:38:18.400 --> 00:38:21.559 thoughts whether or not they are using NX, maybe they're 710 00:38:21.639 --> 00:38:27.559 using other tools, and just celebrating that aspect of what 711 00:38:27.599 --> 00:38:31.400 mono reposts can do, and hopefully people leave the event 712 00:38:31.599 --> 00:38:34.840 with a little bit more knowledge on how to do 713 00:38:34.880 --> 00:38:38.199 things the right way in theory and also have some 714 00:38:39.079 --> 00:38:41.679 uh information that they can bring back to their organization. 715 00:38:42.519 --> 00:38:43.719 What are some of the guests that are going to 716 00:38:43.800 --> 00:38:47.760 be there that spoilers or oh no, no, we we 717 00:38:47.800 --> 00:38:48.880 have we have our guest list. 718 00:38:48.920 --> 00:38:55.000 I'll be there's importantly. 719 00:38:54.719 --> 00:38:56.280 Well, you're not in a hex like, you're. 720 00:38:56.159 --> 00:38:58.239 Not in X, Like, who are some of the big 721 00:38:58.280 --> 00:39:01.920 companies that are going to I guess it's his Mono 722 00:39:02.000 --> 00:39:06.559 Repo world now. Because they're like a emissimash of different 723 00:39:07.000 --> 00:39:09.719 big companies who do monol repo tools that are going 724 00:39:09.760 --> 00:39:10.199 to be there. 725 00:39:10.519 --> 00:39:14.840 Yeah, I mean we're gonna have some folks from obviously 726 00:39:15.039 --> 00:39:18.440 NX will have you know, Jeff Victor are some other 727 00:39:18.559 --> 00:39:21.159 NX folks giving their sessions, but we'll also have folks 728 00:39:21.159 --> 00:39:27.639 from trunk Io, a couple of folks from Webflow, Hero Devs. 729 00:39:28.800 --> 00:39:32.280 We'll have Alex Eagle from the Basil team there to 730 00:39:32.320 --> 00:39:35.039 that way he can share some of his you know, 731 00:39:35.840 --> 00:39:39.920 stories from using Basil and mono repos. So it'll be 732 00:39:40.079 --> 00:39:43.239 just a nice cross section of people that you'll see. 733 00:39:43.800 --> 00:39:46.440 I think NX is also doing like an enterprise portion 734 00:39:46.559 --> 00:39:48.280 that they've kind of done in the past to one 735 00:39:48.320 --> 00:39:49.000 of the days. 736 00:39:49.280 --> 00:39:52.760 Yeah, we'll have a dedicated enterprise day that it's going 737 00:39:52.840 --> 00:39:57.679 to be kind of VIP section for all for customers 738 00:39:57.679 --> 00:40:02.360 and anyone who's doing more large scale projects. 739 00:40:03.440 --> 00:40:06.599 October seventh is like the normal conference day, and then 740 00:40:06.599 --> 00:40:11.920 October eighth will be the the invite yeah summit yep 741 00:40:12.199 --> 00:40:13.519 for science and people. 742 00:40:14.119 --> 00:40:18.800 I know that last year the summit portion of that, 743 00:40:19.000 --> 00:40:22.519 Like so the last year and the year before you 744 00:40:22.599 --> 00:40:31.519 did an x comp two day two conferences two twenty two, 745 00:40:31.679 --> 00:40:36.280 twenty twenty three, and they were really just kind of small, 746 00:40:36.360 --> 00:40:41.079

invite only only conferences, which was a Honestly, it's I mean, 747 00:40:41.159 --> 00:40:44.280 there's probably other industries that do something like that. 748 00:40:45.559 --> 00:40:46.559 What I found about. 749 00:40:46.400 --> 00:40:49.679 It was it was a really great opportunity for people 750 00:40:50.599 --> 00:40:54.239 to get together. Like the conversations I had at tables 751 00:40:54.239 --> 00:40:56.960 with people were so valuable, almost as valuable as the 752 00:40:57.039 --> 00:41:00.760 tracks themselves. And so I'm glad to see that you're 753 00:41:00.760 --> 00:41:05.079 also doing the Enterprise Workshop. What are you calling it, 754 00:41:05.079 --> 00:41:07.559 It's not workshop, you're calling it enterprise Summit. 755 00:41:07.760 --> 00:41:09.760 There we go the on the. 756 00:41:09.840 --> 00:41:12.719 Eighth as well, because I feel like, I mean, it's 757 00:41:12.719 --> 00:41:15.239 one thing to be able to work with the NX team, 758 00:41:15.280 --> 00:41:17.320 it's another thing to be able to talk to like 759 00:41:17.400 --> 00:41:23.039 the you're sort of the connection hub between enterprise people, right, 760 00:41:23.079 --> 00:41:25.360 and so to be able to get people who work 761 00:41:25.400 --> 00:41:28.840 with enterprise mono repos together in the same room so 762 00:41:28.880 --> 00:41:30.599 they can talk to each other, I think is. 763 00:41:30.639 --> 00:41:32.079 Also really valuable as well. 764 00:41:32.280 --> 00:41:36.119 Absolutely, so it's an amazing it's an amazing opportunity to 765 00:41:36.239 --> 00:41:42.159 do that. And so but for this conference, mono RepA 766 00:41:42.199 --> 00:41:48.559 world we're selling like you're selling tickets like general admission tickets, 767 00:41:48.559 --> 00:41:50.719 like if you want to go, like knowing. 768 00:41:50.800 --> 00:41:52.840 All your friends, tell all your. 769 00:41:52.719 --> 00:41:55.800 Friends, right, and so by the time this episode airs, 770 00:41:56.280 --> 00:41:59.480 this episode is scheduled to air on September thirtieth, so 771 00:41:59.639 --> 00:42:03.360 you should definitely go check and check the Mono RepA World. 772 00:42:03.480 --> 00:42:05.800 So I had to see bar any tickets left available? 773 00:42:05.920 --> 00:42:06.920 Get some last. 774 00:42:06.679 --> 00:42:09.119 Minute tickets into the Mono Repo World. 775 00:42:09.519 --> 00:42:10.639 Where's it being helped? 776 00:42:11.119 --> 00:42:13.000 So it's going to be a mountain view. We're actually 777 00:42:13.039 --> 00:42:17.159 going to have it had a really really cool location. 778 00:42:17.559 --> 00:42:21.159 It's going to be at the Computer History Museum, which 779 00:42:21.679 --> 00:42:24.639 I've never been, but I've been just like creeping on 780 00:42:24.719 --> 00:42:27.119 some photos checking it out and say, oh, it's going 781 00:42:27.199 --> 00:42:29.639 to be so cool, like my internet is going to 782 00:42:29.679 --> 00:42:33.000 be right,

just like looking at all the exhibits without 783 00:42:33.039 --> 00:42:36.079 paying attention to sessions maybe right right. 784 00:42:36.039 --> 00:42:38.079 Like Mike, get back in here, like oh sorry, I 785 00:42:38.119 --> 00:42:38.880 was reading. 786 00:42:38.599 --> 00:42:41.920 About I'm getting I'm getting fomo. 787 00:42:42.559 --> 00:42:44.880 I know all right, I'll actually be in Europe when 788 00:42:45.000 --> 00:42:49.559 when when Mono RepA World happens. So yeah, literally on 789 00:42:49.599 --> 00:42:52.159 the wrong side of the world for this conference, which 790 00:42:52.280 --> 00:42:54.639 is I'll be happy to be where I'm at, but 791 00:42:54.719 --> 00:42:58.320 I will also be sad to be missing the Mono 792 00:42:58.360 --> 00:42:58.880 RepA world. 793 00:42:59.079 --> 00:43:01.199 Yeah, this is the first one I'm missing. Like this 794 00:43:01.280 --> 00:43:03.760 is I've been to all of them up until now, 795 00:43:04.000 --> 00:43:07.079 and it's just because travel work travel. 796 00:43:07.679 --> 00:43:13.719 Yeah it's been it's been tight. But yeah, so very cool. 797 00:43:13.840 --> 00:43:16.039 So let's see. 798 00:43:16.239 --> 00:43:18.920 I'm looking at the speaker list here, and you've got 799 00:43:18.920 --> 00:43:21.679 a lot of really great people. I think I see 800 00:43:21.760 --> 00:43:25.239 several of our NX champions. Some of the NX experts 801 00:43:25.280 --> 00:43:28.880 are on the list as well. So so shout. 802 00:43:28.599 --> 00:43:30.599 Out to my guy JBA. I saw that he was 803 00:43:30.599 --> 00:43:32.679 on there. He posted that he's a headliner or something, 804 00:43:32.719 --> 00:43:35.239 and I was like, man, coming a long way, my guy. 805 00:43:35.800 --> 00:43:39.000 I'm excited to see to see his talk. Yeah, there's 806 00:43:39.039 --> 00:43:42.400 also another one in there, like hacking bundli is inside 807 00:43:42.400 --> 00:43:45.719 of NX, Like if you haven't been paying attention to 808 00:43:45.800 --> 00:43:49.000 like the Bundler world, thinking that THEES bills are going 809 00:43:49.079 --> 00:43:52.719 to be the only things. No, it's it's kept like progressing. 810 00:43:52.840 --> 00:43:56.719 It feels like it's the UH like twenty sixteen, twenty 811 00:43:56.800 --> 00:44:01.960 eighteen JavaScript War kind of era, like we'll have rs PAC, 812 00:44:02.840 --> 00:44:07.159 the SNBC UH even what's the new one from the 813 00:44:08.440 --> 00:44:11.639 from the that's like the roll up alternative now rewritten 814 00:44:11.639 --> 00:44:14.440 and rest like roll down. There's like all these new 815 00:44:14.480 --> 00:44:17.119 tools and like having a session that's just going to 816 00:44:17.159 --> 00:44:19.519 talk about like hey, let's show how you can drop 817 00:44:19.599 --> 00:44:22.639 this one or something else and bringing in there and 818 00:44:22.679 --> 00:44:26.400 see what what it what it does, see your project. Yeah, 819 00:44:26.480 --> 00:44:28.119 I think that's gonna be a really cool talk. 820 00:44:28.599 --> 00:44:32.679 Yeah, yeah, absolutely, And I love Lois's So it's Lois now. 821 00:44:32.639 --> 00:44:34.199 Giving that talk and I. 822 00:44:34.119 --> 00:44:37.840 Love her about Lois is just like waitress turncoder, like 823 00:44:38.000 --> 00:44:42.519 to the point, I'm like, awesome, Like, Q, you can relate. 824 00:44:42.280 --> 00:44:44.119 To this, right, I absolutely can. 825 00:44:44.480 --> 00:44:48.239 We literally talked about this last week, So. 826 00:44:48.599 --> 00:44:50.079 I appreciate that. That's awesome. 827 00:44:50.400 --> 00:44:53.480 Yeah, yeah, I love I love I love that. So 828 00:44:55.039 --> 00:44:57.440 what Okay, So Isaac, what session are you looking forward to? 829 00:44:59.000 --> 00:44:59.199 Yeah? 830 00:44:59.440 --> 00:45:02.880 I'm really curious about the I mean some of the 831 00:45:02.920 --> 00:45:06.039 things that are like like non NX related, like like 832 00:45:07.440 --> 00:45:13.079 scaling ownership to improve developer experience, Python mono repos with Basil. 833 00:45:13.320 --> 00:45:15.880 We got a few that are like this one talking 834 00:45:15.880 --> 00:45:18.239 about merged cues at scale. So these are kinds of 835 00:45:18.239 --> 00:45:22.880 things that you know, NX doesn't directly like solve for you, 836 00:45:22.920 --> 00:45:26.239 but but they're they're the kinds of problems that you're 837 00:45:26.280 --> 00:45:28.199 going to have when you have a large mono repo. 838 00:45:29.039 --> 00:45:31.320 And so yeah, this is fun to fund to just 839 00:45:31.360 --> 00:45:34.320 hear how people solve those kinds of things. But there's 840 00:45:34.360 --> 00:45:38.239 also the the polymono repose the best of two worlds. 841 00:45:39.559 --> 00:45:43.079 That that's a another NX champion is doing that, and uh, 842 00:45:43.480 --> 00:45:46.719 that just the the idea that you can have, like 843 00:45:46.719 --> 00:45:49.880 a large organization, you often have more than one mono repo, 844 00:45:51.119 --> 00:45:53.880 and that's you know that it's okay, and there's you know, 845 00:45:53.880 --> 00:45:57.000 there are ways to make that work nice. 846 00:45:57.320 --> 00:45:59.599 So like more than one mono repo as opposed to 847 00:45:59.719 --> 00:46:05.480 and with other mono repo tools mixed in, right, Yeah, yeah, 848 00:46:05.639 --> 00:46:07.360 I'm thinking probably the wrong way. 849 00:46:07.199 --> 00:46:18.079 So to contain himself, Yeah, only turning a little red. 850 00:46:19.840 --> 00:46:23.400 Like it's like like I has gotten ridiculously hot, and 851 00:46:23.400 --> 00:46:25.800 I think my air conditioning needs to get turned back 852 00:46:25.840 --> 00:46:27.119 on because I'm over here. 853 00:46:26.920 --> 00:46:31.719 Just like flushed, quite warm. It's quite warm. 854 00:46:31.800 --> 00:46:34.519 Yeah, so that's yeah. The merge cues is really interesting. 855 00:46:34.519 --> 00:46:38.039 I was

actually looking into because gethub has merge cues now, 856 00:46:38.079 --> 00:46:41.000 but they don't quite work the way I need them 857 00:46:41.039 --> 00:46:41.480 to work. 858 00:46:42.119 --> 00:46:43.840 I Mean, you mentioned that, and it's a shame you 859 00:46:43.880 --> 00:46:46.320 won't be there because there is a session on like 860 00:46:46.480 --> 00:46:50.880 how to set up get in, specifically get hub for 861 00:46:51.119 --> 00:46:55.079 like super large mono repos, which that one I'm also 862 00:46:55.199 --> 00:46:57.440 very excited about because how many times have you looked 863 00:46:57.440 --> 00:47:01.719 at a like large PR and trying to just make 864 00:47:01.840 --> 00:47:04.920 sense of not only the one PR, but then somebody 865 00:47:04.920 --> 00:47:07.960 else's PR and it's all just get history as a 866 00:47:08.000 --> 00:47:08.760 mass at that point. 867 00:47:09.320 --> 00:47:13.360 Yeah, yeah, exactly, well and just like yeah, it's when 868 00:47:13.400 --> 00:47:15.840 you have so many developers working together. Any tool you 869 00:47:15.880 --> 00:47:20.400 can do to sort of make the process easier is uh, 870 00:47:20.920 --> 00:47:23.159 is nice. That's why we're looking at merge cues because 871 00:47:23.159 --> 00:47:29.599 we have problems where sometimes you know, like you'll have 872 00:47:29.920 --> 00:47:33.280 two prs that get submitted at the same time and 873 00:47:33.320 --> 00:47:36.119 they both pass CI, but they when they get merged, 874 00:47:36.159 --> 00:47:36.880 they don't work. 875 00:47:37.199 --> 00:47:37.679 They fail. 876 00:47:37.840 --> 00:47:38.679 Yeah, they fail. 877 00:47:39.000 --> 00:47:40.480 Yeah, yeah, we we have. 878 00:47:40.559 --> 00:47:42.599 That with the NX repo, and like we we should 879 00:47:42.599 --> 00:47:44.119 have a merge cue on the NX repo. 880 00:47:44.480 --> 00:47:48.679 Yeah so so yeah, some of your users, uh, your 881 00:47:48.800 --> 00:47:50.719 enterprise users want that, please. 882 00:47:52.440 --> 00:47:54.719 Well, I sued to talk about our own code base, 883 00:47:54.840 --> 00:47:57.480 like we should have merge cues on our own basis. 884 00:47:57.199 --> 00:47:57.840 Can solve it. 885 00:47:57.880 --> 00:47:59.920 I mean, so like the get hab merchoes are, they're 886 00:48:00.079 --> 00:48:02.400 pretty close, but they don't like when I was looking 887 00:48:02.400 --> 00:48:05.719 in they didn't have enough hooks. And so one of 888 00:48:05.719 --> 00:48:08.480 our problems is that some of our some of our 889 00:48:08.519 --> 00:48:11.719 steps are really expensive to run, and so we were 890 00:48:11.760 --> 00:48:14.639 looking at it too as a way to reduce the 891 00:48:14.800 --> 00:48:16.880 number of times, for example, that we have to run 892 00:48:16.880 --> 00:48:20.400 our end to end suite. And so they didn't have 893 00:48:20.480 --> 00:48:24.400 hooks so that you could run like the like a 894 00:48:24.440 --> 00:48:28.880 pr check to say does the linting pass, does it compile, 895 00:48:29.159 --> 00:48:31.960 like does it build, and then get into the merge 896 00:48:32.000 --> 00:48:35.599 queue and then run the expensive stuff. It ended up 897 00:48:35.719 --> 00:48:38.280 doubling the number of times our end to end tests 898 00:48:38.280 --> 00:48:41.880 would run, as opposed to reducing the number of Okay, 899 00:48:44.880 --> 00:48:48.119 so but yeah, I think that hopefully they'll just keep 900 00:48:48.159 --> 00:48:50.639 developing in that space, because there were plenty of people 901 00:48:50.760 --> 00:48:51.920 that had issues out. 902 00:48:51.760 --> 00:48:53.760 On that to improve that process. 903 00:48:53.840 --> 00:48:57.639 But but yeah, anyways, Yeah, so it sounds like there's 904 00:48:57.639 --> 00:49:02.079 a lot of great topics at Monorepool World. So looking 905 00:49:02.159 --> 00:49:07.239 past Mono Repo World, what are some of the what's 906 00:49:07.280 --> 00:49:08.719 on the roadmap for NX. 907 00:49:09.480 --> 00:49:12.559 Yeah, there's a lot of things on the roadmap. I 908 00:49:12.559 --> 00:49:16.639 think we one of the things that has happened internally 909 00:49:16.760 --> 00:49:19.920 is like having a nice little discussion about how do 910 00:49:20.000 --> 00:49:25.400 we want NX to kind of grow and like grow 911 00:49:25.400 --> 00:49:28.199 beyond what our current user base is and what does 912 00:49:28.199 --> 00:49:30.920 that mean or some of the things that we do, 913 00:49:31.000 --> 00:49:37.559 so like a focus on just visam onboarding, simplifying what 914 00:49:37.920 --> 00:49:43.480 some of the complex product complex config could be project. 915 00:49:43.960 --> 00:49:47.960 The Crystal plugins honestly are one of the really nice 916 00:49:48.000 --> 00:49:52.960 ways to get towards that import as well SYNC. Like 917 00:49:53.039 --> 00:49:55.159 all these little features that have been building up all 918 00:49:55.199 --> 00:49:58.039 for the end goal of make it easy for people 919 00:49:58.119 --> 00:50:01.920 who are not necessarily going to want to dive deep 920 00:50:02.079 --> 00:50:09.840 into becoming an NX DevOps energy engineer or an NX engineer, 921 00:50:10.199 --> 00:50:12.519 Like they can just fix on the simple stuff, know 922 00:50:12.639 --> 00:50:14.079 the tool is going to be there to help them 923 00:50:15.239 --> 00:50:18.800 and just get back to building whatever they're building. 924 00:50:19.239 --> 00:50:22.679 Yeah, absolutely, because I think that that's the scariest part 925 00:50:22.840 --> 00:50:26.719 as a just a I'm a software engineer on my 926 00:50:26.800 --> 00:50:29.280 team and we're using NX, Like what does that mean 927 00:50:29.440 --> 00:50:34.800 to me? And just anything that can make that process 928 00:50:34.920 --> 00:50:38.880 more simplified, or you know, say you are like you're 929 00:50:38.920 --> 00:50:41.400 the tech lead and they're somebody says we should look

930 00:50:41.440 --> 00:50:46.599 into mono repos and how can you lower people's blood 931 00:50:46.639 --> 00:50:51.159 pressure with that process? Because it's it feels like this 932 00:50:51.360 --> 00:50:56.000 huge layer that you're putting in. Honestly, I don't have 933 00:50:56.079 --> 00:50:58.840 to think about NX very much in my day to 934 00:50:58.920 --> 00:51:01.760 day workflow, aside from and now I'm going to run 935 00:51:01.800 --> 00:51:03.639 another generator because I need a new lib for this, 936 00:51:05.000 --> 00:51:08.000 you know, because like once the executors are in place, 937 00:51:08.039 --> 00:51:11.559 once the pipeline is set up. I think the other 938 00:51:11.599 --> 00:51:14.039 command I run the most is NX reset, you know, 939 00:51:14.119 --> 00:51:17.079 like because sometimes when you're switching branches, NX is like, 940 00:51:17.159 --> 00:51:20.280 what did you just do? And it tells you run 941 00:51:20.400 --> 00:51:22.880 NX reset. It's super easy, right, So it's like this 942 00:51:23.199 --> 00:51:26.800 very like it's a very ergonomic tool for me to 943 00:51:26.960 --> 00:51:29.639 use just in the trenches writing. 944 00:51:29.320 --> 00:51:30.000 Code every day. 945 00:51:30.119 --> 00:51:31.159 Sometimes it's easy. 946 00:51:31.639 --> 00:51:35.239 Sometimes sometimes you do it doesn't do anything at all, right, 947 00:51:35.679 --> 00:51:38.039 But I figured out now that it's because I'm stashing 948 00:51:38.039 --> 00:51:41.800 and unstashing stuff and I have new libs or something 949 00:51:41.880 --> 00:51:42.719 and they. 950 00:51:42.599 --> 00:51:44.599 Just kind of sit around. But yeah, yeah, I mean 951 00:51:44.719 --> 00:51:45.519 NX is awesome. 952 00:51:45.960 --> 00:51:49.480 Yeah, yeah, I think the whole idea of mono repos 953 00:51:49.519 --> 00:51:52.760 and like NX in general is that you're you take 954 00:51:52.880 --> 00:51:57.679 the complex like pieces, the cantig and the tooling and 955 00:51:57.719 --> 00:51:59.719 all that, and instead of doing it in lots of 956 00:52:00.360 --> 00:52:03.039 different ways on different repos you put in one place 957 00:52:03.119 --> 00:52:06.559 and you try to like handle it well in one place, 958 00:52:07.239 --> 00:52:09.920 and then you can forget about it and everyone else 959 00:52:09.960 --> 00:52:13.000 can can do the other things that the more important things. 960 00:52:14.639 --> 00:52:17.360 After a while, it just becomes like best practice, like 961 00:52:17.800 --> 00:52:20.679 should make a lift for that, should make it, and 962 00:52:21.039 --> 00:52:24.239 you typically don't go outside of that afture where to 963 00:52:24.280 --> 00:52:25.960 make so supervise. 964 00:52:26.880 --> 00:52:30.079 Yeah, I'd say the most conversations we have like bumping versions. 965 00:52:30.119 --> 00:52:33.880 Obviously that's probably a big like that that sometimes is 966 00:52:33.920 --> 00:52:35.119 a bigger lift. 967 00:52:36.800 --> 00:52:37.000 Then. 968 00:52:38.039 --> 00:52:40.719 I mean, it's like bumping versions of anything. It's kind 969 00:52:40.760 --> 00:52:43.079 of like it's a present. You're going to open it 970 00:52:43.119 --> 00:52:45.440 and you're gonna find out just how big that present is, 971 00:52:46.480 --> 00:52:49.719 how much my touching here? And for the most part, 972 00:52:49.800 --> 00:52:52.639 the version bumps go pretty smoothly. If you've got a 973 00:52:52.679 --> 00:52:55.559 large enterprise app with a lot of like legacy dependencies, 974 00:52:55.639 --> 00:53:01.400 it might not be as easy, but yeah, it's uh 975 00:53:01.639 --> 00:53:03.320 for the most part, like for the day to day, 976 00:53:03.360 --> 00:53:06.239 it's just it's a very ergonomic tool to use, and 977 00:53:06.280 --> 00:53:09.480 then what we get out of it is it figures 978 00:53:09.480 --> 00:53:11.679 out how to build things for us and how to 979 00:53:11.760 --> 00:53:15.440 run things in order, and it caches things and you know, 980 00:53:15.519 --> 00:53:17.719 it's like it does all of this stuff that just 981 00:53:17.800 --> 00:53:20.239 kind of makes my life a lot easier, so. 982 00:53:20.920 --> 00:53:24.639 Right, and then and then it's also like when we 983 00:53:24.840 --> 00:53:27.840 use NX and you're you're allowing an X to make 984 00:53:27.880 --> 00:53:30.480 things faster for you without you thinking about it. It 985 00:53:30.519 --> 00:53:33.840 allows n X. The NX team is constantly working on 986 00:53:33.880 --> 00:53:37.360 improving that process for you. And then as so in 987 00:53:37.480 --> 00:53:42.320 order to like get the next like great like performance boost, 988 00:53:42.800 --> 00:53:44.639 like all you need to do is bump your version 989 00:53:44.679 --> 00:53:47.280 of n X and then and it's faster without you 990 00:53:47.360 --> 00:53:49.440 having to think about it and maintain it yourself and 991 00:53:49.440 --> 00:53:52.199 research it yourself. It's like, okay, I'll just use the 992 00:53:52.199 --> 00:53:55.400 next thing and it'll be better and faster exactly. 993 00:53:55.559 --> 00:53:56.920 Well, and you have a whole team of deads and 994 00:53:56.960 --> 00:54:00.079 that's literally what they do, like that's their job all day. 995 00:54:00.440 --> 00:54:03.440 Is to make a tool that makes those things faster 996 00:54:03.559 --> 00:54:08.079 and better so that every engineer and every company across 997 00:54:08.119 --> 00:54:11.880 the world doesn't have to do that themselves. So so yeah, 998 00:54:11.880 --> 00:54:14.239 I think that's really that's really great. I had a 999 00:54:14.239 --> 00:54:18.400 thought and then it has completely left my head. So well, 1000 00:54:18.440 --> 00:54:20.559 I wanted to ask about So one of the one 1001 00:54:20.599 --> 00:54:24.159 of the paid features of NX is nx cloud. H 1002 00:54:25.199 --> 00:54:29.320 So what does nx cloud give people or give like 1003 00:54:29.480 -->

00:54:32.679 companies that NX itself cannot. 1004 00:54:32.840 --> 00:54:37.840 So NX itself is open source UH terminal tool UH 1005 00:54:37.960 --> 00:54:41.119 that that can manage your manage your local mono repol. 1006 00:54:41.760 --> 00:54:47.320 Nx cloud is the CI product that helps improve the 1007 00:54:47.480 --> 00:54:50.599 give you let's see, let me get the tagline right. 1008 00:54:51.360 --> 00:54:56.199 So and nx cloud helps give you like speed features 1009 00:54:56.599 --> 00:55:02.639 and gives you like more reliability in your CI. So 1010 00:55:03.119 --> 00:55:07.159 the speed kind of features are caching in parallelization with 1011 00:55:07.280 --> 00:55:14.000 paralyzation is the agent's feature. And then reliability gives you 1012 00:55:14.039 --> 00:55:19.079 things like automatically retrying flaky tasks, automatically detecting flaky tasks 1013 00:55:19.079 --> 00:55:23.800 and retrying them and and all of those. Both of 1014 00:55:23.800 --> 00:55:27.800 those like types of features happen without you needing to 1015 00:55:28.519 --> 00:55:33.239 have a whole dedicated team, like reconfiguring your CI process 1016 00:55:33.360 --> 00:55:37.679 on every PR. So the nx cloud product will do 1017 00:55:37.760 --> 00:55:40.280 that for you and say this is the most efficient 1018 00:55:40.320 --> 00:55:46.119 paralyzation strategy for this particular PR. Not just like at 1019 00:55:46.119 --> 00:55:47.920 this on Master at this moment in time. It's for 1020 00:55:48.000 --> 00:55:50.199 this particular set of code that you're passing in. We 1021 00:55:50.239 --> 00:55:53.960 can reconstruct, reconstruct the whole process to make it as 1022 00:55:53.960 --> 00:55:56.239 fast as possible for this one this one thing. 1023 00:55:57.800 --> 00:55:59.480 Yeah, So NX cloud. 1024 00:55:59.199 --> 00:56:04.719 Has like like like that is easy task to replicate. 1025 00:56:04.840 --> 00:56:07.480 So yeah, and so there's like a whole like like 1026 00:56:07.840 --> 00:56:11.119 different levels of of nx Cloud that you can subscribe 1027 00:56:11.119 --> 00:56:15.960 to you there's the the SaaS version where you're they're 1028 00:56:16.039 --> 00:56:19.320 using the agents that it's uh like on the on 1029 00:56:19.400 --> 00:56:23.559 the cloud. There's the enterprise version where you can optionally 1030 00:56:23.960 --> 00:56:27.239 put your your nx Cloud agents run them on your 1031 00:56:27.239 --> 00:56:31.679 own infrastructure. And I guess those are two main things, 1032 00:56:31.719 --> 00:56:33.719 and then there's different levels of like how much you're 1033 00:56:33.800 --> 00:56:36.639 using the service or not with within those those two 1034 00:56:37.559 --> 00:56:38.320 kind of options. 1035 00:56:39.119 --> 00:56:44.199 We are also coming out with a new product, which. 1036 00:56:43.960 --> 00:56:49.679 Is it's not cloud, it's it's like extension basically extensions 1037 00:56:49.719 --> 00:56:53.880 for the n X Terminal tool. We're calling it power Pack, 1038 00:56:54.960 --> 00:56:57.760 and it's just in the beginning stages and we're you know, 1039 00:56:57.760 --> 00:56:59.639 it's going to grow on that. But the idea is 1040 00:56:59.679 --> 00:57:03.440 for for people who who want some kind of enterprise 1041 00:57:03.920 --> 00:57:07.440 focused features, and but they don't. 1042 00:57:07.280 --> 00:57:08.960 Want to go through the whole. 1043 00:57:10.360 --> 00:57:14.280 Like what's it acquisition process whatever, the process of like 1044 00:57:14.599 --> 00:57:17.760 getting the like invoices and stuff, going through approvals and 1045 00:57:17.800 --> 00:57:18.320 all that stuff. 1046 00:57:18.320 --> 00:57:20.519 You can just you can just put in a. 1047 00:57:20.360 --> 00:57:25.039 Credit card and and just get these these extra features 1048 00:57:25.599 --> 00:57:28.559 for the for the n X terminal. And so some 1049 00:57:28.599 --> 00:57:31.360 of these things that that are coming, uh, just they'll 1050 00:57:31.400 --> 00:57:33.679 be they'll already be out by the time this show airs. 1051 00:57:34.519 --> 00:57:37.559 We we have some of the features of power Pack 1052 00:57:37.599 --> 00:57:40.760 are going to be conformance, which is basically the way 1053 00:57:40.840 --> 00:57:45.360 a way to write language agnostic like lint rules basically 1054 00:57:45.480 --> 00:57:47.840 like like es lint, but not just for a JavaScript, 1055 00:57:48.360 --> 00:57:52.079 for like Java and other other languages. And you'll you'll 1056 00:57:52.119 --> 00:57:53.320 be able to write your own so it'll come with 1057 00:57:53.360 --> 00:57:55.039 some default rules and you'll be able to write your 1058 00:57:55.039 --> 00:58:03.360 own rules. And then there's and owners plugin that comes 1059 00:58:03.360 --> 00:58:07.320 with Powerpack, and that one will be for basically you 1060 00:58:07.320 --> 00:58:11.000 can instead of in your typical like GitHub code owners file, 1061 00:58:11.199 --> 00:58:14.719 you can you write rules of like based on the 1062 00:58:14.719 --> 00:58:17.440 file system of like this folder belongs to this team, 1063 00:58:17.480 --> 00:58:20.039 this fold and belongs to this other team. So instead 1064 00:58:20.079 --> 00:58:22.159 of that, you can you can do well so you 1065 00:58:22.199 --> 00:58:25.440 can also write rules about the file system, but you 1066 00:58:25.480 --> 00:58:28.840 can also write rules based on this project belongs to 1067 00:58:28.880 --> 00:58:32.280 this team, and so if that project moves around, you 1068 00:58:32.280 --> 00:58:36.039 don't have to rewrite your ownership because it's it's this project, 1069 00:58:36.239 --> 00:58:38.480 whatever it's called, and everything that belongs to this project 1070 00:58:38.480 --> 00:58:41.079 belongs to this team. And you can also say this 1071 00:58:41.239 --> 00:58:45.239 tag like the way we're the whole NX tagging structure, 1072 00:58:45.239 -->

00:58:48.639 you can say anything that's tagged with util belongs to 1073 00:58:48.639 --> 00:58:51.360 this team or whatever whatever your tag is, you can 1074 00:58:51.400 --> 00:58:54.519 say this, and then you just update your tagging on 1075 00:58:54.639 --> 00:58:56.559 a different project and it changes the ownership. 1076 00:58:57.079 --> 00:58:58.559 So that's nice. 1077 00:58:58.599 --> 00:59:00.760 I think we probably all have the big gross code 1078 00:59:00.760 --> 00:59:01.800 owners file that. 1079 00:59:05.000 --> 00:59:09.199 Is very cool, so that that ownership project uses the 1080 00:59:09.320 --> 00:59:12.039 NXCYNC command to update the code owners file, so so 1081 00:59:12.079 --> 00:59:15.840 it'll work with GitHub or get lab or or bit. 1082 00:59:15.760 --> 00:59:19.840 Bucket just out of the box. That's nice. 1083 00:59:20.159 --> 00:59:22.519 And then we're also doing we have a new kind 1084 00:59:22.519 --> 00:59:28.559 of like caching database that's built into the n x 1085 00:59:28.599 --> 00:59:32.480 c l I to make cashing faster. And uh so 1086 00:59:32.519 --> 00:59:35.320 that's just for everybody that's open source, but there if 1087 00:59:35.320 --> 00:59:39.039 you're if you're using like a custom cash storage mechanism 1088 00:59:39.639 --> 00:59:43.840 that's like next year. Sometimes that's that's no longer going 1089 00:59:43.880 --> 00:59:46.199 to work because of this this database, because we're not 1090 00:59:46.199 --> 00:59:49.400 going to be storing the cash in on the file system. 1091 00:59:49.679 --> 00:59:52.079 We're storing it in a local database, which you know 1092 00:59:52.119 --> 00:59:54.719 makes it faster for for almost everybody, but people who 1093 00:59:54.719 --> 00:59:57.480 have a custom caching thing doesn't work. So if you 1094 00:59:57.519 --> 01:00:01.559 have a custom caching solution, then you'll you can use 1095 01:00:01.599 --> 01:00:05.239 power pack and then still use a custom cash location. 1096 01:00:06.440 --> 01:00:07.119 To do that. 1097 01:00:07.960 --> 01:00:09.079 Nice. Nice. 1098 01:00:09.239 --> 01:00:11.920 So yeah, and I think that you know, I know 1099 01:00:12.039 --> 01:00:17.119 with with nx cloud, one of the reasons that people 1100 01:00:17.159 --> 01:00:21.119 would want to use it is because because of the caching. 1101 01:00:22.400 --> 01:00:23.320 Because of. 1102 01:00:24.800 --> 01:00:27.840 It under because it understands the project graph and can 1103 01:00:27.880 --> 01:00:32.360 cash things that haven't changed. You end up running fewer 1104 01:00:32.400 --> 01:00:33.679 steps in your pipeline. 1105 01:00:34.159 --> 01:00:36.239 Yeah ye, which. 1106 01:00:36.239 --> 01:00:40.639 So a lot of times it sort of balances out 1107 01:00:40.760 --> 01:00:44.880 that the expense you pay to get an ex cloud 1108 01:00:45.679 --> 01:00:48.039 is saved on your CI. 1109 01:00:48.039 --> 01:00:51.800 Run time anyway. So yeah, it's it's. 1110 01:00:51.599 -->

01:00:56.880 Definitely worth exploring. You know, it can be I know 1111 01:00:57.000 --> 01:01:02.639 that there could be a processes with enterprise organizations. It's 1112 01:01:02.679 --> 01:01:06.280 nothing is easy when it comes to getting per strengths 1113 01:01:06.280 --> 01:01:07.639 to open, right. 1114 01:01:07.920 --> 01:01:13.159 Yeah, So yeah, but the pricing model is actually super affordable, 1115 01:01:13.280 --> 01:01:14.800 so yeah, be shocked. 1116 01:01:15.400 --> 01:01:18.199 Yeah, and really, once you compare it against what a 1117 01:01:18.239 --> 01:01:21.079 lot of companies are actually spending on c I, it's 1118 01:01:21.159 --> 01:01:27.760 like yeah, yeah, yeah, it's a it's it's an interesting 1119 01:01:27.800 --> 01:01:28.960 exercise to do. 1120 01:01:31.039 --> 01:01:31.280 Well. 1121 01:01:31.280 --> 01:01:33.039 And they if if you're wanting to do like an 1122 01:01:33.119 --> 01:01:38.480 enterprise license, we will have a whole team like work 1123 01:01:38.519 --> 01:01:41.239 with you too in like like do like a demo 1124 01:01:41.559 --> 01:01:44.400 phase where we prove that hey, this is how much 1125 01:01:44.400 --> 01:01:48.239 money you're actually going to save on your actual code, 1126 01:01:48.400 --> 01:01:50.320 and then they set it all up before you actually 1127 01:01:50.559 --> 01:01:52.360 fully commit and say, okay, yes we're gonna pull the 1128 01:01:52.360 --> 01:01:53.639 trigger on this exactly. 1129 01:01:53.679 --> 01:01:56.719 Get you those like hard numbers or British numbers that. 1130 01:01:56.679 --> 01:02:00.280 You need because the the you know, people that pay 1131 01:02:00.320 --> 01:02:03.920 the pay the bills, don't really care about anything except 1132 01:02:03.920 --> 01:02:06.639 the actual numbers. So if you can get actual numbers, 1133 01:02:06.639 --> 01:02:12.000 it's a lot more helpful. What are ways that people 1134 01:02:12.159 --> 01:02:18.039 can get involved nx's open source? Do you have people 1135 01:02:18.079 --> 01:02:22.880 from the community contributing? Are there ways for people to 1136 01:02:22.920 --> 01:02:27.360 be part of NX? I mean aside from you know, 1137 01:02:27.480 --> 01:02:29.480 applying for a job and getting a job at NX. 1138 01:02:29.840 --> 01:02:34.480 Sure, Yeah, absolutely, so. 1139 01:02:35.920 --> 01:02:40.559 Dev slash community lists out a bunch of things, so 1140 01:02:41.719 --> 01:02:44.840 you can join us on discord. We have discord where 1141 01:02:45.039 --> 01:02:48.840 like people like share questions and help each other with problems. 1142 01:02:49.800 --> 01:02:52.920 We have a Twitter account or x account, I guess, 1143 01:02:53.679 --> 01:02:57.920 and a monthly newsletter and YouTube channel, so all those 1144 01:02:57.920 --> 01:03:02.599 places to follow us and find things up. And yeah, 1145 01:03:02.639 --> 01:03:05.280 we're open source, so you can you can you file 1146 01:03:05.320 --> 01:03:08.280 issues and suggest things there as well. 1147 01:03:08.960 --> 01:03:12.719 Nice. Nice Yeah for Twitter. 1148 01:03:12.800 --> 01:03:15.679 Yeah, I don't think. Yeah, I feel I feel dirty 1149 01:03:15.719 --> 01:03:17.440 calling it X. It's like that's not X. 1150 01:03:17.719 --> 01:03:25.519 Same and I can I can say with all honestly, 1151 01:03:25.559 --> 01:03:29.679 I've never met, uh somebody from NX that isn't an 1152 01:03:29.679 --> 01:03:32.400 approachable nice person. Uh. 1153 01:03:32.400 --> 01:03:34.079 So if you do find yourself. 1154 01:03:33.679 --> 01:03:37.800 At Mono Repo World, definitely say hi to the team. 1155 01:03:38.000 --> 01:03:40.760 I've reached out to people on Discord to ask very 1156 01:03:40.760 --> 01:03:44.280 specific questions, like I've reached out to Craigory quite a 1157 01:03:44.280 --> 01:03:49.159 bit about his NX or his dot net generator, yeah, 1158 01:03:49.159 --> 01:03:53.320 his plug ins. So yeah, like there's everyone is very 1159 01:03:53.320 --> 01:03:57.199 approachable and so yeah, if you have questions, definitely check 1160 01:03:57.239 --> 01:04:00.239 out Discord. If you can make it to Mono Repo Old, 1161 01:04:00.239 --> 01:04:02.519 you're a very lucky person. It's always a good time. 1162 01:04:03.119 --> 01:04:05.559 Most I'm sorry, I almost forgot the most important question. 1163 01:04:05.639 --> 01:04:06.559 Will there be karaoke? 1164 01:04:07.920 --> 01:04:08.039 Uh? 1165 01:04:08.320 --> 01:04:10.719 Yeah, I think, I think I think Jeff will like 1166 01:04:11.239 --> 01:04:12.960 burn down the building if it's not karaoke. 1167 01:04:14.159 --> 01:04:15.440 They will definitely be karaoking. 1168 01:04:16.480 --> 01:04:17.800 Very nice. 1169 01:04:18.960 --> 01:04:22.400 I'll do some sort of protest, right right, right, yeah, yeah, 1170 01:04:22.480 --> 01:04:25.480 the karaoke is always a good time n X. 1171 01:04:25.599 --> 01:04:28.079 The NX team knows how to have a good time 1172 01:04:28.639 --> 01:04:29.280 with singing. 1173 01:04:29.760 --> 01:04:30.320 Absolutely. 1174 01:04:32.519 --> 01:04:36.960 There may have been a couple messages in slack already. 1175 01:04:37.320 --> 01:04:38.559 It's like karaoke is there? 1176 01:04:38.639 --> 01:04:38.840 Right? 1177 01:04:38.920 --> 01:04:41.039 We got karaoke set up right. 1178 01:04:43.800 --> 01:04:48.400 We didn't forget the most important part, did we. Well, 1179 01:04:48.400 --> 01:04:52.239 thank you so much for joining us today. I'm looking 1180 01:04:52.280 --> 01:04:56.239 forward to really just everything that's coming, everything on the 1181 01:04:56.280 --> 01:05:01.239 road map. And yeah, so thank you for joining us 1182 01:05:01.880 --> 01:05:04.400 to the listener. Thank you for tuning in. If you 1183 01:05:04.599 --> 01:05:07.239 like this episode and you'd like to hear more episodes 1184 01:05:07.280 --> 01:05:09.800 that are equally as awesome, be sure to subscribe to 1185 01:05:09.840 --> 01:05:12.599 the podcast and we'll catch you next time. 1186 01:05:13.119 --> 01:05:14.599 All right, thanks, thank you. 1187 01:05:15.199 --> 01:05:15.400 Yeah. 1188 01:05:17.639 --> 01:05:20.440 Hey, this is Prestom. I'm one of the ng Champions writers. 1189 01:05:20.800 --> 01:05:23.039 In our daily battle to crush out code, we run 1190 01:05:23.079 --> 01:05:27.199 into problems and sometimes those problems aren't easily solved. NGCOMF 1191 01:05:27.199 --> 01:05:30.719 broadcasts articles and tutorials from angie champions like myself that 1192 01:05:30.800 --> 01:05:33.360 help make other developers' lives just a little bit easier. 1193 01:05:33.920 --> 01:05:37.920 To access these articles, visit medium, dot com, forward Slash NGCOMF. 1194 01:05:39.079 --> 01:05:41.280 Thank you for listening to the Angular Plus Show in 1195 01:05:41.519 --> 01:05:45.320 Chcoff podcast. We'd like to thank our sponsors, the NGCOMF 1196 01:05:45.440 --> 01:05:49.360 organizers Joe Eames and Aaron Frost, our producer Gene Bourne, 1197 01:05:49.480 --> 01:05:52.880 and our podcast editor and engineer Patrick Kay's. You can 1198 01:05:52.880 --> 01:05:59.679 find him at spoonful ofmedia dot com. 1199 01:06:00.159 --> 01:06:03.719 The Retina in a potting