Energy isn't taught in most curricula and no tool shows it by default, so teams don't know what their design choices cost. Surveys cited in GreenCode's review found 18% of developers considered energy during development and just 10% had measured it.
The fix you can use today
Give teams one easy measurement tool and a demo on their own code.
Make one energy check part of normal review.
Share before-and-after results from your own systems.
A survey found that only 10% of developers had ever measured the energy of their software. GreenCode's research review draws on this work.
Tools that help
green-languages (GreenCode researchers): a command-line tool that measures the energy of whole programs or marked sections of code, across languages
GreenCode Constitution skill (GreenCode researchers): open-source energy principles and a catalogue of 37 energy anti-patterns that an AI coding agent can follow to find and fix waste like this
CodeCarbon: a Python package that estimates the energy and CO2 of a run from hardware power and regional grid intensity
How GreenCode helps
GreenCode helps tackle this by turning the record of every change it makes into training material written around the team's own code, so the lesson arrives with the pull request. More on this.
