What can a software engineer do about climate change?
Sarah Hsu24:342021
Software is heating the world, and engineers decide by how much
A typical French person's digital activity accounts for 580 grams of carbon a day, and more than half of that comes from software, according to a blog series the speaker cites. For engineers, that turns everyday choices about code, hosting and scheduling into climate decisions. Sarah Hsu, a Cloud Platform Engineer at Goldman Sachs and Climate Action Tech volunteer, asks where a single developer can actually start.
Get the green software principles and practical resources to cut your software's carbon
Sarah Hsu, a Cloud Platform Engineer at Goldman Sachs, argues that software engineers have real leverage on climate change because software drives a growing share of digital emissions. She explains the core principles of green software engineering, shares how she built momentum through Climate Action Tech and an internal working group, and points front-end and back-end engineers to practical starting resources.
“With almost everything that requires the software, from pregnancy tests to self-driving cars, software is not just helping the world progress, it's also heating the world.”
“We're also building applications that are more resilient and performant. And when a piece of software is more resilient and performant, it normally costs less too.”
What you will learn
Explain the core green software engineering principles: carbon efficiency, energy efficiency, carbon intensity and embodied carbon.
Schedule flexible workloads such as daily batch jobs for times and locations where electricity has lower carbon intensity.
Find starting resources for front-end, mobile and back-end work, from sustainable web design to cloud carbon estimation tools.
Build momentum for green software at work with awareness talks, a shared deck and a working group of like-minded engineers.
Start with small wins, such as switching off machines that run all day for a once-a-day job, before proposing redesigns.
Key takeaways from the speaker
Software engineers can make decisions to accelerate climate actions and join in the fight to address the climate crisis now.
As technology integrates further with our society, software engineers are empowered to make decisions that will have lasting impacts for generations to come by understanding the principles of Green Software Engineering.
How can you get involved now? Remember, every bit of help is meaningful, and as an individual, you can influence real impact.
Details
Level
Beginner
Format
Talk
Technical depth
Introductory technical
For
Early career, Mid-career, Senior individual contributor
Length
24:34
Published
June 2021
Questions this talk answers
How does software contribute to climate change?
Citing the Developers Can Save the Planet blog series, Sarah notes that of about 14.5 kg of carbon a typical French person emits per day, 580 grams come from digital activity and about 55% of that from software.
What is carbon intensity and why should engineers care?
It measures how much carbon is emitted per kilowatt hour of electricity consumed, and it varies by location and over time. Engineers who are flexible about when and where workloads run can choose cleaner times and places.
Where can a software engineer start applying green software principles at work?
Start small rather than proposing to rewrite everything, for example by turning off a machine that runs 24/7 for a batch job that runs once a day. How far you go depends on your organization's size and who you need to convince.
What resources exist for front-end and back-end engineers?
Front-end engineers can use the book Sustainable Web Design, website carbon calculators and progressive web apps. Back-end engineers can draw on a 2018 programming language benchmark study, Microsoft's green software blog and an open-source tool that estimates workload emissions on AWS, Azure and GCP.
Does green software bring benefits beyond lower emissions?
Yes. Sarah says greener applications are also more resilient and performant, and that normally makes them cost less too.
About this talk
The COVID-19 pandemic has not just reminded us of the importance of tackling climate change but also its urgency. In this talk, Sarah will share her journey as a Green Software Engineer, emphasising that every bit of help is meaningful, and individuals can have a real impact. She will also cover the basics of Green Software Engineering before sharing examples of applying the principles, providing a call to action for like-minded engineers.
Start green software at work with small wins (73 s)
Speaker: Hello, everyone. Welcome to this presentation. I'm really excited to be here, and it's great to see so many of you have decided to spend the next 20 minutes with me to learn more about what can a software engineer do about climate change. So what we're going to cover today. Firstly, we will learn the principles of green software engineering. Next, I will share my journey so far as a green software engineer, demonstrating that software engineers can help accelerate the climate actions. Then we will go over resources that I have organized for front-end and back-end engineers, respectively. Hopefully, those resources can be a nice kickstart to your strategies to join the fight against climate change. I have set aside the last five minutes of this presentation for Q&A, so please save all your questions towards the end where
you can use the chat function provided by helping to type in your questions. Thanks, Iona, for a lovely introduction, but let me just quickly introduce myself again. A little bit about myself. My name is Sarah Hsu. I'm a site reliability engineer with Goldman Sachs, specializing in Amazon Web Services, and currently, I'm supporting our consumer car businesses. I'm also a volunteer with climate action tech. Climate action tech is a very vibrant online community for any tech workers who are passionate about climate change. If you have any additional questions after the session, please do reach out to me directly using my email, or you can connect with me on LinkedIn.
Normally, when you read about climate change in the news, you see forest fire, you see drought, you see polar bears standing over ever-decreasing melting ice caps. All these events are very scary, and they are a great reminder for us all on how desperate the situation is. But they all seem very far from what we do day to day a software engineer. Guess that brings us to why we are here today. What exactly can a software engineer do about climate change? Let me quickly set the theme on how the software is actually heating the world.
This is actually a really interesting series of blog posts called Developers Can Save the Planet. I do encourage you to check out the whole thing, but long story short, in the first part, the author estimated that a typical French person would emit about 14.5 kilograms of carbon per day, and 580 grams of those emissions come from digital activity, and about 55% of the digital emissions come from software. With almost everything that requires the software, from pregnancy tests to self-driving cars, software is not just helping the world progress, it's also heating the world. So what we do day to day to day, a software engineer can have a real impact on the global effort to decarbonize if we can adapt to build softwares that are sustainable.
But what do we mean by building sustainable software? Up till recently, there is no industry-wide agreed definition on what GSE should entail. A lot of research has been done in the space, but people started to notice everyone has slightly different definitions when it comes to calling something green in the software engineering context. So last year, a group of people from the Mozilla Foundation and Microsoft, they came together and gave GSE the following definition. Green software engineering is an emerging discipline at the intersection of climate science, software practices and architecture, electricity markets, hardware and data center design. The first principle of GSE is all about carbon and how building carbon efficient applications can have a real impact. Carbon is a shortened way to describe all greenhouse gases. Greenhouse gases are gases in Earth's atmosphere that trap heat. They let the
sunlight pass through the atmosphere, but they prevent the heat that the sunlight brings from leaving. So essentially greenhouse gases acts as a blanket increasing the temperature on the surface of the Earth. Do you remember that this is a natural phenomenon, but due to the crazy amount of human-made carbon pollution, the global climate is changing at a rate that is too fast for us human, animals or plants to adapt.
So the goal of the Paris Climate Agreement is to reduce carbon pollution. So the temperature increase stabilizes to 1.5 degrees Celsius by 2100. And the temperature increase is dependent on the total amount of carbon we have in the atmosphere, not the rate at which we're emitting the carbon. So to completely hope the rate of temperature increase, we need to stop adding carbon in the atmosphere or achieve something that's called the net zero emissions.
Net zero just means for every ground of carbon we add to the atmosphere, we have to take it away. So the overall mass of the carbon remains fixed. The second principle is about electricity. How building applications that are energy efficient can help us reduce our energy consumption/electricity consumption. The third principle is about carbon intensity. The carbon intensity of electricity is a measure of how much carbon emissions are produced per kilowatt hour of electricity consumed.
Not all electricity are produced the same way. Some are produced by burning of fossil fuels and we consider those electricity dirty and some others are produced by renewable sources such as wind or solar and we consider those clean. So if I plug my laptop directly into a wind farm, then the carbon intensity of electricity that my laptop consumes would have a carbon intensity of zero.
But none of us can't really plug anything directly into wind farms. Instead, we use power grids. Those power grids are normally supplied with electricity from a mix of sources. And because of the varying nature of renewable sources, the carbon intensity of electricity changes by location and changes over time. So if we can be flexible with when and where we consume electricity, we can then choose to run our workload when the carbon intensity is less.
For example, I can choose to host a Bitcoin farm at a location that has zero carbon intensity. So if I have daily if I have a batch job that needs to run once a day, why don't we look for a time frame that is at least carbon intense? The fourth principle is the embodied carbon. Embodied carbon is the amount of carbon pollution produced during the creation and disposer of a device.
But why do we care? We're not hardware engineers. Almost everyone's first thought when an application is laggy is I should probably get a new phone. The average lifespan of mobile phone is estimated at two years. It's not even just a mobile phone. It's the hardware in our laptops. As developers, we can make sure that the applications we've built can run smoothly on all the hardware.
Here are all the eight principles. I do encourage you to go check them out and familiarize yourself with them. Because by understanding those eight principles, we are in a great position to define, build and run green software. Right. So if I can make a tiny guess on what you're thinking right now, are you thinking, "Wow, I did not realize software engineers can have a real impact when it comes to addressing climate crisis."
Or are you also thinking, "Okay, what now?" "I know about the principles. They're all well and good, but what can I do and where can I start?" "Don't worry, I got you." I was feeling and thinking exactly the same same time last year. I was inspired by this one sentence in a podcast. This podcast is not even about green IT. It was about cloud monitoring. The founder of this cloud monitoring made a career transition from security. And while he was discussing the transition with the host, he said something along the line that how he can now use his expertise to have a real impact tackling climate change.
This one sentence really resonated with me. I've always tried to do better when it comes to be more environmental friendly. But there's just so much I can do by grieving my friends or family when I see them use plastic bottles. So now I want to share my journey with you, what I have done internally and externally. And hopefully those actions can inspire you to start your own journey as a green software engineer.
So the first thing I did after the podcast was to hit the internet. I wanted to see what has been done in a space. We are all software engineers. We don't like reinventing the wheels. Then I found green software engineering as a discipline, which led me to climate action tech. Again, it's a very vibrant online community for any type of tech workers who are passionate by utilising their technical skills to address the climate crisis. Since joining, I've started volunteering.
Right now, I'm helping out new members to onboard and make sure they are settled in. And most importantly, is to make sure that the new members are connected with others whom they share common goals or interests. I really love the community's energy and the variety of topics that it covers. And every time I have a question, it's always responded quickly and with very useful information. Even though my volunteering responsibility right now doesn't cover any actual technical work, but I do feel like I'm having an impact in the space. The community is also very open to new ideas. And right now we have kickstarted a new proposal, which I hope will massively help others who are in the same boat as me. Where finding the right project
with the right tech staff in the correct time zone is really tricky nowadays. With everything online, with like a hundred different open source projects you can get involved with. And last point I want to make is that green software engineering is not necessarily a new discipline, but a discipline that has gained a lot of traction lately due to the current climate crisis. So a lot of people aren't aware of this topic and not realizing how much of an impact our daily activities as soft engineers can have.
So earlier this year, I put together a deck very similar to this one, and I started talking about this topic to basically any engineers who would spare me two minutes. What about what I did internally at my company? Very similar to what I have done externally. I started by giving talks to engineers in my region. Then I found a group of like-minded engineers, and now we have a working group on green software engineering. Again, what we realized, this discipline is not very well known, so we have a shared deck that we use whenever an opportunity should arise for us to raise awareness.
Their working group has now grown to a healthy size that we are capable of running multiple initiatives concurrently. So what about you? What can you do next? Before we jump into the resources for front-end and backing engineers, I just want to reiterate that volunteering is a worthwhile contribution in this space, and I do encourage you to find a topic that you're most interested in.
It's a shame that we're not in person, and I can't ask you to raise your hands and see how many of you are front-end engineers, because you guys are a very lucky bunch. The work that has been done in space is very impressive, and they're all readily available online. For example, if you're a designer, there's a book called Sustainable Web Design.
The book describes an approach to designing digital products and services that puts the people and planet first. The author of this book is also the founder of a booting WordPress firm in London, and they have made a head start in a green space. They have regularly published blog posts, for example, the one you see on the slide, 17 ways to make your website more energy efficient.
They've also built a calculator that estimates the amount of carbon your website would have emitted per year. And here, I've tested out the BBC News homepage, and it turns out it's not a very green site. The amount of carbon emission estimated is roughly equal to what 14 trees would have absorbed in one year alone. And if you're a mobile developer, building a progressive web app is not just making your application more efficient, and how you can reach more audience, all the benefits that come with building a PWA have a great aspect to them as well.
And if you're a backend engineer, there are also loads of work being done in the space, not as much as the front end, but just enough to get you started. There's a very interesting study done back in 2018, where they benchmark tested different programming languages, and they've provided a useful table for you to consider which one to pick based on optimal sets.
For example, C, Pascal, and Go are the top choice if your optimal objectives are time and memory. Microsoft is also leading the pack here, where they have started a blog post sharing tips and tricks on how to write green software. And this particular one I've shared, demonstrate how you can measure power consumption of your backend services. And lastly, there's now this open source tool available if you host your solution with any of the following cloud providers: AWS, Azure, or GCP.
This is a really, really nice tool that uses the out-of-the-box APIs provided by each cloud provider to estimate the carbon emission of your workload. But what about SRE and DevOps phase? Right now, there's not a lot being done in this phase. We are in a phase where applying green software engineering principles is going to start make waves across the tech world.
And how would those affect the way we support, for example, a 4.9 service? Is it possible for us to do monitoring based on demand instead of having a Prometheus cluster running 24/7? Right, before we start the Q&A, I want to quickly talk about the additional advantages for going green. We're not just building applications that emit less carbon.
We're also building applications that are more resilient and performant. And when a piece of software is more resilient and performant, it normally costs less too. So I guess that brings us to our last slide. I hope you have enjoyed this talk and the talk has inspired you to kickstart your GSE journey. Remember, it's Earth Day every day.
The planet is in desperate need of help for anyone and everyone. Thanks, guys. Right, let me just go to the chat function. Can we get... Well, I will reach out to the organizer and see how I can share the slides. Yeah, I actually do have another slide. But I don't really want to make this session too preachy.
But let me just quickly share that with you. So basically, there are some habits we do when we are tech users. For example, when you stop using your computers, you can try to switch it off. We can then save energy and electricity. And if you are watching Netflix, if you have an opportunity to download and not stream, that can also save a lot of electricity.
And again, we're all software engineers. Dark mode is saving us so much energy. So change your ID to dark mode. And Zoom meetings, I know this has been a crazy year where Zoom has transformed the way that we have experienced corona if we're in a different decade. And so if you are in a Zoom meeting with a hundred other people, where sharing your face is really not that important, you can try turning it off.
I think there was a study that basically, if you turn your camera off during a Zoom meeting, you can reduce about 87% of the carbon emitted if you have your camera on. Again, ditch the clutter, declutter, try to delete things that you don't need anymore because those are taking up space. Those are taking out your RAMs and CPU when you're running your laptop.
And lastly, prolong electronics. You can do like, I know I'm the same, you know, I live in the UK. I always try to buy a new phone every two years. I don't know why, they still work, but it's just probably my contract run out and then they try to sell me a new phone and I buy it.
So it is a really difficult transition to make, but hopefully with the common goal to decarbonize globally, those are the habits we as tech users can also pick up. What's the difference between download and stream? Oh, I guess like streaming is because the way that Netflix where they have like CDN, right, at the different edge locations. So they will have to make sure that the CDN is working in the nearest location with where you are, right?
And, but if you download it after they send it off, you don't have to keep going back to Netflix and have like a connectivity between your phone and Netflix. Right? So you can only, so you can basically watch TV without internet and that's saving a lot of electricity and energy. Um, cool. I think, um, I see my nails have any more problem.
I mean, not problem, um, questions. Yeah. I know the Mozilla foundation has been doing a lot of really interesting work. Um, and I'm really looking forward to what they have achieved. And my, myself, um, is an SRE and I'm really interested in SRE and DevOps space. So hopefully there's some, something coming out of this space in the next couple of months.
I have faith. And if you're really interested in partnering up to do something with me, please do reach out to me. Um, could you hear me at the end? Oh, no, I can't hear you. Um, Iona. How can the software engineer start applying green software engineering principles at work? Right. I think, um, it really depends on the size of your organization and, and, and, um, and then who you need to convince if that makes sense.
And, um, there's, but then before you actually say, Hey, we need to redesign all our architecture. We need to rewrite all our code. But before you get to that, why don't you think about, Hey, I have a, I have a batch job that runs once a day, but this batch job lives on a, on a machine that is running 24 seven.
Can we, can we try to turn those machines off? You know, just by doing that, we are saving energy and then proxy carbon. So I think by applying brain software engineering principle, it's very, it's very, it's very useful. But then, and again, it really depends on your organization size and who you can convince. And right now, because the discipline is so new, if you Google, Hey, what's the most sustainable way for me to deploy a springboard application to AWS, you can't find any like pattern or like blog posts.
So hopefully in a couple of months, then people will be able to use some of the out of the box too. And then you can then say, Hey, I've seen this guy deploying a springboard applications, applying green software engineering principles. And this is how much carbon, how much cost they have saved. Why don't we try to apply that at work?
Yeah. Yeah, I can hear you. Important thing that I'm trying to unmute is that main practice is that all the amount of carbon nice, because as you mentioned, we don't that consider video in zoom calls. Everyone started of the pandemic. Camera overdue. Yes. To think about all the practice just because their size, but we don't it's a big part of the pandemic.
It would be nice to share if the audience have to be familiar with the topic. I literally like to look for a patient to see on your side. And we have a let's that I find the people than others are bad on yes, how other people are committed in assessing impact of resources. Yeah, so there's a question.
What I found difficult, yes, AWS greener than others, but there are also bad on so many other areas, how other areas should be integrated and assessing greens and human impact of resources. Yeah, I agree. To be honest, right, AWS is actually one of the cloud providers right now does not have a transparent solution, not transparent solution, transparent data point for their customer to see how much exactly, how much carbon my hosted solution is costing.
Like GCP have something called a carbon free energy and Microsoft, they have a calculator for their enterprise customers. So I, but then again, right, hopefully with like so many people now are interested in this topic and how all these topics are in the front page, we can then, we can then like reach out to Amazon or like change the way they provide, they help out the customers basically.
Switching camera off is a trade-off for not commuting and avoiding travels. It's definitely worth it to keep us all connected. I definitely agree. Zoom meeting is very important. So like, I think what I was trying to convey is that if you're, you're in a massive meeting with a hundred other people or showing your face or when you're not speaking, turning your camera off then is probably useful.
But yeah, if it's like one-on-one meeting or like a meeting with less than 10 people, I think definitely have your camera on. Otherwise, it would be very sad to not to see your teammates. Great. Thank you so much, Jessie, for sharing links on SRE. Question from how automation, testing and deploy impact. That is a DevOps space there's not a lot being done.
So for example, I'm mainly working AWS. There are so many different ways of deploying infrastructure to AWS. but I don't know which friendly. I can use Terraform infrastructures code. I can use CloudFormation. I can use CDK. I can use other different tools. But right now, there is just no data set against any of those considerations. So you'll be really useful in the future if there is available, there's two available out of the box for any of those IEC.
And then same thing for like automated testing, like how you have to set up every bit of your automated testing. For example, your front end, your back end. And then like running some like user testing and stuff. Thanks guys.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Article based on this talk
How can software engineers help fight climate change?
Sarah Hsu explains the principles of green software engineering and shows where developers, from front end to SRE, can start today.
In short
Sarah Hsu argues that software engineers have genuine climate leverage, because software now runs almost everything and accounts for a meaningful share of everyday emissions. She walks through the principles of green software engineering, shares how she built momentum both in a volunteer community and inside her company, and points front-end and back-end engineers to resources they can use right away.
Key takeaways
Software engineers can make decisions that accelerate climate action and join the fight to address the climate crisis now.
As technology integrates further with society, software engineers who understand the principles of Green Software Engineering are empowered to make decisions with lasting impact for generations to come.
How can you get involved now? Remember, every bit of help is meaningful, and as an individual you can have a real impact.
Why software belongs in the climate conversation
Hsu opens with a familiar problem: climate news is full of forest fires, droughts and melting ice caps, images that feel far removed from a developer's daily work. To close that gap, she cites a blog series called Developers Can Save the Planet. As the speaker cited, the author estimated that a typical French person emits about 14.5 kilograms of carbon per day, that 580 grams of that comes from digital activity, and that about 55% of digital emissions come from software.
Her conclusion is direct: "With almost everything that requires the software, from pregnancy tests to self-driving cars, software is not just helping the world progress, it's also heating the world." (2:16) If engineers learn to build sustainable software, she says, their everyday work becomes part of the global effort to decarbonize.
The principles behind green software
Hsu explains that until recently there was no agreed definition of green software engineering (GSE). A group from the Mozilla Foundation and Microsoft described it as an emerging discipline at the intersection of climate science, software practices and architecture, electricity markets, hardware and data center design.
She highlights four of the eight principles. The first is carbon: building carbon-efficient applications, in service of net zero, where every gram of carbon added to the atmosphere is taken away. The second is electricity: energy-efficient applications reduce consumption. The third is carbon intensity, the amount of carbon emitted per kilowatt hour, which changes by location and over time because grids mix fossil and renewable sources. "So if we can be flexible with when and where we consume electricity, we can then choose to run our workload when the carbon intensity is less." (5:55) A daily batch job, for example, could run in the least carbon-intense window.
The fourth is embodied carbon, the emissions from making and disposing of devices. Users often blame a laggy app on their phone and buy a new one, so engineers carry responsibility here too: "As developers, we can make sure that the applications we've built can run smoothly on all the hardware." (6:50)
From one podcast sentence to a working group
Hsu's own journey began with a single line in a podcast about cloud monitoring, where a founder described using his expertise to tackle climate change. She went looking for existing work rather than starting from scratch: "We are all software engineers. We don't like reinventing the wheels." (8:51)
That search led her to green software engineering and to Climate Action Tech, an online community for tech workers passionate about climate. She now volunteers there onboarding new members and connecting people with shared interests, and the community has started a proposal to help volunteers find projects with the right tech stack and time zone. Inside her company she followed the same pattern: talks to engineers in her region, then a working group with a shared deck for raising awareness, which has grown large enough to run several initiatives at once. She stresses that volunteering, even non-technical work, is a worthwhile contribution.
Resources for front-end and back-end engineers
Front-end engineers, Hsu says, are lucky: there is a lot of readily available work. She recommends the book Sustainable Web Design, blog posts such as 17 ways to make your website more energy efficient, and a website carbon calculator. Testing the BBC News homepage, she found its estimated yearly emissions roughly equal to what 14 trees absorb in a year. Mobile developers can look at progressive web apps.
For back-end engineers she points to a 2018 study benchmarking programming languages (with C, Pascal and Go leading for time and memory), Microsoft's blog on writing green software, and an open-source tool for AWS, Azure and GCP: "This is a really, really nice tool that uses the out-of-the-box APIs provided by each cloud provider to estimate the carbon emission of your workload." (13:47) SRE and DevOps, her own field, remain largely open, with questions such as whether monitoring could scale with demand instead of keeping a Prometheus cluster running 24/7.
She closes with the business case: "We're also building applications that are more resilient and performant. And when a piece of software is more resilient and performant, it normally costs less too." (14:31)
Starting small at work
In the Q&A, Hsu shares habits for tech users, from switching devices off and downloading rather than streaming to turning cameras off in very large meetings, while keeping them on with small teams. Asked how to apply the principles at work, she advises against opening with a full redesign. Instead, look for a machine running all day for a job that runs once: "Can we, can we try to turn those machines off? You know, just by doing that, we are saving energy and then proxy carbon." (19:35)
She also notes gaps: at the time of the talk, AWS offered customers less transparent carbon data than Google Cloud or Microsoft, and there was no data comparing infrastructure-as-code tools such as Terraform, CloudFormation and CDK.
Watch the talk
"What can a software engineer do about climate change?" by Sarah Hsu, 25 minutes: https://www.womentech.net/video/what-can-software-engineer-do-about-climate-change
About the speaker
Sarah Hsu is a Cloud Platform Engineer with Goldman Sachs focusing on Amazon Web Services, who recently transitioned to a Site Reliability Engineer role with the Consumer Cards business. Alongside being a Cloud Advocate, she is a Green Software Engineer who has volunteered with several climate groups, using her expertise to accelerate climate action.
Questions this talk answers
How does software contribute to climate change?
What is carbon intensity and why should engineers care?
Where can a software engineer start applying green software principles at work?
What resources exist for front-end and back-end engineers?
Does green software bring benefits beyond lower emissions?
Drafted with AI from the talk transcript. Editor review pending.
Frameworks and ideas mentioned
Principles of Green Software Engineering
Net zero emissions
Progressive web apps (PWA)
Resources mentioned
Developers Can Save the Planet (blog series)
Sustainable Web Design (book)
17 ways to make your website more energy efficient (blog post)
Website carbon calculator
Microsoft blog on writing green software
Open-source cloud carbon emissions estimation tool for AWS, Azure and GCP (not named in the talk)
2018 programming language energy benchmark study
Climate Action Tech (online community)
Cite this talk
Sarah Hsu. "What can a software engineer do about climate change?." WomenTech Network, 2021. https://www.womentech.net/video/what-can-software-engineer-do-about-climate-change