So,

e, do you think you're impatience, i should say, impatience you're a aste for repeating work is part of what made you a good programmer?

Absolutely. I think it's almost pathological, actually. Ah, thad, i have such an aversion to doing the same thing twice that, i mean, not that it's that unique. I think tha, lots of programmers have it, that i'll sometimes go overboard in just trying to prevent that from happening again. And that's where i need some restraint of saying like, ok, i've only seen this problem once. I might fear that i'll see it again. But until i actually see it again, let's let's not over rest here and build some huge hanking framework to to do it again. But i usually match one of the things i like them most actually, in terms of working on open service and on ruby an rails, has been pattern matching in the work that i already do. So it's not so much that the thing is exactly the same, but there's a pattern. Theres an outline that's similar. And when i spot those similar outlines and i come up with an extraction that kind of makes that work go away next time that something has a similar shape and outline, that is really where i hit the jack pot in terms of personal satisfaction with the work. I love just spotting these things where i think to myself, if i had to write base camp again from scratch to i'd be so much better off, because i'd solve all these problems. I'd put all these tools into the tool kit of base cammonet. This is one of the things with negative visualization where i have thi, i don't know, nightmare or fantasy. Evr, you want to put it where, like, we lose it. All right. I have to do it all over again from scratch. We have to write base cam again. It's just me and jason and whatever. And ike, we don't have the 50 people any more. We don't have all the money, and, like, whatever, like, where am i can. I do it. I imagine this whole thing, and i've packed this back tak. I gave a talk at the rails compay last year about the survival kit that rails ays for me, i think of like, if everything goes wrong and i have to start over from scratch, will i at least have the tools to survive? And that's my mission for rails. An's always been, if i had to reboot fully, i don't have a staff, i don't have other programmes, i don't know, i just have myself. Self sufficiency, as we talked about at the beginning, there has been just such an important driver to the pathological level. And i mean, good things have come out of it, and sometimes not so good things come out of it too. I think it's, it's, thereare good things to think about, like, how can you rely on and depend on other people? But he i carry that cross and deal with that, and just try to maximie the benefits and minimize the drawbacks of it. But one of the benefits have been just this focus on creating truly productive tools that allow tiny teams to do amazing things. Because i want to enable other people who want to do it like we did it, tiny team, no external money to have a chance to compete. Becauseyou didn't use to be that way, right? If you wanted to start a web start up, 95 or whatever, you had to spend 200 grand under oracle license just to get a data base going. That was a terrible time to get things going. Now it's never been easier. And i just love that. I mean, it's funny, we're lowering the berries of entry, which in some sense makes it perhaps harder, because there's more people competing. But to me, there's something fairer about that. And i can imagine myself in that situation. I can imagine myself e ing, doing all the negative lisation, and thinking, it's going to be ok.