4 ms·
Could someone summarize this article? This article is condescending and very poorly written, I can't stand to try to finish it.
by stevebmark 4y ago
Could someone summarize this article? This article is condescending and very poorly written, I can't stand to try to finish it.
- jevgeni 4y agoHere's a recap. - The guy was a principal engineer at Mailchimp. - Assumes he solved the problem of organizational complexity. - Quotes the Stanford Encyclopedia of Philosophy instead of any relevant operational or organizational research. - Firms tend to ignore outside perspectives and examples. (which is often true) - Assumes an organization is a distributed computational process. (it's not) - Kant. - The *amount* of work (i.e. work hours) a company can dish out grows linearly with headcount. - Time for parallel tasks amortizes to zero if more resources are added. (no idea what this means...) - Assumes organizations only write software. - Assumes people know or care what "superlinear productivity" is. - Assumes productivity = added value. - Says that orgs should optimize for individual productivity. - Queue theory and King's formula and hand-waving about contention - Management consultants are bad at writing code. - (I gave up after that)