A Philosophy of Software Design, 2nd Edition
The dilemma is a cruel one. For efficiency and conceptual integrity, one prefers a few good minds doing design and construction. Yet for large systems one wants a way to bring considerable manpower to bear, so that the product can make a timely appearance. How can these two needs be reconciled? Mills's Proposal A proposal by Harlan Mills offers a f
... See moreFrederick P. Brooks Jr. • Mythical Man-Month, Anniversary Edition, The: Essays On Software Engineering
This basic stack is so accepted (and frankly so much easier now with AWS etc.) that we rarely question it. But it's ridiculously inefficient. Why should every potential business need to build all 3 parts of this stack when their core innovation or value add comes primarily from one or two?
Danny Zuckerman • Data composability: what it is + why it matters
Most of the big last gains in software productivity have come from removing artificial barriers that have made the accidental tasks inordinately hard, such as severe hardware constraints, awkward programming languages, lack of machine time. How much of what software engineers now do is still devoted to the accidental, as opposed to the essential? U
... See moreFrederick P. Brooks Jr. • Mythical Man-Month, Anniversary Edition, The: Essays On Software Engineering
Add one component at a time. This precept, too, is obvious, but optimism and laziness tempt us to violate