GreenCode Tech Tips

Short, practical tips for developers, operations teams and CTOs on cutting the energy software uses, each with a problem, a fix you can apply today, and how GreenCode helps, drawn from the project's own research.

Videos for greener software

Every GreenCode Tech Tip is a short video with the same shape: a real problem that wastes energy, a practical fix you can apply yourself, and a line on how GreenCode's pipeline helps with it. Each tip is drawn from the project's own research: its state of the art reviews, its published papers, and the catalogue of energy anti-patterns in the GreenCode Constitution. Below each video you will find the tip written out, with the sources behind it.

Tech Tip #77 Developers · Web and front-end

Make your website grid-aware

What if your website went lighter when the grid gets dirtier?

#carbon-aware#web-performance#ux

Tech Tip #76 Ops and infrastructure · Testing, CI and code quality

Tear down CI environments after use

Your preview environments are still running from last month.

#ci-cd#cloud#idle

Tech Tip #75 CTOs and technical leads · Strategy, reporting and procurement

Back every green claim with a before-and-after

An unsubstantiated green claim is now a legal risk.

#esg#certification#reporting

Tech Tip #74 Developers · Code efficiency

Close what you open

Leaked connections keep burning resources after your code has finished.

#memory#databases#python#java

Tech Tip #73 Ops and infrastructure · Measuring energy

Measure idle power first

Before you measure your code, measure the machine doing nothing.

#measurement#idle#reporting

Tech Tip #72 Developers · Code efficiency

Memoise expensive recursion

Naive recursion can repeat the same calculation millions of times.

#algorithms#caching#python

Tech Tip #71 CTOs and technical leads · Strategy, reporting and procurement

A software saving is worth more at the meter

Save 100 kWh in software, save up to 158 at the meter.

#data-centre#cost#esg

Tech Tip #70 Developers · Code efficiency

Use a set, not a list, for lookups

Checking a list for a name? You're scanning it every time.

#algorithms#python#java

Tech Tip #69 Ops and infrastructure · HPC, embedded, mobile and games

Try a lower CPU frequency for batch work

A 2 GHz cap cost 1-5% speed and saved 13-20% energy.

#hpc#hardware#scheduling

Tech Tip #68 CTOs and technical leads · AI and machine learning

Start pre-trained, fine-tune the adapter

LoRA trained 10,000 times fewer parameters with comparable quality.

#llm#model-efficiency#gpu

Tech Tip #67 Developers · Code efficiency

Stop looping over DataFrame rows

Looping over a DataFrame row by row wastes your processor.

#python#loops#performance

Tech Tip #66 Ops and infrastructure · Containers, Kubernetes and serverless

Go stateless so you can scale down

Your service can't scale down because it remembers too much.

#kubernetes#autoscaling#microservices

Tech Tip #65 CTOs and technical leads · HPC, embedded, mobile and games

Make the efficient mode the default

Most players never turned off the energy-saving default.

#games#ux#devices

Tech Tip #64 Developers · HPC, embedded, mobile and games

Stop rendering what nobody can see

Halo Infinite rendered 4K behind its pause menu. Fixing it saved 15%.

#games#gpu#devices

Tech Tip #63 Ops and infrastructure · Testing, CI and code quality

Add an energy check to CI

Your CI catches slow code. Does it catch hungry code?

#ci-cd#testing#measurement

Tech Tip #62 CTOs and technical leads · Strategy, reporting and procurement

Most developers have never measured energy

Only 10% of developers have ever measured software energy.

#training#measurement#governance

Tech Tip #61 Developers · Measuring energy

Your laptop already has an energy meter

Your operating system already knows which app is draining power.

#measurement#profiling#devices

Tech Tip #60 CTOs and technical leads · Web and front-end

Does dark mode save battery?

Dark mode saves less battery than you think, at normal brightness.

#mobile#ux#devices

Tech Tip #59 Ops and infrastructure · AI and machine learning

Batch your inference

An idle GPU waiting for one request at a time wastes power.

#llm#inference#gpu#performance

Tech Tip #58 CTOs and technical leads · Strategy, reporting and procurement

Keep hardware in service longer

Most hardware is retired because software outgrew it.

#hardware-lifetime#procurement#devices

Tech Tip #57 Developers · HPC, embedded, mobile and games

Predict, don't just react

A smarter controller cut greenhouse energy by over 60%.

#embedded#devices#algorithms

Tech Tip #56 Ops and infrastructure · HPC, embedded, mobile and games

Look up what your job actually used

Your cluster already records the energy of every job.

#hpc#measurement#research-software

Tech Tip #55 CTOs and technical leads · Testing, CI and code quality

Put energy in your definition of done

Energy is in almost nobody's definition of done.

#governance#ci-cd#testing

Tech Tip #54 Developers · Code efficiency

Profile before you optimise

Fixing code that never runs saves nothing.

#profiling#measurement#refactoring

Tech Tip #53 Ops and infrastructure · Cloud and infrastructure

Test your workload on other CPU architectures

Your app might run cheaper and leaner on ARM.

#cloud#hardware#cost

Tech Tip #52 Developers · Web and front-end

Load video only when someone presses play

Autoloaded video can outweigh the rest of the page.

#video#web-performance#frontend

Tech Tip #51 CTOs and technical leads · AI and machine learning

Ask AI for less

Every extra word in or out of a chatbot costs energy.

#llm#training

Tech Tip #50 Developers · Web and front-end

Put your page's footprint in the footer

What if every page told you its own carbon cost?

#web-performance#measurement#javascript

Tech Tip #49 Ops and infrastructure · Containers, Kubernetes and serverless

Attribute energy to pods, not just nodes

Which of your hundred pods is burning the power?

#kubernetes#measurement

Tech Tip #48 CTOs and technical leads · Strategy, reporting and procurement

Don't buy availability you don't need

Half your infrastructure may exist just in case.

#resilience#cost#governance

Tech Tip #47 Developers · Web and front-end

Cache at every layer

Why send the same bytes a million times?

#caching#cdn#web-performance

Tech Tip #46 Ops and infrastructure · Containers, Kubernetes and serverless

Do containers waste energy?

Containers add a small energy tax. Consolidation pays it back.

#docker#kubernetes#right-sizing

Tech Tip #45 CTOs and technical leads · Strategy, reporting and procurement

A green cloud doesn't fix wasteful software

Moving to a green cloud doesn't make your code efficient.

#renewables#cloud#governance

Tech Tip #44 Developers · Code efficiency

Delete dead code and unused dependencies

The greenest code is the code you delete.

#code-quality#refactoring#cost

Tech Tip #43 Ops and infrastructure · Cloud and infrastructure

Consolidate underused servers

Moving VMs off half-empty hosts can cut energy by up to 22%.

#right-sizing#idle#data-centre

Tech Tip #42 Developers · Web and front-end

Serve images at the size they're shown

That 4000-pixel photo is displayed 400 pixels wide.

#images#web-performance#frontend

Tech Tip #41 CTOs and technical leads · Strategy, reporting and procurement

Optimise what runs everywhere

Install base, not percentage, is the number that matters.

#governance#cost

Tech Tip #40 Developers · AI and machine learning

Give your AI assistant structure, not raw files

Pasting whole files into an AI wastes tokens and accuracy.

#llm#ai-assistants#legacy

Tech Tip #39 Ops and infrastructure · Cloud and infrastructure

Put your infrastructure in code

You can't cut waste you can't see.

#iac#cloud

Tech Tip #38 CTOs and technical leads · Strategy, reporting and procurement

Not everything is worth optimising

Some code isn't worth the energy it takes to optimise.

#governance#cost#refactoring

Tech Tip #37 Developers · Code efficiency

Don't block on a hot path

Your server is burning power just waiting.

#performance#networking

Tech Tip #36 Ops and infrastructure · Containers, Kubernetes and serverless

Let quiet services scale to zero

Why run a service all night for zero requests?

#kubernetes#autoscaling#serverless#idle

Tech Tip #35 CTOs and technical leads · Strategy, reporting and procurement

Start with your legacy systems

60 to 80% of software in service is legacy.

#legacy#cost#refactoring

Tech Tip #34 Developers · Testing, CI and code quality

Write the tests before you refactor

Never optimise code you can't test.

#testing#refactoring#legacy

Tech Tip #33 Ops and infrastructure · Containers, Kubernetes and serverless

Right-size your Kubernetes requests

Your pods reserve four times the CPU they use.

#kubernetes#right-sizing#docker

Tech Tip #32 CTOs and technical leads · AI and machine learning

Quantise before you buy more GPUs

8-bit weights ran 175-billion-parameter models without losing quality.

#llm#model-efficiency#gpu#inference

Tech Tip #31 Developers · Web and front-end

Ship less JavaScript

Every page loads your whole app's JavaScript. Why?

#javascript#web-performance#frontend

Tech Tip #30 Ops and infrastructure · HPC, embedded, mobile and games

Test small before you run big

Half a cluster's energy went on jobs that failed.

#hpc#research-software#testing

Tech Tip #29 CTOs and technical leads · Strategy, reporting and procurement

Ask for an energy rating when you buy software

Your fridge has an energy label. Why not your software?

#procurement#certification#standards

Tech Tip #28 Developers · Code efficiency

Do it once, outside the loop

Your loop compiles the same regex a million times.

#loops#refactoring#python#java

Tech Tip #27 Ops and infrastructure · Cloud and infrastructure

Carbon-aware isn't the same as energy-saving

Shifting a job to a greener hour saves no energy.

#carbon-aware#scheduling#measurement

Tech Tip #26 CTOs and technical leads · Strategy, reporting and procurement

Make the saving stick

Cheaper computing can mean more computing.

#governance#esg#cost

Tech Tip #25 Developers · Web and front-end

Load images only when they're needed

Most of your images load before anyone scrolls to them.

#web-performance#images#frontend

Tech Tip #24 Ops and infrastructure · Cloud and infrastructure

Run flexible jobs when the grid is cleaner

The same job can cost less carbon at a different hour.

#carbon-aware#scheduling#ci-cd

Tech Tip #23 CTOs and technical leads · Strategy, reporting and procurement

Put software energy in the numbers you already report

Your IT emissions are probably an estimate.

#esg#standards#reporting

Tech Tip #22 Developers · Code efficiency

Buffer your reads and writes

Writing one line at a time means one system call per line.

#performance#java#python

Tech Tip #21 Ops and infrastructure · Cloud and infrastructure

Find and remove zombie resources

That instance at 3% CPU has been running for a year.

#idle#cloud#cost

Tech Tip #20 Developers · Databases, APIs and storage

Write in bulk, not row by row

Inserting 10,000 rows? Don't send 10,000 statements.

#sql#orm#databases#performance

Tech Tip #19 CTOs and technical leads · AI and machine learning

Make AI pay for itself in energy

Can your AI save more energy than it uses?

#llm#esg#governance

Tech Tip #18 Developers · Code efficiency

Don't build strings with += in a loop

This one-line habit makes your code quadratically slow.

#algorithms#loops#python#java

Tech Tip #17 Ops and infrastructure · Web and front-end

Serve static sites from the edge

A page view shouldn't need a database.

#cdn#caching

Tech Tip #16 CTOs and technical leads · AI and machine learning

Use the smallest AI model that does the job

You're using a giant AI model for a tiny job.

#llm#model-efficiency#inference

Tech Tip #15 Developers · Code efficiency

Even tuned code has energy left in it

An AI agent found savings in code experts already optimised.

#profiling#compiled-languages#video

Tech Tip #14 Ops and infrastructure · Cloud and infrastructure

Shift flexible load to your own solar

Moving flexible data-centre load cut energy costs by 16.64%.

#carbon-aware#scheduling#data-centre#renewables

Tech Tip #13 CTOs and technical leads · Testing, CI and code quality

Clean code is greener code

Ordinary refactoring saves 10 to 30% energy, studies report.

#code-quality#refactoring#cost

Tech Tip #12 Developers · Measuring energy

Faster is not always greener

Your speed-up might not save the energy you think.

#measurement#profiling#llm#gpu

Tech Tip #11 Ops and infrastructure · HPC, embedded, mobile and games

Tune your video pipeline

An AI agent cut FFmpeg 4K transcoding energy by 28.4%.

#video#compiled-languages#profiling

Tech Tip #10 Developers · AI and machine learning

Asking AI for efficient code works, until it doesn't

Asking AI for efficient code made it up to ninety-two percent more efficient.

#llm#ai-assistants#testing

Tech Tip #9 CTOs and technical leads · Code efficiency

An AI agent saved a quarter of the energy

An AI agent saved a quarter of the energy, on average.

#llm#refactoring#measurement

Tech Tip #8 Ops and infrastructure · Containers, Kubernetes and serverless

Slim your container images

Is your container a gigabyte, for a hundred-line service?

#docker#ci-cd#cloud

Tech Tip #7 Developers · Web and front-end

Weigh your web page

We cut our home page from six point eight megabytes to one point seven.

#web-performance#images#javascript#frontend

Tech Tip #6 CTOs and technical leads · AI and machine learning

Count your AI coding assistant's footprint

Coding with AI had nearly thirty-three times the carbon of coding by hand.

#llm#ai-assistants#governance#esg

Tech Tip #5 Ops and infrastructure · Containers, Kubernetes and serverless

Forecast load before you scale

A simple maths model beat neural networks at predicting server load.

#kubernetes#autoscaling#cloud

Tech Tip #4 Developers · AI and machine learning

Give your AI coding agent energy rules

Your AI agent optimises for passing tests, not for energy.

#llm#ai-assistants#refactoring

Tech Tip #3 CTOs and technical leads · Measuring energy

Measure before and after, on the same setup

If you didn't measure it twice, you didn't save it.

#measurement#governance

Tech Tip #2 Ops and infrastructure · Cloud and infrastructure

Your cloud servers are mostly idle

Most cloud servers sit idle about seventy percent of the time.

#idle#right-sizing#cloud#cost

Tech Tip #1 Developers · Databases, APIs and storage

Stop the N+1 query

Your page makes a hundred trips to the database when one would do.

#sql#orm#databases#loops

New tips arrive weekly. Follow GreenCode on YouTube and TikTok to see them as they are released.

  • Format short videos, one tip each
  • For developers, operations teams and CTOs
  • Every tip a problem, a fix, how GreenCode helps
  • Watch on YouTube and TikTok
  • Evidence GreenCode's research and deliverables
GreenCode

Have a tip you want us to cover, or a system you want measured? Talk to the GreenCode team.

Get in touch