Valentino Stoll

Oh, there you go.

Oh, there you go.

Sure. Yeah, I mean... IRB is basically just a REPL. You give it input and it'll evaluate the Ruby that you give it, analyze the syntax of it, and then directly show you the output for whatever that it is that you give it. So people work in REPLs all the time. If you open up any console, that's a REPL in a bash shell, basically. But Ruby's IRB kind of has a hierarchy to it.

Sure. Yeah, I mean... IRB is basically just a REPL. You give it input and it'll evaluate the Ruby that you give it, analyze the syntax of it, and then directly show you the output for whatever that it is that you give it. So people work in REPLs all the time. If you open up any console, that's a REPL in a bash shell, basically. But Ruby's IRB kind of has a hierarchy to it.

that breaks all the different pieces of it into little modules that then pipe it through as it's going through and evaluating just the strings that you're giving it. And it does that in real time. And it does that basically in what they call a session and wraps that in a context and then evaluates it inside of a binding, which is really the underpinnings of Ruby code

that breaks all the different pieces of it into little modules that then pipe it through as it's going through and evaluating just the strings that you're giving it. And it does that in real time. And it does that basically in what they call a session and wraps that in a context and then evaluates it inside of a binding, which is really the underpinnings of Ruby code

Ruby's own core evaluation is the binding object. And then through the binding, it can basically compile Ruby on the fly into low-level code and do whatever it is that you tell it to do. You know, IRB, it's kind of like what gets you really into Ruby, right? You go and you're trying to learn a new, like try and learn any new language, even JavaScript as an example.

Ruby's own core evaluation is the binding object. And then through the binding, it can basically compile Ruby on the fly into low-level code and do whatever it is that you tell it to do. You know, IRB, it's kind of like what gets you really into Ruby, right? You go and you're trying to learn a new, like try and learn any new language, even JavaScript as an example.

You'll go and what do you do is you open up the JavaScript console and you try and play around and move elements around or, you know. try and be the first to purchase a pair of sneakers or something like that. But, you know, learning Ruby is so easy. You don't do the same thing. You open up an IRB session and they just type anything that you want and you can play around with the language.

You'll go and what do you do is you open up the JavaScript console and you try and play around and move elements around or, you know. try and be the first to purchase a pair of sneakers or something like that. But, you know, learning Ruby is so easy. You don't do the same thing. You open up an IRB session and they just type anything that you want and you can play around with the language.

It's pretty powerful. Yep, absolutely.

It's pretty powerful. Yep, absolutely.

So coming into this, definitely the customization part.

So coming into this, definitely the customization part.

of the prompt itself so i believe it was matt swanson that i discovered the uh you know customization of the prompt for when you're in a production server that you could just signal hey this is a different server than your development console you might want to be careful what you write in here and from there it kind of just exploded into okay well what else is in this

of the prompt itself so i believe it was matt swanson that i discovered the uh you know customization of the prompt for when you're in a production server that you could just signal hey this is a different server than your development console you might want to be careful what you write in here and from there it kind of just exploded into okay well what else is in this

customization and you know you open up your you find out you start you start with the irbrc as like your starting point and it kind of leads you into the rabbit hole of customization and what i realize is that you can basically make this file that will evaluate anytime you open up irb and do whatever you want with it so anytime you're trying to you know open up

customization and you know you open up your you find out you start you start with the irbrc as like your starting point and it kind of leads you into the rabbit hole of customization and what i realize is that you can basically make this file that will evaluate anytime you open up irb and do whatever you want with it so anytime you're trying to you know open up

specific set of code in a specific context, you can make a custom IRB file for whatever that context might be. So that was probably my biggest, you know, aha moment. And as an example, what we eventually ended up doing at Doximity was making a special Rails console that tagged the system internally

specific set of code in a specific context, you can make a custom IRB file for whatever that context might be. So that was probably my biggest, you know, aha moment. And as an example, what we eventually ended up doing at Doximity was making a special Rails console that tagged the system internally