Climate Crisis: Can we as developers save the planet? (panel)
summary
Panel argues software can help but also creates impact: data on data‑center energy is missing (estimates range 2% to 50% of global power), cloud providers refuse to disclose kWh, and hyperscale builds like a 400 megawatt facility in Sweden illustrate hidden demand. Practical levers include asking vendors for kilowatt‑hour transparency (ask providers for kWh), shifting noncritical jobs off peak, reducing over‑engineered redundancy, choosing employers by business model, and using checklists like Leaders for Climate Action.
AI-written summary · about
chapters (17)
- 0:00Introduction and panel setup
- 2:52Developer actions in daily work
- 6:05Software’s role in climate impact
- 7:52Lack of transparency in data
- 10:52Challenging data center practices
- 14:34Company choices and developer influence
- 18:42Voting with your career
- 23:20Capitalism and climate urgency
- 28:31Community and activism
- 31:20Open source’s potential for change
- 35:36Technology vs. policy solutions
- 39:30Electronic waste and consumption
- 43:07Personal responsibility and action
- 47:04Imperfect progress over perfection
- 48:16Education and knowledge sharing
- 52:11Corporate accountability and resources
- 57:33Closing remarks and takeaways
related talks
55mCode that Won't Heat the Planet: Engineering Sustainable Software for a Better Future
32mCoding Against Climate Change
57mSustainable Green Software development
44mFighting Climate Change by Building Sustainable Software
31mHow to save the world... one line at a time?
48mSustainability in software engineering - how to fight climate change
46mMaking Software & Data Architectures Sustainable
22m#ClimateActionNow! How sustainable software development...