Torvalds's job is to say 'no'... and it works
Watch on YouTube He literally said: "Most of the code I write is in my emails". When someone sends him a patch that has a problem, he responds with pseudocode. He doesn't test it. He doesn't compile it. He writes it in the body of an email. That's either very confident or very efficient. Probably both. And his fun
He literally said: “Most of the code I write is in my emails.” When someone sends him a patch that has a problem, he responds with pseudocode. He doesn’t test it. He doesn’t compile it. He writes it in the body of an email. That’s either very confident or very efficient. Probably both. And his main function, in his own words, is to say “no.” That’s what he does. He reads proposals, evaluates whether they make sense, and rejects them when they don’t. His argument is that this constant “no” forces developers to do better work before sending it in. There’s something philosophically interesting about that. The gatekeeper who almost never says yes is what maintains the quality of a gigantic system.
Full episode: https://youtu.be/Swnh7kEXnUE
🤖 AI-generated content: the script, voices, and images in this episode were produced using artificial intelligence tools.
#Shorts