Anders Hejlsberg on the joy of open source

Key Concepts

• Open-Source Development: A development methodology where source code is publicly accessible, allowing for community contribution and transparency.
• Community Engagement: Active involvement of users in the development process, providing feedback and shaping product direction.
• Issue Tracking Systems: Platforms used to manage and prioritize bug reports, feature requests, and other development tasks (often with upvoting features).
• Iterative Development: A cyclical process of building and releasing software in small increments, incorporating user feedback at each stage.

Benefits of Transparent, Community-Driven Development

The speaker highlights a significant advantage of a development approach characterized by complete transparency and direct community involvement. This model fundamentally shifts the relationship between developers and users, creating a “win-win” scenario. Users benefit from observing the entire development process – described metaphorically as “seeing the sausage being made” – gaining insight into how their feedback is considered and decisions are made. Crucially, this isn’t a closed-door process where issues are taken “behind the scenes” and then a decision is delivered. Instead, the entire “discourse” surrounding each issue is publicly documented within the issue tracking system itself.

Developer Satisfaction and Motivation

Beyond user benefits, the speaker emphasizes the positive impact on developer morale. Traditional software development, involving lengthy release cycles (every “six or 12 months”), often leaves developers uncertain about whether their efforts will resonate with users. In contrast, this open model provides daily validation. The speaker notes the positive reinforcement developers receive – “You guys are so cool…let me upload this” – fostering a more enjoyable and fulfilling work experience. This contrasts sharply with the uncertainty of traditional development.

Prioritization Through Community Voting

A core mechanism of this approach is the use of community voting to prioritize development tasks. Users directly indicate which issues they deem most important by “voting” on them (presumably through an upvote system within the issue tracker). The development team then simply sorts these issues by the number of upvotes, creating a clear, data-driven list of features and fixes the community desires. This system isn’t merely efficient; it actively generates excitement and happiness within the user base.

Iterative Feedback Loop & Positive Reinforcement

The speaker describes this as a “lovely process” and expresses a “deep believer” in its efficacy. The system creates a positive feedback loop: addressing highly-voted issues leads to increased community engagement, which in turn provides further input for prioritization. This iterative approach, driven by direct user feedback, is presented as superior to the traditional, less responsive model.

Notable Quote

“You guys are so cool and let me upload this and whatever…Yeah, this is like this is way more fun than sitting in a room and then like every six or 12 months ship a product and hope that it's the right one.” – This quote encapsulates the core benefit for developers: the immediate and positive feedback loop replacing the uncertainty of traditional release cycles.

Synthesis

The primary takeaway is that embracing transparency and actively involving the community in the development process yields significant benefits for both users and developers. By leveraging community voting for prioritization and fostering open communication, development teams can create more satisfying products and a more engaged user base, moving away from the “hope” of traditional releases towards a data-driven, community-validated approach.