Energy is in almost nobody's definition of done.
Sustainability stays incidental because nothing in the delivery process asks for it. Changes pass review on features, tests and security, and energy regressions ship unnoticed.
GreenCode researchers found that energy is almost never part of a team's definition of done.
GreenCode helps tackle this by building the energy test for you: a load test generated from the system's own endpoints that records energy as well as speed and ranks the hotspots by the energy they use. More on this.
Energy is in almost nobody's definition of done. Changes pass review on features, tests and security. But nothing in the process asks about energy. So a change that uses more power ships without anyone noticing. It can go unnoticed for months. Here is the fix you can use today. First, add an energy check to your definition of done. Start with the changes where speed matters most. Then add an energy test for your key scenarios. Tools like Eco CI and the Green Metrics Tool fit it into your pipeline. If energy goes up, the release waits. And look at energy trends in the same meeting as speed and cost. GreenCode researchers found that energy is almost never part of a team's definition of done. GreenCode helps tackle this by building that energy test from your system's own endpoints. It records energy as well as speed, and ranks the hotspots by energy. That was GreenCode Tech Tip number fifty-five. Follow for the next tip, and find more on greencode.ai/tech-tips.
Share this
