 Today, I'm going to talk about how improving developer experience is vital to making frameworks more accessible and also contributes to a healthy open source ecosystem. Good developer experience helps bring engineers together from all levels toward the common goal of learning. My hope is by the end of this talk, you'll be inspired to work on developer experience features or at least think about and appreciate the ones that you consume. I don't have a traditional CS background. My training is actually in journalism, and that's really shaped how I tackle and solve problems in the software engineering space. I actually started my career out in Alaska at a public radio station where I was a journalist and also a web administrator. So I was writing stories about shucking oysters and gardening while also making sure that the website didn't go down, and that's how I learned how to code. And because of my past, one helpful system I use is the classic who, what, when, where and why thought process, which I'm going to use in this talk to describe developer experience. So who am I? Why am I talking to you about this? I'm a UI engineer on the economic graph team. One thing that my team does is release a quarterly workforce report that shows trends in the U.S. labor market. And this research is used by policymakers, by academics, by journalists. So I feel like I've really kept a tie back to my original training by working on this team. And like I said previously, I started out as a journalist. I really didn't have that much experience starting off on the job at LinkedIn three years ago. I really ramped up on the job. And when I was starting out, Ember seemed really new and exciting, but also scary. And not a lot has changed since then, to be honest. Also because of my past, I'm really passionate about working with the Reach Apprenticeship program at LinkedIn. And this program helps engineers from non-traditional backgrounds start full-time software engineering roles. And I really have to tap into the feelings that I had starting out, all of my fears, everything that I struggled with in order to empathize and mentor the apprentices. And also now I have a lot of experience seeing people from very different backgrounds go into the industry and how they learn and how they process concepts. And this has really inspired me to work on developer experience. So my main focus is on Ember data and the related add-ons, particularly M3, which is an alternative to DS model. And when I started learning Ember, that was the area that I found to be the most intimidating but also incredibly interesting. I distinctly remember when I had to hook up my first API endpoint at LinkedIn. I was actually pair programming with someone on my team because I was really stuck. And honestly, I was actually on the verge of tears because I was really feeling like I didn't understand how anything worked. I was really struggling. I kind of had this feeling in the back of my mind that LinkedIn had made a mistake by hiring me. It was one of those really terrifying moments early on in my career. But I was able to push through it. I got a lot of help from really supportive people. And I felt like this incredible joy when I actually got everything to work. And I realized that I was actually learning one of the most powerful aspects of the framework. And that was incredibly exciting to me. And so that experience really motivated me to learn Ember data deeper because I wanted to make it easier for me to understand what was going on and also for other people to understand what was going on. And one of the more recent features I was responsible for was for adding support for M3 models in Ember Inspector. This was actually just basically solving a pain point that I personally had. So what is developer experience? Developer experience is how engineers interact with your framework. It's really at the boundary between people and code. This can include documentation. Which is the entry point for most developers. And probably the first impression that they'll make of your project. If I go to a repo and it has a missing, outdated, or blank read me, I really hesitate to use the project. This also includes debugging tools, which engineers really appreciate. And they definitely remember if they're frustrating. This can also include framework ergonomics. And developers may not be consciously aware of good ergonomics, but they definitely know if a framework has clunky or difficult syntax. So unfortunately, developer experience is often not prioritized. And I believe one of the reasons why is because it involves people. And people metrics are notoriously hard to measure. It's a lot easier to say that you reduce the build size by X amount or sped up the website by X milliseconds. It's a lot harder to say that you made developers work X times faster with your feature. And just to be clear, though, developer experience is important, it should not come at the expense of user experience. Ideally it should be a symbiotic relationship. So I actually ran into this problem myself on a feature that I'm currently working on, the concept of people metrics. So I'm trying to add a button in the data pane to output the store into the console. And this is actually a feature that I wish existed when I started out, because I didn't know that you could grab the store off the container pane. I didn't even know what a container was. I wasted so much time putting breakpoints into my code to try to grab the store. It was very frustrating. But I didn't want to build a feature that I just only found useful. So what I did is I actually talked to a lot of developers from all different levels. I heard about their pain points with Ember data. I also pitched my idea to see if they actually would find it useful. And that enabled me to gain a little bit of consensus and traction, so that I felt confident that what I was working on was actually something that people wanted and that they would use. And I'll be making a PR for that soon, so keep an eye out for that. So why is DX important? If a framework has great DX, it's a lot easier for people to adopt it, to contribute to it, to answer questions, open issues, et cetera. And this really encourages diversity in a healthy open source ecosystem. If the framework is a delight to use, it really makes for happier engineers. If a framework doesn't have good DX, that really limits the type and number of people who can adopt it, contribute to the project, et cetera, this really can create conformity in the types of people that use it and the problems being solved. And also, if only a small number of people understand it, when developers are building out applications, there's a greater risk of bugs being introduced into the code and framework misuse. If the beginner can only understand what is happening by looking at the source code, that is a failure of the framework. And they'll probably go and find something else that's a lot easier to use. They don't have to use what you've built. And luckily, I'm not the only one who thinks that this is a problem. So when should you contribute to developer experience? One great thing is that newcomers bring new and very valuable opinions to developer experience. New engineers have fresh eyes and new insights into the framework. They know what's hard starting off. These insights are really lost the longer you work with a framework. And people can contribute to different facets of frameworks as they gain experience, and each of these ladders is vitally important. And as engineers grow, they should continue to contribute to all levels of developer experience and help new engineers level up. And this will create a self-perpetuating ecosystem. I also really encourage people from nontraditional backgrounds to contribute to developer experience. I feel like there's a lot of pressure for people from nontraditional backgrounds to conform to the expectations of how software engineers should learn and solve problems, and we should really be using our unique backgrounds to make frameworks and the open source ecosystem a more open and engaging place for everyone. So where can you actually contribute? One suggestion I have is to work on features or missing documentation that bother you or hinder you in your day-to-day work. This will help motivate you to contribute, and you'll also directly benefit from it. And a lot of small one-line changes exist. I personally have a huge pet peeve when it comes to deadlinks. Whenever I see a deadlink in the code, I'll make a pull request from the repo to fix it, and this ensures the next person will have access to the information, and I've done this for Ember data, for the octane guides, for Mirage, so on and so forth. And usually this PR gets merged within days, and it really helps build relationships with the maintainers at the very least and kind of give you ramped up onto the framework. You can also add examples of how to use add-ons. So if you start consuming an add-on and you kind of struggle with a bit to figure out how to get it to work, you can create a pull request in the readme with an example. And I've also done this with Ember sign-on queue unit, because like a lot of people, I actually spend a lot of time figuring out how to test my code in addition to writing my application code. And as you work on the framework more, you can add comments into the source code. You can work on developer tools like Ember Inspector. There are just so many areas out there that are just waiting. And maintainers really appreciate you making these fixes, even if they seem trivial, because honestly, a lot of times they don't have time to take care of these themselves. So hopefully now you understand why I'm so passionate about developer experience and how important it is. DX is a great opportunity to help you learn more about the framework and also to help others learn. And if you're inspired to work on developer experience tools, I'm more than happy to talk to you about them. Just let me know. So, thank you.