Dear Diary: How Energy-Expensive is a Bug?

25-minute Talk

Facing climate crisis and stupid wars we should accept our responsibility and the challenge to refer to energy consumption as a first-class quality to assure and to improve in the software we develop.

Virtual Pass session

Timetable

11:45 a.m. – 12:30 p.m. Thursday 24th

Room

Room F3 - Track 3: Talks

Audience

It's our shared responsibility to contribute to our environment, my talk is dedicated to everyone.

Key-Learnings

  • Energy consumption is a first-class quality we need to assure
  • Research of how to develop green software is not new
  • Practicability of how to develop green software is still challenging
  • Energy consumption of bugs can be measured
  • We can do something! More specific suggestions are to be outlined in the talk

Towards greener software beyond greenwashing

Dear Diary, I'm always honest with you. Many companies see the need of contributing to our environment and being sustainable. Using green hosting providers and data centers, or avoiding flights for business trips is one dimension they apply or consider to do. This is good already or at least a first step into the right direction! But, from my perspective, becoming energy-neutral is only one part of the whole story. I'm struggling with the question of what we can really do to reduce our resource consumption? As always when I have a conflict with myself I'm writing to you. I'm convinced that we as software developers have a strong responsibility to reflect on our power to refer to energy consumption as a first-class quality we can genuinely improve (= reduce) in order to make a difference for nature and our environment. Additionally, current situation of stupid wars also shows that dependencies to electricity providers should be avoided. So, dear diary, I'm going to create a talk for the Agile Testing Days, and I will shed some light on the challenge to reduce energy consumption of our developed software. I'll show that it is important to be able to identify energy bugs and how to measure them. Yes, we can do something in the domain of software development! I hope the audience will like it and that it can help in changing their thinking.

Related Sessions

11:45 a.m. – 12:30 p.m.
Room E2+E3 - Track 5: Test Automation Deep Dive

25-minute Talk

10:45 a.m. – 12:30 p.m.
Room D5+D6 - Track 6: Accessibility Deep Dive

105-minute Workshop

Virtual Pass session
9:15 a.m. – 10:15 a.m.
Room F1+F2+F3 - Plenary

45-minute Keynote

Virtual Pass session
10:45 a.m. – 11:30 a.m.
Room F3 - Track 3: Talks

25-minute Talk