It is my observation that if you use a shit ton of abstractions, wrapper libraries, frameworks, so on, your software gets crappier. This is from experience, too. Whereas, if you build something from scratch, that is, reduce reliance on abstractions, the software quality in the long run is more stable. Thoughts?
The best code I've seen uses abstractions to decouple itself from the libraries and frameworks it uses. I don't see any references to libraries or frameworks within the codebase, except in thin layers at the outskirts.<p>The worst code I've seen uses 1,000 frameworks and libraries without abstracting its communication with them. It calls their API's directly, inherits from their classes, and passes their domain objects to its own API's.<p>Abstractions should reduce complexity, making code more robust and simpler to understand. It doesn't always work out that way, especially when abstractions have poor names, but it can. If abstractions truly decreased productivity, then machine-code programmers would blow everyone else away with their speed and efficiency.<p>P.S.
I have a deep respect for machine-code programmers.
True, but within reason. For example, if you program in Javascript, you either build your own shitty DOM-library or you rely on a solid one like jQuery.<p>In general I would say your claim is much more true than it is false because a piece of software with too many abstraction layers and wrappers is orders of magnitudes harder to fix than one which doesn't have enough of them.
You might have seen some very bad abstractions. In my experience, they almost always make code more flexible, if designed & implemented sanely. My $0.02.