Better Coding for the Climate?!
summary
Examines how software design choices affect CO2 emissions by giving measurable examples: cloud workloads have grown ~6.5× since 2010 while PUE improved, serverless/FaaS can enable energy-aware scaling, and language/runtime choices change CPU cycles and energy use. Provides concrete figures (79% of an iPhone’s lifecycle emissions occur in production; streaming ≈0.015 kWh/GB; Wikipedia saved ~4.3 TB/day ≈30 t CO2 via page-load optimizations) and argues that extending device lifetime, collecting sufficient data, and using measurable cloud metrics yield the largest emissions reductions despite rebound effects and device-production footprints.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:55Sustainability basics
- 7:46Digitalization energy use
- 13:01Rebound effects examples
- 16:54Device production vs use
- 20:06Cloud efficiency scaling
- 23:16Efficiency in software dev
- 27:15Data model optimization
- 30:43Blue Angel certifications
- 31:50Developer actions
- 32:31Summary outlook
related talks
55mCode that Won't Heat the Planet: Engineering Sustainable Software for a Better Future
32mCoding Against Climate Change
26m“Green” development: is it even a thing?
46mMaking Software & Data Architectures Sustainable
44mCloud computing and carbon emissions
28mSustainable IT : Connect the Dots to a Greener Future
29mResponsible Coding for a Better Future
57mSustainable Green Software development