And most ideas ust let you do that rit. So that's arefractuin because the cod behavior is changing. Youre doing it for pure coordinative reasons. And then, of course, once you have understood what everything does, then you can put everything back. You cn ca tit like control or just, you know, delet our local branch. That is really something that you do. So this is something i practise with students in class. So that that's alevel. But of course, this is a long game, because many developers are not the university any more. And so also we're doing something called code reading clubs. Were professionelswhere people come in. We have open and free on line coach reading clubs. Every month. You come into the coat training club. And we, we, we the facilitators. We are wit a group of us. We have a piece of sorsco to study, and then we read it together, and we do some exercises around the code, and we discuss otwys this hard, what strange syntactic consens are these em and then this way we can learn together. So that's also something that some of your audience might be interested joining, or starting in your own company. You don't have to participate an hour cod training clups. You can also do thi together with skill workers, you come to get together every two or three weeks, and you read a piece of source code, and then definitely, you know, with practice, you will get better. I

love that, and i think that's a really great way to welcome new people who are maybe just learning how to code as well. One challenge i think that i heara, that is kind of a consistent thread, is that a lot of times a it's hard to almost sell the value of reading where it's, you know, sometimes people still erroneously measure a productivity based on the number of lines you committed, or or features you show. Said that nature, yes. And so we also have a management challenge where, if you're spending too much time, you know. Or i've seen this before, like we have, we almost have to train some of the developers we have at corybites of it's not just keyboard time. It's not just the amount of time that you're typing that, you know, counts. So how do you think addressing some of the corporate culture challenges too?

Yes, this so this is a more genari question, right? This is also true, for example, for refractoring, people are often complaining, and my husband is also developer, hes aways, like, i want to clean up our coat beds, but my manager only cares about, like, launching features. I have no time to lon's features g in clean up. And for testing, i think, in testing. Soi slightly getting better, but i think we were maybe ten, 20 years ago, also, at the situation people like that, we have no time for testing, or testers will test as o kno users or user testing. We have no time to write outomatee tests. Testing is getting a little bit better, but i think wein refractoring al so you have this challenge. I think with coat reading, it might be a little bit easier, because apart from doing something like a coat reading club, whe youre like litelly carving out time to practise coat reading. Ote reading is something youaready writ if your there's an error, there's an issue that you have to tackle, you have to read, maybe even your own code. It's not even necessarily negazie code. You have to read your own code to figure out, oiet, this class is not initialized. Where? Where is this method called? Where should it have been initialized? So code reading is something you ro to do already often. So if you would learn a few strategies, for example, sing a coage reading club, or from a bol or from other from other sources, if youre reaty know a few strategies, then you can sort of quickly apply t em. Because coage reading youare doing is all the time. Another context, or coage reating, happens is youre doing a coage review. So i am reviewing your code for in a poor request, or in another method you might use in your company, i have to read the cods. And this is a specific form of coage reading. Because maybe if i do this, one gets up in a poor request, treat the whole cod base. Maybe i'm only reading the changes. So than i'm interestingly, sort of buzzling together my prior knowledge of the coad base and a few small modifications. So that's yet another form of cod reading. So once you know a fou strategy, you can apply it everywhere. You know, i would not necessarily recommence printing out your entire coad base, stapling it together and sit in the coffee room for everyone to see, whatare you doing studyof our code? Ri tat that. Maybe your manager get slikhe yo upset. And maybe also, that will be somewhat reasonable.