Coding green, revisited

analysis
Aug 2, 20082 mins

I'm obviously not the first person to think about the concept of coding green. I say that because after writing about the topic this week, I found this article on earth2tech titled "Your bad code is killing my planet," written last year by Alistair Croll, vice president of product management and co-founder of Coradiant. In it, Croll takes the position that three modern advances in technology mean that bad code m

I’m obviously not the first person to think about the concept of coding green. I say that because after writing about the topic this week, I found this article on earth2tech titled “Your bad code is killing my planet,” written last year by Alistair Croll, vice president of product management and co-founder of Coradiant.

In it, Croll takes the position that three modern advances in technology mean that bad code matter:

1. Virtualization – If you’re scaling apps across hundreds of servers, you don’t want bloated code, or it means you more of a load for your machines. That, in turn, means you need more servers to satisfy service levels, which in turn means more power usage, both to run the servers and to keep them cool.

2. “Power is the limiting factor for many data centers.” Datacenters don’t have the power (or the space) to spare to add infinite machines, which makes fat code all the less appealing.

3. “Software-as-a-service platforms let us run sophisticated applications on someone else’s infrastructure.” Problem is, the more we need to use, the more we need to pay. Again, bloated code means a waste of energy and a waste of money.

Read Croll’s article in its entirety here.