Stop Scheduling Like It’s 1999 – Green Software Needs Better Timing

Software, like dinner, is often prepared at night—automated jobs ticking away silently while the team sleeps. But not all kilowatt-hours are created equal. Some are green and clean. Others… well, let’s just say your 2 a.m. batch job might be dirtier than you think.
In this talk, I’ll show how we turned that awkward insight into an actual Java library: GreenScheduled. With one Spring annotation, your jobs can now wait patiently for a greener moment to run—based on real-time carbon intensity data from the electricity grid.

You’ll get a glimpse into:

• Why timing matters for sustainability (yes, even in software)
• How we calculate the “least dirty” execution window
• What went wrong while building it (spoiler: time zones are evil)
• And what’s coming next (hint: Quarkus wants in too)

Expect real use cases, some mild shaming of legacy cron setups—and a hopeful look at how developers can make a difference, one job at a time.

👥 Target Audience

Java developers, tech leads, DevOps engineers, and anyone who's ever written a cron job and never thought about what the power grid was doing at that moment.