Context Aware Ability

fredag den 14. juni 2024

One of the more context-aware abilities when solving a challenge is balancing complexity with appealing to a lower common denominator. I'm not sure if my phrasing is entirely accurate, but I'll leave it for now.

My experience tells me that in any field, the expected up-front complexity simultaneously increases the price and costs, either initially or over time. This might seem like a no-brainer, but the question is what positive side effects reduced complexity offers you.

There are a lot of underlying things here that I'm fully aware exist - for instance, fiberglass doesn't make itself. Or that nuclear power is a more stable base-load technology because it works even when the sun isn't shining or the wind isn't blowing. But I think you understand what I'm trying to say.

"It is easier" naturally also applies to software.

I think it's important, at least for myself, not to view increased complexity as a stamp of higher quality. Quite the opposite, in fact. I don't get a better product by using more complex technology, exclusive ingredients, or titanium. Unless I am 100% aware of why I need to use these. But then I usually pay a higher price for this increased complexity.

Therefore, getting the balance right is also important. In other words, you need to be meticulous about the question of why.

It's actually fun to take your own statements and try to think about what they "cost" up-front, what their relative price is over time, and also what they give back, both up-front and over time.

Is it really that different from:

You don't need to question whether these statements are easier or not - they are merely trying to state a few examples - but you should think carefully when making choices and on what basis you make them.