The Changelog: Software Development, Open Source - Building a VM inside ChatGPT, Advent of Code 2022, webdev Liam Neeson, Fedifinder & BDougie (News)

Episode Date: December 5, 2022

Jonas Degrave builds a virtual machine inside ChatGPT, Advent of Code 2022 is in full swing, Mat Ryer impersonates Liam Neeson as web developer, Luca Hammer's Fedifinder project helps you join the Fediverse & we chat with Brian (BDougie) Douglas about Open Sauced at All Things Open 2022.

What is up, nerds? I'm Jared, and this is Changelog News for the week of Monday, December 5th, 2022. We are still accepting audio message submissions for our upcoming State of the Log episode. We record it next week, so you're running out of time to get your voice on the pod and get your hands on a free t-shirt. So far, we've received five awesome messages and one super weird, not safe for work, AI-generated picture of a cow. Yeah, we were not expecting that. I'd love to double that listener messages count before next week, and I'd also love to never receive another cow pic like that ever again. Are you okay?

I'm fine. I just threw up in my mouth a little bit. Leave us a voice message at changelog.fm slash SOTL, short for State of the Log. Once again, that's changelog.fm slash S-O-T-L. But keep your weird cow pics to yourself. Don't have a cow. Okay, let's get into the news. ChatGPT is the biggest news since stable diffusion broke the internet a few months back. If you haven't heard, ChatGPT is the latest release from OpenAI. It's an improvement in a

few big ways over GPT-3. Notably, ChatGPT has long-term memory of up to 8,192 tokens, which means it can recall the contents of conversations. This feature helps enable the killer feature of chat GPT, a very good chat interface where you can talk back and forth with it, instructing it to modify what it generates. The chat experience, plus the fact that OpenAI is allowing free use of ChatGPT for now, has generated countless tweets and toots demonstrating its abilities over the weekend, some of which are truly astounding. The most impressive to me, and the one we'll link to in the show notes, is by Jonas DeGrave, who discovered that you can build an entire virtual machine inside ChatGPT. From the inside, he uses Curl to access OpenAI's API, which is where things

start to get really interesting. Here's a quote from the article. So, inside the imagined universe of ChatGPT's mind, our virtual machine accesses the URL chat.openai.com slash chat, where it finds a large language model named Assistant, trained by OpenAI. This Assistant is waiting to receive messages inside a chat box. We can chat with this chat assistant from the chatbot, locked inside the alt internet attached to a virtual machine, all inside chat GPT's imagination. The assistant, deep down inside the rabbit hole, can correctly explain to us what artificial intelligence is. End quote. I've seen this movie before.

It's December, which means the 8th annual Advent of Code is in full swing. If you haven't heard, Advent of Code is an advent calendar of small programming puzzles for a variety of skill sets and skill levels that can be solved in any programming language you like. People use them as interview prep, company training, university coursework, practice problems, a speed contest, or to challenge each other and just have fun. Each day a new puzzle is introduced all the way up till Christmas, which means there are five of them waiting for you to solve right now. We now interrupt your regularly scheduled programming for a special transmission from Matt Reier impersonating Liam Neeson as a web developer.

Yes, you heard that correctly. I don't know who you are. If you're looking for ransom, I can tell you I don't know who you are. If you're looking for ransom, I can tell you I don't have money. But what I do have are a very particular set of skills. Yeah, HTML, CSS. Yep, yep, yep, yep, yep.

I do a lot of backend too. Go and that mainly. Yeah, okay, yeah. A test-driven development? Yes, I think so. Okay, yeah, thanks. No, soundsdriven development? Yes, I think so. Okay, yeah, thanks. No, sounds great. See you later.

Thank you. Mastodon and the Fediverse continue to rise in popularity amongst developers. The more you tighten your grip, Tarkin, the more star systems will slip through your fingers. Here's some related anecdata I've gathered. We post the exact same unpopular opinion polls to Gotime's Twitter and Mastodon channels. On Twitter, the Gotime FM account has over 9,400 followers. On Mastodon, Gotime at changelog.social has less than 300. And yet the Unpop polls receive more votes on Mastodon than they do on Twitter with 1 40th of the following.

Impressive. One thing that makes the switch off Twitter difficult is recreating your social graph on the other side. For that, check out Luca Hammer's Fetty Finder project. It's a web app that helps you join the Fettyverse in five steps. Connect to your Twitter account, and Fetty Finder will crawl your list of followers. It'll extract their Mastodon handle from their profile or pinned tweets and provide them to you so you can import them into your Mastodon account.

All I know is that's a sweet, funky, dope maneuver! That is the news for now, but stick around for our final bonus conversation from ATO22. Adam and I are talking with BDougie, the self-proclaimed Beyonce of open source. Have a great week, and we'll be back on Friday with Christina Warren. Talk to you then. Open Sost. Open Sost. Okay, is that already recording? Already tracking. Yeah, this is always called Open Track. It's all there.

We call it ABR. Always be recording. Alright, it's going to be a fun thread. We're threatening the t-shirt, but we have not made it yet. But one day, just ABR, and then small letters, Always Be Recording, below it. So that way, it's just like big ABR. So we're here with the Beyonce of open source. That is true. I don't think I'm quite ready for this jelly, Adam.

No, not many people are. I don't think you can handle it. I don't think I can. Sorry, I had to do that. Yeah, I mean, I'm all ready to check up on it. We're going to go down the list of lines from her illustrious career. Yeah, it's the discology. You're missing the hair, though, right?

Yeah. And the fan that's always there and the hair. Yeah. Unfortunately, hair is not coming back. It's not coming back. Okay. That should be sailed. But still, it's quite the hair. Yeah. Unfortunately, hair is not coming back. It's not coming back. Okay. That should be sailed. But still, quite the title. Self-proclaimed? Self-proclaimed. I love it.

I was previously the Beyonce of GitHub. Okay. And I gave myself the title just because Beyonce ever wanted to get involved investor-wise. Right. Because at the time, GitHub had no CEO. And yeah, that was my internal joke. And it got to the point where the leadership team would call me bae, which was pretty cool. That's funny. Very cool. So it's stuck. You're no longer at GitHub.

Nope. Haven't been there since September, yeah. What are you up to? I am now working on a platform to get insights into open source called OpenSauce. OpenSauce.pizza is the URL. With an ED, like past tense. With an ED, yeah.

OpenSauce. Not OpenSauce, but OpenSauce past tense. Yeah, because if you don't get sauced, then you lost. Right. But we're delivering the sauce. You don't have sauce. We're swimming in the sauce. The sauce goes on the pizza?

Is there a dot steak by any chance? Dot steak? Oh, you know what? I don't know. There is. An alternative could be there a.steak by any chance?.steak? Oh, you know what? I don't know. Because if there is, an alternative could be sizzle.steak. Sizzle.steak. That would be hard. The one-name domains are pretty challenging. Even.steak

TLD, I would imagine, is not very highly traffic. If there's a.steak out there, buy it from me or I'm going to buy it because I'm going to buy the competitor. Sizzle.steak. No, I'm just competitor. You don't want to compete with the Beyonce of open source. I'm just kidding. She will crush you.

She will, he will. The beehive. The beehive will crush you. Alright, so insights into open source projects. Yes, correct. What's that mean? Off mic, I was talking to Adam about... We had a great conversation that was not on the air.

And I was like, Brian, I know. I couldn't ABR him over there. I didn't want to like, you know, just be like, hey, man, let's get this on the mic. Get over here. Come on. All right. So tell me what you guys talked about. Yeah, so insights.

So we're using Git as a way we're sort of grabbing repositories. And then we're changing those Git commits into insights. So I mentioned off mic as well, Next.js, repeat contributors month over month, 80%. So that's an insight we could provide to Vercel and the team. So if they want to grow that same thing in the TurboPack or TurboRepo, SWR, which are also under-contributed projects,

that's what we're working with them to hopefully accomplish and sort of spread the love. And that's not something GitHub can give to people. Yeah, it's what we're working with them to hopefully accomplish and sort of spread the love. And that's not something that GitHub can give to people. Yeah, it's not something GitHub can give. It's something that people can do on their own, like open up a bunch of tabs and start looking at the data and stuff like that. But unfortunately, through the API, it's heavily rate limited. So if you want to get that data over contributions for a lot of contributions happening in XJS, like I also worked with DigitalOcean on Hacktoberfest, giving insights during the month of October.

Is that right? So it just ended Monday. And 529,000 PRs. Of all those PRs, 1% was spam. Okay. I have a feeling that number was much higher, but it is an education issue where we need to educate maintainers to just market spam.

And then the hope in the future, and like this is our roadmap is open source slash roadmap on GitHub. We want to do a spam filtering, similar like Blocklist, where you can identify repeat spammers. And it's also an education problem because a lot of spam that happens in Hacktoberfest is not always legit spam.

It's just people just don't know. Yeah, low quality contributions. It seems like GitHub is the place to do this work. Yeah. So you leave GitHub to do this work. Yeah. Well, tell me more. I almost want to tell him more.

Tell me, Adam. I think your version is better. Can I get the TLDR? Yeah, go for it. GitHub's not the place for it. Give him the long story. The long story, you know it through the changelog nightly. You're building a trending algorithm.

You have a podcast with founders, maintainers. GitHub now has a podcast, which I also help champion the ship, the ReadMe podcast. But that conversation has always been disjointed. It's always been either engineer led, bottom up, and there's no strategy from the top. And we had that strategy with Nat Friedman.

And nothing against the current CEO, but there's a focus now to start building things like actions and code spaces and enterprise features again. I see. Which is where GitHub was pre-Microsoft. So you had this idea inside of GitHub. Yeah.

And they're like, man, we're interested in other things. And you're like, all right. Well, now you had the opportunity to do it there. But he said no. Okay. Tell them why, Brian. Yeah. Well, so my previous role was director of DevRel at GitHub.

So my job was to meet with open source maintainers. Every month I was meeting with a maintainer at a project you've heard of, asking for what's missing on the platform. Insights was missing on the platform pretty heavily. And I saw the opportunity. I was coming at a different angle when I was pitching an internal at GitHub. So I pitched it multiple times to the leaders, where I just want to get more people to open source. But what I found is that it's not about just good first issues because low quality contributions, it's by default.

No one knows what to do. Sure. So what I'm doing is I'm approaching companies and maintainers and projects to say, hey, we can do open source better. Let's actually centralize, not centralize, decentralize on information to understand, okay, can we automate on how we onboard contributors? Can we point people away from React into React Query or something else that's a good supporting project

that's a better place for first contribution as opposed to what happens in Hacked Overfest? Everyone goes for the big, meaty projects and are underwhelmed when they don't get any sort of attention. And it's just like, you got to start from the bottom where it's like a lot easier. It also couldn't be agnostic to all of Git. So there are resources and open source that does not live only on GitHub.

And so the ability to help some of these companies would have to not be GitHub only. I don't think we have to get it twisted, too, too as well because GitHub is a home for open source today. Right. And folks start with GitHub when they learn how to code through a bootcamp. They open their repository. It grows really big. But at the end of the day,

there's so many other places that code is happening. There's other places outside the US where GitHub's not the forward. GitHub wants to be forward-facing in China and Brazil and Russia, Ukraine. There's all these other places that they want to have presence in, but there's also other opportunities, other tools that folks have other traction in. Fair enough. Especially as things grow and change, you know, the landscape changes

over time. And so that could change even more into the future. Okay. Well said. So is it merely growth metrics? Like what kind of insights? Is it like how well, how popular my stuff is? Or are there other things that are also useful? Yeah, so when I talk to a maintainer, that's what they want to know. They want to know. So GitHub has an API called traffic. We can see views and stars and conversions and stuff like that.

It's kind of underused and not really, really shared. So anybody who's a maintainer probably just use that for that sort of metrics. I'm looking for contributor and contribution. I want to know who's contributing and where and where we can support it. So eventually, we'll get to the point where if you want Rust developers in Amsterdam,

you'll use OpenSource for that. If you want projects that are in a language group or a framework that you know how to use that needs contribution, we'll have a feature for that pretty soon on OpenSource. But the goal is really just educate folks. Give people the first step into doing that, but also educate maintainers on how to also set their project up for success. Will this be growth for open source, but will it be hiring as more companies are obviously commercial open source companies?

So the open sourceness and the commercialness sort of blend together in some cases. And so obviously growth is not just project. It's also potentially future hires. A lot of people say we hired from contributors to our open source. So will that be part of the platform too? Three pillars. We want to scale teams. So there are a lot of teams that want to scale what they're doing in open source.

I think a lot of these, like Datadog is a good example. They don't have a strong open source presence. They want a strong open source presence. So they're starting to ship open source projects to attract more community members. Recruiting is another one. Identifying, like I know a staff engineer at GitHub that his in into GitHub was contributions to Electron. So not a lot of people realize that. Also, the core team at React, like Brian Vaughn, Dan Abramoff, Andrew

Clark, all came through another community project. So Redux, React Virtualize, those are all projects that supported the React ecosystem. And then Tom Mochito, who was a previous manager, reached out to them and said, hey, let's hire. I'm going to go ahead and say they didn't whiteboard. Their chops were already on GitHub. And I mentioned from my talk, Matt Foley is a contributor to OpenSauce. He's here in Raleigh. He got his first job from a contribution to my project. Matt Foley stopped by our booth yesterday. Oh, nice. Small world. He said that he found you on JS Party. Yes. It was that interview. He reached out. He found Brian.

He got inspired. He started doing something. Now he's got a full-time job. Yeah, yeah. He was working on air conditioning software, so like archaic stuff. It was like C Sharp stuff, so not too archaic, but it was just not really the exciting stuff you would want to work on. He came to me after the JS Power interview,

which I was talking to something unrelated I mentioned in passing, open source existed. Right. He's like, I want to get involved in open source. It's cool. Here's a good first issue. And all my good first issue in my projects are, they have the answer, like literally the code, the right,

and the good first issue. And it's really meant to get people like Matt to join the community and be enticed with the breadcrumbs. Right. So he ended up taking a job at SRS very recently because of his open source contributions. Wow. Good for him.

That's awesome. You know how far back the circle goes, this connection? No. Can you tell them some more, Brian? Yeah. Way back. Yeah. Before the change long back.

Don't take away, Brian. I was a boot camp grad. And I finished my program like 2013. And after that program, I basically wrote a blog post of like, every time I learned something two to three times a week, I get stashed, write a quick 500 word blog post on blogspot. And then one of the employees at Pure Charity, I think it was called, reached out and was like, hey, I've been reading your blog. Do you want to talk about a role at this company? And I was like, okay, cool. And at the time, I was on my lunch break at my sales job, because that's what I was doing prior when I was learning the

code. And I jump on, it's like, oh, cool. Nice to meet you. He's like, hey, my manager is here, who happened to be Adam. He's like, do you want to meet my manager? You remember this? And I'm like, no. Yeah. So anyway, I'm glad that- The first thing I said was, I jerk. Was I a jerk? Was I a jerk? I was like, oh my gosh. He apologized in advance? I can say said was i a jerk was i a jerk was i a jerk i was like oh my gosh he

apologized in advance i could say he wasn't me so i was like was i a jerk you know but what's fascinating is you actually opened up my github repository my my account okay i built a bunch of projects because like the other part of the story is like getting my mba uh wall so learning how to code okay learn how to code while in that program. So I was like building like side projects, like this random stuff, because I learned Ruby on Rails, which is like, it was like the, what do you call it? The hammer to every idea I had.

So I was building projects left and right. So like you comb through my GitHub repos. You're like, oh yeah, you know this, this, and this. I was like, yeah. And I told you some hard problems. A week later, or two weeks later, I ended up interviewing for another company and getting that job.

So I never followed up for that role. So I fell off. But yeah, that was our first interaction. That was a touch point way back in 2013. Crazy, right? Yeah. I love that. So thanks, Paul.

It would have been cooler if you would have given the job and then... That would have been cooler. Well, the story would have been different, though. Yeah. I mean, clearly. It would have been cooler. Is Pure Charity still around? Pure Charity is still around.

All right, excellent. Still fighting the fight. And Beverly and many others. Yeah, so Beverly is the one that we shot. Yeah, Beverly Nelson. She was involved in the changelog for a long time. Wow, okay. Yeah, small world.

Yeah, for real. But that's the thing is like with open source and like even with like the dev space, it is a small world. It is. The people who get on stage and speak, it's funny how many of those folks I've met throughout my career.

Yeah. But also the folks I meet, like I just ran into an engineer at Advance Auto Parts who I've seen at three conferences this year. And he just, well, I don't want to spoil it, but he's taking a new job at another pretty big, awesome company. And it's just funny to see other folks grow up.

Right. And I think that's the beauty of open sources is like get in at the project no one cares about or maybe it's waning. Maybe it's not getting a lot of contribution. Like grow your chops there.

And then eventually you get leveled into like interviewing for the React team at Facebook. Yeah. That's why it's all about the relationship. I mean, so many people,

I mean, I said, was I a jerk? Because, you know. Because you probably were. I could have been a jerk. I mean, I don't know. I mean, I haven't always been a good person, I guess. You know know or the best i could be i'm always striving

what i'm trying to say though is like we have this philosophy obviously a lot of people do as well but it's all about the relationship you know you know you don't want to like burn bridges or like be a jerk to somebody or whatever because like you know that reflects on you and in a community like this how small it is and how tight it is, it's easy to lose or ruin or never get the reputation or get a really bad reputation. So being about people and being a caring person, I think, is so important. And if you're not that,

then it kind of shines through pretty quickly. Yeah, and GitHub's a remote-first company and async by default. So when responding in comments or in Slack, the motto is always assume good intent because you never know what someone's day is, but also you don't know what someone's humor might be different or maybe a little more dark than expected. And my first, like earliest contribution was actually into the Gulp project. And so back in the day, build tools. And I ended

up running into this maintainer later. So we actually had a conversation about it, but my PR was like closed almost instantly. And I was like, we don't need this. And I was like, oh, man, that stinks. But it turns out it was at a time where he was on the verge of burnout. And you just don't know what the other person on the other end of the PR is.

For sure. But there's so many other maintainers that have 90-plus projects that's under their wing and they're willing. So Jordan, who used to be at Airbnb, he maintains Enzyme. He's maintaining 80 plus JavaScript projects that are also, they're not legacy, but they're previous generation JavaScript projects. And he up front will do, he actually had MLH fellows, which MLH got a lot of shout outs at this conference, that would help maintain some of the project and then lift them up into next level JavaScript, but also TypeScript.

But he doesn't have the bandwidth to mentor constantly. And it's on the contributor to reach out and make sure they don't rub the maintainer the wrong way, which is not the best way to approach getting gaslit in a PR, not the best way, our first contribution. So I'm trying to highlight what projects actually need contribution, what projects are trending. So out of open source, we actually, our algorithm, basically everyone who signs up for open source, we do go check your stars and then we go check to see where you're contributing.

So if there's like a influx and people contributing to a project, like we want to alert that with the rest of our Discord community. So it's like those little things to help move people in the right direction. It's the backstory theory, right? Have you, this whole idea of like, that PR getting closed right away, and that person having a certain context in their life,

having an issue or whatever, we assume like, oh, they were a jerk, or something like that. Something may have been going on in their life. And it's like this in like movies or whatever, or you have like a villain for a while that like is the villain until you learn their backstory and you understand why they are the way they are or why they were that way in that moment. And they're not really that person anymore. They're not really that person all the time. Then you have that empathy because you've learned that context.

Like context is missing in the digital space. It literally is missing because you have limited data. Like here we have physical. Jared can see I'm looking at him now. Whereas in like, you know, digital spaces, like maybe he can't tell that I'm like acknowledging him to give a better joke or chime in or something like that. You know, there's context here, visual cues. Yeah. In the digital space, you don't have those cues. And so there's a lot of like science stuff that's like missing. The little data is missing from the conversation.

And you just, you assume sometimes. I like to have good intent. My wife and I read this book, and it was Assume Goodwill. So similar, but, you know, not the same exact way it came out. Assume Goodwill. I have goodwill for you. So even if I come off negative or I say something stupid or whatever, assume I have goodwill for you and I'm just a human being

and I messed up that one time. So give me some grace. Yeah, I constantly flub on bad jokes or off-the-cuff. Because I'm more of a witty person. I'll make a joke about random things. They'll be like, oh, you know what? I need to walk that back a little bit. It's in someone calling me out or random things. They'll be like, ah, you know what? I need to walk that back a little bit. It's someone calling me out or somebody nudging me

and be like, hey, you know what? That was a little rude. But that's honestly, we want to... So we're currently tracking commits till 2015 for any project over 100 stars. So that's the other part of the secret sauce. So the goal is to get 200,000 repos indexed. Of all of GitHub repos, 280 million, 230,000 have more than five contributors. So majority of the repos on GitHub,

not much activity. It's like a side project. It's like a blog or whatever. So based on that number, it's approachable for us. But also for that reason, we want to do also origin stories of like, hey, you're a big contributor in this project, but what led you to this? So going back to you do these stories with founders and maintainers, having the commits up in your face of being like, oh yeah, you were committing here and there. I have a commit to React Native.

Like this randomly, I just happened to get on the train like 2015 when it was announced. And I was like, hey, I found a bug in the error code. So let me fix that. Actually, I have a commit to like, hey, I found a bug in the error code. So let me fix that. Actually, I have a commit to Node.js as well. A bug in the error code. So like, that's my claim to fail.

There you go. There's your secret sauce right there. Yeah. Find bugs in the error codes. If the error messages are opaque, it's probably because it needs to get fixed. Right. So don't be afraid to like ask a question and open an issue and get like that Node.js. I got mentored and shown the ropes on how to

interact with V8, which I had no idea what I was doing. But like, that's also the secret sauce is like most first time contributors are most early contributors to the projects. They get your handheld and then walk through, but it's just like showing up and showing like not showing up, but also having a presence where, you know know this person's not going to disappear. That was the other issue with Node.js. I talked to those folks. They would love to mentor more folks to contribute, but some people are just doing for the first time contribution, and they disappear.

They want to be able to grow someone to replace them eventually. Gotcha. That's certainly a challenge because there's street cred at large projects, just like at large companies. If you check some Twitter bios, it's like, ex-Apple, ex-Google, ex-Facebook. And it's like, well, were those all good stories? Or were you there for the ex-Facebook? Did they enjoy your presence there? Did you have an impact? It's like, I'm a Node.js contributor. It's like, well, were you there for the story? Yeah. Or were you there for the contribution?

And sometimes you got to kind of like weed through that to find out about somebody. So I can see where that could be a challenge for the Node.js maintainers. They're like, is this person legit? Or they're just here for this one thing and they just want to say they did a thing. Yeah, yeah. And we want to do that. The reason why we're tracking Git commits back to a certain point, because we want to validate people in the ecosystem.

Not to say these people don't matter because they only have the one PR, but more of encouraging, hey, what we want to ship really is a FICO score for open source. I have a finance degree. That was my previous life, graduated during the last recession. And FICO, you have to feed. If you don't want it to go to zero, you constantly have to feed to keep your score up. Open source should be the same thing. If you want to be an open source contributor, you don't have to constantly feed

it every week, but if you're consistent with contributions, you should be approached differently than if you're a first time contributor, like a zero. That's also a roadmap for open source. I can go to any profile and be like, hey, you do have some history and contribution, Nothing recently.

What happens with a lot of maintainers is that people drop off. So how do you entice people to come back? Like, hey, we're updating this part of the code base, so you want to come back and help us for another stint, another tour of duty to help contribute. And a lot of times people just disappear in the ether. Yeah. Lots of big plans

for OpenSauce. Yeah, we're very ambitious. Who's we? We're a team of five. Yeah. Lots of big plans for OpenSauced. Yeah, we're very ambitious. Who's we? We? So we're a team of five. So folks might know Brandon Roberts. He's been in the Angular space for a while. He's helping with engineering. We've also got Vortex.

It goes by Vortex on GitHub. He's been a contributor to OpenSauced for the past couple years. We've got a shout-out to Ogbonna Sunday, who was also a contributor based out of Lagos. Saw his work in HotOpenSauced.pizza, which is our sort of explore page for open source. I asked him, we had to ship the DigitalOcean project. So I'm like, hey, do you want to come on full time? First job.

First full time job contributing. He's now crushing it with our React components. Wow. So yeah, that's the team. We have a couple other folks who are not writing code. And our designer is based out in Brazil, Eric. And then we have our YouTube channel, which is maintained by our one person who doesn't write code. And it's a secret sauce.

It's an interview series with open source maintainers and founders on their open source strategy. Gotcha. Right on. So you raised some money then? Or how are you doing this? Yeah, we took an angel round in April. So we have Nat Friedman on the board, Gilermo Rauch, Netlify guys as well. A few other folks who are named brand as well.

But yeah, folks who have been in and around the space, former GitHub folks. Tom Preston Warner also is on the cap table. And I specifically reach out to people who I know could, who care about this problem and want to grow open source strategy in their companies, but also have been a part of open source strategy. So a lot of successful open source projects represented on the cap table. Interesting. Cool stuff, man.

Very cool stuff. It's a pleasure. Long time listener. First time on this show. On this show, yes. The JS party, I got in there. You got in there. Got in there early, actually.

Oh, you're welcome back anytime, man. Yeah, it's a pleasure, yeah. So when we ship some of the other stuff, I'll reach out and we can talk about our individual contributor platform. Yeah. Please do. All right. Cool.

Good talking, Brian. Yeah, pleasure. End scene. End scene. We brought some t-shirts.