Speaker 2
That's the other piece of this. Obviously, Jaymon just goes for the you suck
Speaker 1
angle. Is that a new role prompt engineer? Prompt
Speaker 2
engineer. Oh, totally. There you go. Professional AI prompt. I'm unironically saying it is. That's going to be
Speaker 1
a thing. Recruiters knocking on the door. I'm not even kidding. Prompt engineering is a thing. I'm, I'm putting
Speaker 2
a stake in the ground right now. You're one of the first experts at it, I think. You're, you're one of the best. I wouldn't call myself an expert, but co-pilot prompters, I know.
Speaker 1
I like, I like it. I'm tab driven development, right? Like you're just, you're creating prompts and then
Speaker 2
you're hitting tab. The new TDD. Exactly. So I guess if you're
Speaker 1
a space driven, if you like spaces over tubs, you're kind of out of luck with. Well, you hit tab to auto complete,
Speaker 2
right? Yeah. So. Sorry. I thought it was funny. Thank you. Even if Jaymon
Speaker 1
didn't. Did I just, I was like, seriously. You can still tell me. I'm funny. It's okay. So co-pilot in my observation is very good at JavaScript and TypeScript. It's pretty good at React Native. Like it knows certain things and knows quite a bit. It knows Kotlin Swift, Ruby, Ruby, these are all languages we use internally with React Native projects. Objective C, Java, knows Ruby particularly well because there's so much Ruby on GitHub. But so if
Speaker 2
you ever have to write Ruby, like you shouldn't be writing it like co-pilot. Why is there like more Ruby than other things on GitHub?
Speaker 1
Because my opinion is it's because GitHub was written in Ruby. So their circles knew about it early and started using it. I mean, I was doing Ruby, so were you, Robin? And like it was just like an early like, oh, GitHub's written in Ruby. It's written in Rails. When did GitHub first come out?
