Pete GonzalezGitHub / Gitter / Twitter I’m a software engineer. My focus is developer productivity. When you maintain a large software app, the build system often turns into small project in itself. These systems shape your life at work every day. Probably (hopefully) this investment is accounted for as part of project cost and planning... But what’s the experience like using these tools? Are they easy to use? Are the operations speedy? While a lot of attention is given to product experiences, as developers we often overlook our own “user experience” for reading, writing, and shipping code. Investing in this area creates efficiency gains that multiply across every developer in your ecosystem. Usually those people are your own friends and colleagues. It can be very rewarding to work on tools that make their lives a little better.
Open SourceSuccessful open source projects tend to have all these qualities: - The goals and scope of the project are obvious
- The target user base includes a lot of software engineers
- Some of them can get paid to work on it That describes most developer tools! It just makes sense to build them in the open. It’s not just about getting code for free. The real payoff is the community. People help each other and collaborate to solve problems. Open source broadens perspectives and connects your team to a network of interesting people with cool ideas. Companies shouldn’t just use free tools; they should encourage their engineers to actively contribute. Everyone wins! This is the main idea behind the Rush Stack effort that I’ve been helping to organize. I’m also a major contributor to the TSDoc standard for TypeScript through my involvement with API Extractor.