"Been all. What is your developer? Origin Story That's a great question I guess I got started when I was a kid my birth. My parents have computer or computer adjacent jobs and I was sort of always fascinated so I started programming when I was I was very career young. I think I wrote my first Java program when I was age. Twelve and one of the things does mean is I've been using eclipse for more than half of my life which is always Funny to me but really it came from a instinct to sort of Tanka to really understand how computers walked. And that's that's sort of carrying me through My entire life really like what are the things is that I find myself like messing around with software in my hubby time. As much as you when I'm walking and that has been a really consistent throughout my life And so you're like where I am today. Like is really a product of having been fascinated by computers in my entire life and having sort of manipulated and what with them for a really really long time. I think you're so lucky because I got introduced to computers when I was in high school. My parents encouraged me to take computer science classes and so I felt it was lucky Dietz. Who get that experience early on but for you to know so early on that you enjoyed it and wanted to make a career of it is just something that I feel is still kind of rare in our industry free? Yeah it's I I don't know I find that most of the people I talk to you. like found owned computer science like much much later in their life so like even high school is sort of like relatively early rights are like I know some folks who didn't really look at programming at all until like the second or third. He is of the undergraduate degrees even like later in life career switched switched from a different profession through boot Camp Lasalle teaching or whatever it might be And so yeah like I like. Excuse me I in a sense. Consider myself to be very lucky that I like sort of have developed technical superpowers superpower's just from having been able to do it from a very very early age. That's great well. Our SPEC is a very love framework in the Ruby Community of course and so I would absolutely love to hear how you got involved. Yeah that's A. That's a great question. I'm so I got involved through aspect actually while I was studying full my computer. Science degree Sawyer Iowa's like alongside my degree like teaching myself ruby learning how to build rails applications because Like the community. Not at that time was sort of like just beginning to really exploited out onto the internet like I remember being Sawyer so fascinated by all of the conference Tokes That will sort of coming out of the community. And like the learning and teaching and sort of like niceness that was associated with that And so one day while I was working on rails APP and writing tests with us back doc I encountered a bug and I like looked into the source code of us back and what how how to fix it and sent a poor request request but along the way I was finding lots and lots of places in the SPEC Code base that could like we're meetable to factoring And so I spent maybe like a good six to eight weeks of my life just as a college student. I had loads of free time. I'm like just refer factoring The tunnels of aspect and I ended up sending them so many. Poor quests that essentially they will like. Hey we're going to give you a commitment because these greats and we would like we would like for you to keep doing this and stop bugging us like please please just merge these yourself And so I ended up basically just joining the cool team through like share application an off Wanting to make it better. So where did you gain that experience that you were able to look at the arse back out source code and be able to pinpoint pinpoint the possible re factories that you could do. Did you gain that from school or did you have other open source. Experience Neither I oh this is this is like this is a somewhat difficult question to you on Sir. But essentially essentially just sort of like an aesthetic for wanting to remove jeff location or things that were proving hot to change And so like actually back back at that point in time aspect had Code climate mounted in all of Repos and basically just sort of took it upon myself to just stop moving the code climate grades of the entire base like upwards towards those as really sort of using the insights code climate was providing To find those places and then sort of just thinking about house collapse things together or create new abstractions or whatever it might be right and like at the time Really Oh code. Climate was doing thing was running the flag and flame gems like rubies solo spaces and those just spot sort of like joop located Covered all oil like curd. That is extremely complex so like I was like. Oh yeah this. Totally is a three hundred line function with Grizzly two nested. If statements we can probably make that like like less nested and shorter rate and so like really it was it was an application of stuff I had being directly taught Through those aforementioned sort of like Ruby conference talks I had been watching so there was this like very sort of tight. feedback cycle between the things. I was learning and getting to apply them That was like a very unique experience. I think that was really interesting. I think that's great because even though that happened to you in college I mean we're GonNa get into Ruby format. It just seems to be a pattern throughout your career so aside from the sixty eight weeks that you contributed during your university time What contributions are you most proud of with our SPEC so basically I think perhaps the most interesting thing that happened to us? Back in my tenure I guess there are two things so one is when I joined the aspect team aspect was still on major Russian to And now it's on major three and I did a lot of the work along with the other team members at the time to actually like like deliver that and so I was sort of on the front lines of implementing some of the new keywords and doing method clean Alpina. Actually a big part of it was just deprecating code in a way that didn't break people's test suites which is what we use. The major version for so like aspect has a very strict adherence to semantic brushing and gut. Like when it is people's test suites you like literally cannot break them right like like breaking someone's suite would be like a sort of horrifying thing for aspect to do and so part of it. Frankly just what that people couldn't really detect to make sure that moving from two to three was a seamless as possible in terms. uh-huh of tangible stuff. People have actually probably seen I managed the sort of like rails compatibility of aspect through reversion five and up to version six point zero including implement implementing the compatibility for rail system test which replaced placed feature specs. Basically wholesale and like the system tasks are just like way better than feature specs F. O. were And so like I'm really proud of that one because it sort of took a standardized piece of work that was done by the rails team and specifically I lean you should tell and Sort of integrated with AAs back and that was a lot of fun because like it was done very collaboratively. It wasn't it just sort of me. In a lab that one was like reaching out to folks who have applications like test prototypes and see what upgrading onto those might look like and whether or not there are bugs and that sort of thing but yeah so like broadly. Speaking most of my tenure on our SPEC was either a fixing bugs in aspect all SPEC mocks or maintaining aspect rails through Russians five and up"