Software: Greener is Leaner & Cleaner

"There's an already existing large segment of the software-development ecosystem that cares about this space—they just haven’t known what to do." — Asim Hussain , Green Web Foundation

And THAT (chances are you are part of that 'large segment of the software-development ecosystem that cares') would be my first action oriented call for you, head over the Green Web Foundation and particularly take the course that is hosted in Linux Foundation.

In essence we all are to half our emissions by 2030. Regardless of pledges, this is UN target which is legally binding.

We ALL, humans, as an individual, household, hobby activity, village, city, council, county, country, industry, company, department, product, team... ain't exceptions--half our emissions in all dimensions.

No small task. No time to waste.

Software is everywhere. I argue is no longer 'an industry' per se, but a fabric layer of any business. The question then becomes: how to half your software emissions.

Energy

Less post-processing. How easy is to over complicate things. Only few months ago, having a 15 minutes conversation reviewing an application architecture we got to half the amount of objects (Data tables) and the related post-processing by around 70%.

Better timing. Shifting processing when renewables are plentiful! Look at your grid mix and make informed decisions. When tapping into Software and or Platform as-a-Service, check through your provider (even better if you see what else is out there-put the money where you want the world to go)

For AI related, check this compilation: https://www.dhirubhai.net/pulse/ai-dont-fooled-hype-i-got-ines-garcia-1kgme/

Materiality

We tend to think of software as a decoupled, cognitive, abstract thing. Yet, software is indeed bounded to physical world and natural governing laws (so we are).

Think that software and 'the cloud' is just shared infrastructure--still with servers, hardware and the like into existence.

Questions here to ask is about the balance between redundancy and usage, about keeping those products in used for as long as possible, the temperature needs (cooling, heating, water use and drain) etc

And again, who you do business with matters. Have a clear stand on procurement and don't afraid to ask and change if commitments (and actions) do not align with your goals.

Don't forget the end user devices, the CPU and consumption needs, the support older versions (keeping products in use it's also about the software knock on impact to devices).

Zen

Be more Zen: Less is more.

Thats deletion of code, redundant and unused functionality. As well as deletion of data, images, storage items, deletion of subscriptions, newsletters, old emails. To deletion of accounts, applications, logins...

Here a good entry in the Agile Alliance on Digital Clean Up (and benefits including one's bottom line) https://www.agilealliance.org/digital-clean-up-this-is-how/

Zen is also--Won't do.

Isn't just reduction by deletion, but also avoidance. How much stuff we churn and is just noise? not used? no value? Often a 70% get us to the goal, and sometimes 0% is all its needed. Allowing oneself to ask these questions opens a world of possibilities, including maximising the work not done.

The best thing? You don't have to ask for permission for any of it. Gather details of savings, such as cost savings (storage, apps, usage consumption based), time (easier more flexible and adaptable applications), effort (account for this too!). I can tell you now, other parts of the organisation--including neighbouring teams--will be much interested!

It is up to us.