Submitted via IRC for soylent_blue
Linus Torvalds: 'I'm not a programmer anymore'
Linus Torvalds, Linux's creator, doesn't make speeches anymore. But, what he does do, and he did again at Open Source Summit Europe in Lyon France is have public conversations with his friend Dirk Hohndel, VMware's Chief Open Source Officer. In this keynote discussion, Torvalds revealed that he doesn't think he's a programmer anymore.
So what does the person everyone thinks of as a programmer's programmer do instead? Torvalds explained:
I don't know coding at all anymore. Most of the code I write is in my e-mails. So somebody sends me a patch ... I [reply with] pseudo code. I'm so used to editing patches now I sometimes edit patches and send out the patch without having ever tested it. I literally wrote it in the mail and say, 'I think this is how it should be done,' but this is what I do, I am not a programmer.
So, Hohndel asked, "What is your job?" Torvalds replied, "I read and write a lot of email. My job really is, in the end, is to say 'no.' Somebody has to say 'no' to [this patch or that pull request]. And because developers know that if they do something that I'll say 'no' to, they do a better job of writing the code."
Torvalds continued, "Sometimes the code changes are so obvious that no messages [are] really required, but that is very very rare." To help your code pass muster with Torvalds it helps to ''explain why the code does something and why some change is needed because that in turn helps the managerial side of the equation, where if you can explain your code to me, I will trust the code."
In short, these days Torvalds is a code manager and maintainer, not a developer. That's fine with him: "I see one of my primary goals to be very responsive when people send me patches. I want to be like, I say yes or no within a day or two. During a merge, the day or two may stretch into a week, but I want to be there all the time as a maintainer."
That's what code maintainers should do.
(Score: 5, Interesting) by acid andy on Wednesday October 30 2019, @05:09PM
I'd also add that these religious obsessions with reinventing libraries, languages and methodologies without adding any genuinely new power to what came before are probably the mark of a bad software developer. A good coder can see if programs written using two different technologies are functionally equivalent--and if they both compile to equivalent machine code then all that is left to differentiate them is higher level things like readability, type safety, expressive power, and how experienced a team is with that language.
I can see a case for the development of new languages, or libraries, to improve security, take better advantage of parallelism, or support new technologies like quantum computing. If on the other hand it's just a new flavor of the same old stuff, as far as I'm concerned it's just an excuse to boast and to sell books, software licenses and training courses.
Welcome to Edgeways. Words should apply in advance as spaces are highly limite—