Fiona Fung

Um, and for example, a sad might be, Hey, is it flickering?

Like it might be recoverable, but we have each team like, and that's why it's been interesting because before each, because surface areas are different, like we would have all these dashboards, but it's, it's harder to zoom out and go, okay, what's the overall theme of the experience.

So to your point, we give high agency to each team of what we think constitutes a bad and what's a sad.

And then what's the goal that, um, each team wants to take.

Yes.

Actually, I remember, yeah, that was last September because we were all seeing some frustrations.

And, yeah, that was an engineer on the team of, hey, we should maybe track square words.

I'm like, oh, that's a great idea.

I remember it.

I had just, you know, joined when we were having that really fun conversation.

Yeah, so it's, again, like it's very interesting to kind of like look at.

And that's why like evals is hard, too, because it's going back to like that user experience and how we can make sure it's a delightful experience and less frustrating experience.

But yeah, the swear word dashboard is a fun one.

I love it um it's funny when I first joined because I and I have amazing recruiting partners and I noticed we were you know this whole theme of um kind of growth mindset it's just because the landscape is changing so fast like what worked well before like may not make sense and even what makes sense today may need to change tomorrow right like that's what I have to keep reminding myself so yeah when I first joined recruiters like okay yeah we have these um

couple like manager postings and I'm like you know because actually how it came from like a listening tour I did with like all the all the um members on the team of and I heard a lot of these hey I really appreciate the agency but how can I make sure prioritization and and so I kind of through that I I um I realized and then there was some really good feedback too of making sure that um it's not too many layers of reviews like there was good feedback some

folks that might have joined from other companies are like, you know.

And then I'm like, hmm, when I actually think as a leader, if you actually start as IC First without the worry of supporting people, because that's a very heavy responsibility that, you know, I think like matches.

But before you have to take on that full responsibility,

give yourself that maker time to actually tap deep into the code and learn the code base.

And I, or, or, or the product, like whatever it is, it doesn't have to like, honestly, the PRs I do are like, but it's more about, for me, it's important because it keeps me in the flow because we're making so many changes to co-work and code.