The article is essentially discussing frustration at the hiding - by abstraction - of technical debt incurred in adopting poor software architecture and/or development process.
Some potentially relevant quotes[1]:
Zymurgy's First Law of Evolving Systems Dynamics: Once you open a can of worms, the only way to recan them is to use a larger can.
Ducharm's Axiom: If you view your problem closely enough you will recognize yourself as part of the problem.
The organization of the software and the organization of the software team will be congruent. (paraphrasing of Conway's Law)
Separation of concerns ... a necessary consequence of loss of resolution due to scale ... a strategy for staying sane. (Mark Burgess, In Search of Certainty: The Science of Our Information Infrastructure, 2013)
Some potentially relevant quotes[1]:
Zymurgy's First Law of Evolving Systems Dynamics: Once you open a can of worms, the only way to recan them is to use a larger can.
Ducharm's Axiom: If you view your problem closely enough you will recognize yourself as part of the problem.
The organization of the software and the organization of the software team will be congruent. (paraphrasing of Conway's Law)
Separation of concerns ... a necessary consequence of loss of resolution due to scale ... a strategy for staying sane. (Mark Burgess, In Search of Certainty: The Science of Our Information Infrastructure, 2013)
[1] Taken from my fortune clone https://github.com/globalcitizen/taoup