That sounds like a lot of fun. I guess we'll hear a bit about that in a bit. Yeah. So we have Jeff here. Welcome, Jeff.

Hey, I'm happy to be here. I gotta say, it's gonna be a little weird because I normally listen to you guys at one and a half speed. So it's like you're talking really slow. Being here in person. Oh, yeah.

I do the same thing. Yeah, same. Well, I don't really listen. How are you doing? There

we go. Hi, Jeff. Everyone

sounds drunk. If you go from like 2X down to 1X, it is

ridiculous. Yeah, I saw that during the summit. I got a little behind and I was trying to catch up. And then eventually you hit the wall where it's live again. You're like, oh, everyone's

talking slow. I'm going to talk really, really slowly so that when you listen at 1.5, I sound normal.

Yeah, that'll be a big help. Thank you.

All right.

So Jeff, who are you? Yeah.

Hello, I'm Jeff. So I am sorry. Yeah, just jumped into a box. So I'm a senior software engineer at Alaska Airlines, which is a regional airline here in the United States. And I am also a frequent blogger about Svelte. I've been doing that for probably about a year and a half now. And a recent addition to the Svelte core team. So yeah, that's a little bit about me. Congratulations. Thank you. Yeah. It was really exciting and not expected. So

it's well deserved. All right. Well, thank you.

Cool. Now, is it true that your surname, you gave yourself that surname, Intribute to Rich Harris? I mean, that's partly true.

Yeah, it was actually an undercover operation. It's like if I if I at least match the man in name, you know, it's more likely that all appear more knowledgeable about Svelte and be more likely to be accepted.

And you'll become pretty smart. That's why we kind of do

this. It's the long game. It's been going on for years.

It's

working out

ways. Nice. Started even before you were born. Yeah.

Now, my, my, this was the goal. My parents had a plan. Wow.

They knew Svelte was going to be a thing. Premonition. Wow. That's a stock in that. Yeah. So you mentioned Alaska Airlines. What do you do there? Do you just do you work with Svelte or do you?

Yeah. So I mean, at Alaska Airlines, I'm a full stack engineer there. So I touched the back end and the front end. And yeah, we use Svelte for some things. So we're currently in the process of breaking up our big monolith into smaller micro sites owned by independent teams, independently deployable. And for a couple of the micro sites, my team owns, we've chosen to go with Svelte for that. So we have a few small Svelte sites in production right now, which is, which is exciting. It's nice being able to work on Svelte at work, which I know not everyone has the opportunity to.

Is that micro front ends or is that completely separate sites?

I think it's, I think it's not a micro front end. It's a micro site because we're not pulling in different parts from other teams. Where it's like an independently deployable site that gets proxied. So if you go to a URL starting with this, you're being served this micro site. If you go to a different URL, you're being served a completely different micro site.

So that's pretty interesting. I never think that like an airline has so

many websites, but I guess it kind of makes sense. I mean, if you think about it, there's just so much, you know, there's booking, there's actually viewing your reservation information, there's accounts, there's flight status, there's operational stuff. And the airline business, there's, there's so much deep business logic and knowledge that there's just a lot going on.

How do you deal with things like shared, like style, like shared CSS across sites? Yeah.

So we actually have a, we have a design system that's been in progress for a few years now, actually built on, on web components. Because of that micro site nature, you know, my team using this felt there's another team using React. We still have legacy.net code. So we needed a deliverable there that could be used across all teams instead of having the design system team build a separate version for each framework people are using. So yeah, we have, we have shared design system components, built using web components. And then we also have shared,

there's some shared base CSS that the newer projects can pull in. Do you know if that's published, is that an NPM package? That's what I did at my previous job. So I'm very into design systems and how they work at other places.

Yes. That's actually a big thing are the lead on the design system really wanted it to be open source. So it's all open source. If you go to a URL or a Alaska air.com, you can see everything there. That's, that's being built. And that's all in GitHub. We're trapling to that.

Oro. What was the, he addressed?

You are a Alaska air.com.

So I mean, since you work for Alaska air, do you live in Alaska?

That's a frequent question, but no. I live, I live south of Seattle. And actually our main hub is in a sea tack Seattle area. So, oh, yeah, most of our, there are people in Alaska. And I think it's Alaska, because that's where we, where we started. It's where some of the first airlines were, but we're, we're all around the West Coast. So not just Alaska.

That kind of makes sense for an airline to have a hub on the mainland. Well, I mean, Alaska is the mainland, but it's a way.

Yeah, we still fly a lot of flights to Alaska and Alaska is still a big part of our business. But our hub is, is in Seattle.

Cool. Cool. So being a spelt maintainer now, what, what do you do? Yeah.

So I mean, since I've become a spelt maintainer, I haven't done that much. All exciting. It's not like, like, oh, look at this big new feature I shipped. I mean, it's basically what I was doing before. So looking at issues, responding to issues where I have feedback or have something to add or asking for reproduction there. The biggest thing is probably providing feedback around some accessibility things as they come up. One thing in particular, this felt kit Doc's got a search bar. And, and as Rich was working on that PR, he was asking me to take a look at it from an accessibility perspective and I was able to give some feedback there. And then, yeah, I mean, the biggest difference is there's now I'm in the, the maintainers chat. So I can see a little bit of the behind the scenes stuff and, and get to look at a few things before they're actually out there as an issue or whatnot. But yeah, it's mostly, mostly those smaller contributions right now. Yeah.

Cool.