I might have agreed with you a few years ago but these days I see Spotify's perspective more clearly. Today I see code as a liability. Like the parts in my car it is eventually going to break in some strange way and cause me a headache. The only real solution is to never drive a car, but that's almost impossible if you want to get around. Same with code, it's a vehicle that gets a business to a destination, which is nice: bit it can also be quite expensive when things go wrong. Efficient engineering teams balance this inherent risk against the needs of the business.
Comments
I might have agreed with you a few years ago but these days I see Spotify's perspective more clearly. Today I see code as a liability. Like the parts in my car it is eventually going to break in some strange way and cause me a headache. The only real solution is to never drive a car, but that's almost impossible if you want to get around. Same with code, it's a vehicle that gets a business to a destination, which is nice: bit it can also be quite expensive when things go wrong. Efficient engineering teams balance this inherent risk against the needs of the business.
Every line of code has a cost. The question you have to ask yourself is whether that cost is worth the return on your investment?
No code is less expensive than no code.