does that make this a bad idea?
You could think that people are smart enough to understand that they can't patch the most used webserver in the world like that, but hey, remember that Dunning–Kruger effect ?
This article does not tell people to patch Apache. The point, as for as I can tell, is to explore the projects you use so you can learn to write better code.
Then you say "they can't patch the most used webserver in the world like that"
What is "like that"? As far as I can tell it's "working with others". Although I've never patched Apache, I'm confident I'll need to work with others to do so.
The article gives good advice. I don't understand why you would jump to the Dunning–Kruger effect to seemingly assume that the readers are incapable of following the advice.
You're right. But saying something like "I’ve never taken a hard look at the Apache source code before, but I have found a few bugs in Apache that I’d love to have fixed." is like launching a stick in front of a dog.
>The article gives good advice. I don't understand why you >would jump to the Dunning–Kruger effect to seemingly assume >that the readers are incapable of following the advice.
It's a book about php. Don't tell me about Composer, Symfony or other things that 0,1% of php coders are using. Php coders don't read, they cut'n'paste.