On infrastructure code

We all write some infrastructure code. All the debug messages. All the connection handling. All the reconnects of a failed connection. All the deployment scripts. All your little helper scripts. Yes your favourite ManagerHelperUtil class too.

Everything your client did not order. Everything your customer is not interested in.

We can call it infrastructure. But we can do better. Much better. The correct term is waste.

Waste? Are you serious?

Yes. All your precious infrastructure. All your cleverness. It is not what your client wants. It is a waste.

Waste?? Waste!! We need it! 

I know. We all produce waste. In our kitchens. In our lives. In restaurants. In offices. In factories. In software development.

It took us so much time! 

I guess so. And it still does. Code is a liability, not an asset.  Just let it go.

But it saves us so much more.

Great. Finally this is a good reason. Sometimes we just cannot avoid producing a waste. Or we could, but it is not worth it. Like 3D printers - no material wasted, but that does not make them efficient for mass production.

So we get to the roots. Yes, you can produce waste when you need. But still - think before you print. Think before you code. Keep the waste in the bin. Recycle.