3 ms·

This should be required reading for any developer, if only to hopefully instill the belief that you will eventually reach a problem that you cannot lean on pure

• varelse 13y ago
  Fortunately, one frequently transitions to management and/or dies before this happens because one's career is finite. Linux and other such runaway success stories are true Black Swans and Linus's subsequent embrace of source code control IMO demonstrates you can teach new tricks to old dogs.
  • derekp7 13y ago
    I don't remember that Linus was against source control -- it's just that none of the solutions at the time really fit the methodology that the Kernel was developed under. That was his main argument. And actually, there was source control all along. Every version of the kernel was a separate tarball sitting on many ftp servers, and there was a patch / set of patches to bring it to the next version. It just wasn't a database-backed automated version control system.
• mattfenwick 13y ago
  But is that really what this thread shows? It didn't show that for me. What I got out of the thread was that Linus had a solid & rational argument justified by actual technical reasons, which was ignored by Eric. I did not see where Linus was leaning on pure ability.