
Facts and Fallacies of Software Engineering

Jim Highsmith is on target when he says, “Productivity measures in general make little sense in knowledge work.”13 Designing good software and infrastructure, solving business problems, and creating IT strategies are knowledge work.
Mark Schwartz • War and Peace and IT: Business Leadership, Technology, and Success in the Digital Age
As long as efforts at learning and change focused on external organizational factors—job redesign, compensation programs, performance reviews, and leadership training—the professionals were enthusiastic participants. Indeed, creating new systems and structures was precisely the kind of challenge that well-educated, highly motivated professionals th
... See moreChris Argyris • Teaching Smart People How to Learn (Harvard Business Review Classics)
I have earlier argued that the sheer number of minds to be coordinated affects the cost of the effort, for a major part of the cost is communication and correcting the ill effects of miscommunication (system debugging). This, too, suggests that one wants the system to be built by as few minds as possible.