GitHub and Yale Survey Reveals Developer Demand for Software Efficiency and Sustainability Tools

A new survey published by GitHub and the Yale Program on Climate Change Communication reports that a significant majority of surveyed developers want better tools to measure and improve the energy efficiency of software. According to the report, which gathered responses from 1,039 GitHub active users in the United States, about 80% of respondents expressed interest in tools for writing energy-efficient code and learning best practices to reduce environmental footprints.

Survey Findings and Developer Sentiments

The research indicates strong concern among respondents regarding climate change and the environmental impacts of artificial intelligence systems:

• Climate Concerns: 79% of respondents reported worrying about global warming.
• AI Impact: 71% expressed concern over the environmental footprint of AI, encompassing energy consumption, water use, and carbon emissions.
• Organizational Goals: 75% stated it is important for their employers to actively work toward reducing environmental impact.

Readers should note that these findings reflect a non-probability sample of GitHub users who opted in to marketing emails. Consequently, the responses represent only the surveyed group rather than all developers universally, and responses differed from broader U.S. adult population samples surveyed by Yale.

Practical Steps for Efficiency

The survey highlights that while interest is high, many developers feel their daily work has only a small impact on reducing environmental footprints. Survey feedback pointed toward specific technical needs, such as estimating repository footprints and finding unnecessary GitHub Actions runs.

Engineering efficiency can begin by targeting visible areas of waste across four main pillars:

• Code: Addressing repeated computations, inefficient algorithms, and unoptimized allocations.
• Data: Managing unbounded queries, over-fetching, and missing caching strategies.
• Network and I/O: Reducing duplicate requests, oversized payloads, and unnecessary polling.
• Frontend: Eliminating unnecessary rendering and eagerly loaded off-screen assets.

Verification and Tools

To ensure reliability, developers are advised to back up claims with verifiable data. Metrics such as execution time, CPU utilization, memory allocation, and network transfer sizes serve as proxies for demand, though each has limitations. Automated tools, such as the open-source Daily Efficiency Improver workflow, can assist in scanning repositories for efficiency opportunities and generating draft pull requests. However, human maintainers remain responsible for reviewing evidence, testing changes, and deciding what ships.

To verify these findings, readers can review the full report on the official GitHub Blog and examine the methodology documentation provided by GitHub and the Yale Program on Climate Change Communication.