I think it's better to view this in terms of analyzing abstractions and their pros and cons, versus some vague notion of explicit vs implicit. The more I learn

I think it's better to view this in terms of analyzing abstractions and their pros and cons, versus some vague notion of explicit vs implicit. The more I learn, the more it seems an immense portion of high caliber software engineering is knowing how to approach and analyze very general questions related to abstractions, such as: 1. Given the current and expected future constraints, is this the best abstraction we can come up with? 2. Is the abstraction worth its cost? How heavily should we invest in using it, given how confident (or not) we are currently that it solves our problem well? I think of abstractions as being everything from breaking an if condition into several local variables to splitting a large monolithic app into independent services. We could go further of course, but I think that gets the idea across.