There was a time about a decade ago when I was obsessing about reducing energy consumption of my laptop (because I wanted it to run on solar energy only). After applying what jwillia3 and Maturin mentioned (that should be the biggest objectives before anything else), I went the last mile by declaring war on bloat.
As Maturin justly put it, "everything you do with the machine uses energy". And "modern" software loves to do *a lot* of things. Standardizing on the simpler variants (i3 instead of Gnome or Plasma, CLI apps instead of web apps, UNIX tools instead of the last trendy tool, etc), you gain on simplicity, which translates to gain on performances, which translates to gain on energy.
And then, the next big step on debloating is to write your own software. Most programs you use to solve one of your problems has been written to solve dozens of other problems you don't have. This has a cost in energy. If you can write a program that solves the single one problem you have, it is usually a big win (for many reasons, including energy saving).
And finally, there is something to say about daemons. Daemons, even idling, consume RAM and CPU cycles, which consumes energy, and this adds up. Maybe instead of having ten programs running in the background, you could have only crond, calling the programs you need every now and then. Maybe instead of having 10 webapp backends running and waiting for connections, you could have one httpd daemon running and running CGI programs, existing only for the time they process a request. You probably have your own preferences regarding infrastructure and software architecture, but systematically asking yourself "how much energy is this going to consume?" is a good mindset to have. Also, wattmeters rock, but that's an other story. ^^