4 ms·
"I wonder, if you had 5 different Paul Grahams working on different subsystems of the same project" In fact, I think having one Paul Graham working on the proj
by Hexstream 19y ago
"I wonder, if you had 5 different Paul Grahams working on different subsystems of the same project"
In fact, I think having one Paul Graham working on the project would be better than having 5. Especially "if they'd each create 5 different mutually incompatible object models, with no code reuse between them".
Overhead and incoherence kill.
- henning 19y agoOne person can't do all the work on many modern software projects. Needlessly reinventing the wheel in an incompatible, inefficient way is pointless. Suppose you're working on a 3D game. There'll be plenty of work for one person each for AI, sound, networking, graphics, networking, and game logic. The game logic code will probably touch all those different parts. If each person is like Paul Graham and thinks he'll roll his own fucking object system it's going to be a nightmare.
- gruseom 19y agoIf each person is like Paul Graham and thinks he'll roll his own fucking object system This is a total non-issue. Graham's original comment was that even in situations where an object model was appropriate, he wouldn't necessarily use the OO constructs of an OO language to build one. It had nothing to do with working on a team or not. Conversely, five intelligent programmers would quickly recognize areas of potential conflict and agree on a common approach. This has nothing to do with using OO or not.