 It's interesting. I've worked with developers for so long, and I consider myself a developer, so I'm kind of biased in my opinions here. I guess I should have said that in the beginning. I'm really biased in everything that I say because I've been a developer for really long time. I think that don't be afraid, and this is good advice in general, but I think it's good advice with developers. Don't let them talk over you. If they say something and you don't understand, ask them to clarify. There's so much going on and there are so many different things. It's important to make sure that when you're doing your user research and you're talking to your audience that you have them explain things to you because it can be very easy to make assumptions and get it wrong. It's really important to dive deep down and really understand what it is they're talking about. There are many things that are very overlapping, and they can go this way or they could go that way, so it's important to ask those clarifying questions. I think it's also important to keep in mind again that they're not just your user base, but they're also partners on this side of the fence. Make allies out of the developers you work with to better understand the developers you're designing for, which we're really lucky to have that insight here. We work with a huge development team or on the engineering team, so not only do we have to talk to them about our designs and the things that they need to implement, but they're using the tool we're building for them and designing for them. We get this crazy feedback loop that comes in where we get to hear from them their initial thoughts and ideas, but that's also dangerous because then you can get in this little bubble and think that well the way I use it and the way they use it is the way everybody else will use it. You do have to get out of that GitLab bubble, and it's the same for any product. Don't get yourself in that bubble where you think just because you're using your product and then the developers are using your product that you totally get how other people are using it, because you probably don't.